On jeu., 2011-07-14 at 12:42 -0300, Art Ortenburger wrote: > Package: xfce4-power-manager > Version: 1.0.10-4 > Severity: normal > > xfce4-power-manager does not respond to the hardware power button being > pressed, whether set to Shutdown or Ask. gnome-power-manager can detect it > and > initiate a shutdown, as can only upowerd without either power manager, so the > problem isn't hardware or drivers. (The GNOME and KDE power-button settings > seem buggy as well.) > > When reproducing the problem, xfce4-power-manager is running in the > background, > having been automatically launched at login, and the Xfce4 Power Manager > settings have the Power Button action set to "Shutdown". > When the power button is pressed, no action results. > > > The motherboard is an Asus P8P67 Deluxe (rev.3). Below is a transcript of > evtest: > $ evtest > No device specified, trying to scan all of /dev/input/event* > Not running as root, no devices may be available. > Available devices: > /dev/input/event0: Logitech USB Receiver > /dev/input/event1: Logitech USB Receiver > /dev/input/event10: Wacom Bamboo > /dev/input/event11: HD-Audio Generic HDMI/DP > /dev/input/event12: Griffin PowerMate > /dev/input/event2: Microsoft NaturalĀ® Ergonomic Keyboard 4000 > /dev/input/event3: Microsoft NaturalĀ® Ergonomic Keyboard 4000 > /dev/input/event4: Power Button > /dev/input/event5: Power Button > /dev/input/event6: PC Speaker > /dev/input/event7: UVC Camera (046d:0802) > /dev/input/event8: Eee PC WMI hotkeys > /dev/input/event9: HDA Intel PCH Headphone > Select the device event number [0-12]: 5 > Input driver version is 1.0.1 > Input device ID: bus 0x19 vendor 0x0 product 0x1 version 0x0 > Input device name: "Power Button" > Supported events: > Event type 0 (Sync) > Event type 1 (Key) > Event code 116 (Power) > Testing ... (interrupt to exit) > Event: time 1310657422.330326, type 1 (Key), code 116 (Power), value 1 > Event: time 1310657422.330329, -------------- Report Sync ------------ > Event: time 1310657422.330335, type 1 (Key), code 116 (Power), value 0 > Event: time 1310657422.330335, -------------- Report Sync ------------ > Event: time 1310657428.638821, type 1 (Key), code 116 (Power), value 1 > Event: time 1310657428.638824, -------------- Report Sync ------------ > Event: time 1310657428.638829, type 1 (Key), code 116 (Power), value 0 > Event: time 1310657428.638829, -------------- Report Sync ------------ > Event: time 1310657433.904943, type 1 (Key), code 116 (Power), value 1 > Event: time 1310657433.904946, -------------- Report Sync ------------ > Event: time 1310657433.904959, type 1 (Key), code 116 (Power), value 0 > Event: time 1310657433.904960, -------------- Report Sync ------------ > Event: time 1310657627.403203, type 1 (Key), code 116 (Power), value 1 > Event: time 1310657627.403206, -------------- Report Sync ------------ > Event: time 1310657627.403210, type 1 (Key), code 116 (Power), value 0 > Event: time 1310657627.403211, -------------- Report Sync ------------ > > That was for four power button presses. I tested both the case power button > and > the power button on the motherboard. > > The other power button reported, /dev/input/event4, does not receive any > presses, although its information is the same: > Input driver version is 1.0.1 > Input device ID: bus 0x19 vendor 0x0 product 0x1 version 0x0 > Input device name: "Power Button" > Supported events: > Event type 0 (Sync) > Event type 1 (Key) > Event code 116 (Power) > > > Kernel version [from uname; kernel is not Wheezy standard] is > Linux fenrisulfr-pup 3.0.0-rc2-amd64 #1 SMP Thu Jun 9 19:02:26 UTC 2011 x86_64 > GNU/Linux > libc version is 2.13-7 >
Can you run upower --monitor and report back if power button press is detected? Regards, -- Yves-Alexis
signature.asc
Description: This is a digitally signed message part