Package: xlockmore Version: 1:5.13-2.1 Severity: normal
-- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.11 Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Versions of packages xlockmore depends on: ii libc6 2.3.2.ds1-22 GNU C Library: Shared libraries an ii libfreetype6 2.1.10-1 FreeType 2 font engine, shared lib ii libgcc1 1:4.0.0-9 GCC support library ii libice6 4.3.0.dfsg.1-14 Inter-Client Exchange library ii libpam0g 0.76-22 Pluggable Authentication Modules l ii libsm6 4.3.0.dfsg.1-14 X Window System Session Management ii libstdc++5 1:3.3.6-6 The GNU Standard C++ Library v3 ii libx11-6 4.3.0.dfsg.1-14 X Window System protocol client li ii libxext6 4.3.0.dfsg.1-14 X Window System miscellaneous exte ii libxmu6 4.3.0.dfsg.1-14 X Window System miscellaneous util ii xlibs 4.3.0.dfsg.1-14 X Keyboard Extension (XKB) configu Versions of packages xlockmore recommends: ii libpam-modules 0.76-22 Pluggable Authentication Modules f -- no debconf information xlock will kick the CPU to 100%, makes no sense to use it anymore. I don't know if this anything to do with the fact that I have DRI and that it was a change I recently did. The CPU is kicked to full throttle afaik with the matrix screensaver. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
