Your message dated Sat, 10 Dec 2011 15:56:53 +0100
with message-id <201112101556.59126.panfa...@gmail.com>
and subject line Closing bug
has caused the Debian Bug report #542237,
regarding kdebase-bin: powerdevil ignores suspend and hibernate keys
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
542237: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=542237
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: kdebase-bin
Version: 4:4.2.4-1
Severity: normal
Suspend and hibernate work on my Thinkpad R61 using pm-utils and using the
powerdevil GUI in kde4, but the sleep (Fn-F4) and hibernate (Fn-F12) buttons
on the keyboard do not work.
When the sleep and hibernate keys are pressed, "acpi_listen" reports the
following acpi events
button/sleep SBTN 00000080 00000000
button/suspend SUSP 00000080 00000000
"lshal -m" reports
09:15:11.876: computer_logicaldev_input_6 condition ButtonPressed = sleep
09:15:14.277: computer_logicaldev_input_6 condition ButtonPressed = hibernate
and "xev" reports
KeyPress event, serial 31, synthetic NO, window 0x3000001,
root 0x6b, subw 0x0, time 975061, (164,3), root:(1121,523),
state 0x0, keycode 223 (keysym 0x1008ff10, XF86Standby), same_screen YES,
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False
KeyRelease event, serial 31, synthetic NO, window 0x3000001,
root 0x6b, subw 0x0, time 975061, (164,3), root:(1121,523),
state 0x0, keycode 223 (keysym 0x1008ff10, XF86Standby), same_screen YES,
XLookupString gives 0 bytes:
XFilterEvent returns: False
KeyPress event, serial 34, synthetic NO, window 0x3000001,
root 0x6b, subw 0x0, time 980721, (164,3), root:(1121,523),
state 0x0, keycode 165 (keysym 0x0, NoSymbol), same_screen YES,
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False
KeyRelease event, serial 34, synthetic NO, window 0x3000001,
root 0x6b, subw 0x0, time 980721, (164,3), root:(1121,523),
state 0x0, keycode 165 (keysym 0x0, NoSymbol), same_screen YES,
XLookupString gives 0 bytes:
XFilterEvent returns: False
dbus-monitor --session
"type='signal',interface='org.freedesktop.PowerManagement'"
reports nothing.
I do not understand how powerdevil learns about acpi events and do not
know what information you need to investigate the problem, but I'd be
happy to help any way I can.
I see the same symptoms using xfce4-power-manager in xfce4, so the
problem may lie at a lower level of the system. If this bug should have
been filed against a different package, please let me know which one.
-- System Information:
Debian Release: squeeze/sid
APT prefers testing
APT policy: (990, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.30-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages kdebase-bin depends on:
ii kdebase-data 4:4.2.4-1 shared data files for the KDE 4 ba
ii kdebase-runtime 4:4.2.4-2 runtime components from the offici
ii kdelibs5 4:4.2.4-1 core libraries for all KDE 4 appli
ii libc6 2.9-23 GNU C Library: Shared libraries
ii libqt4-dbus 4:4.5.2-1 Qt 4 D-Bus module
ii libqt4-xml 4:4.5.2-1 Qt 4 XML module
ii libqtcore4 4:4.5.2-1 Qt 4 core module
ii libqtgui4 4:4.5.2-1 Qt 4 GUI module
ii libstdc++6 4.4.1-1 The GNU Standard C++ Library v3
ii libx11-6 2:1.2.2-1 X11 client-side library
kdebase-bin recommends no packages.
kdebase-bin suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
> This don't work because I haven't runing powerdevil daemon. After start
> powerdevil daemon all work fine. Sorry for the trouble I am giving you.
> I looked back at the corresponding XFCE bug report, #542238, which I also
> submitted and which led to a long exchange of tests and suggestions, some of
> which might be useful. That bug actually got fixed by an update, although
> nobody seemed to understand why. Sorry I had forgotten this.
--- End Message ---
