I had a look at this problem. It seems that the kernel side is alright, I get KEY_POWER input events:
$ sudo input-events 1
/dev/input/event1
bustype : BUS_HOST
vendor : 0x0
product : 0x1
version : 0
name : "Power Button"
phys : "PNP0C0C/button/input0"
bits ev : EV_SYN EV_KEY
waiting for events
11:17:05.881107: EV_KEY KEY_POWER (0x74) pressed
However, they never make it through X.org, with xev I don't get XF86XK_PowerOff. g-p-m doesn't directly listen to input events, just to X.org key presses. So am I right in assuming that we need to fix the xorg driver to propagate KEY_POWER -> XF86XK_PowerOff, or is it meant to work in a different way?
Richard,
I had a look at this problem. It seems that the kernel side is alright, I get KEY_POWER input events:
$ sudo input-events 1 button/ input0"
/dev/input/event1
bustype : BUS_HOST
vendor : 0x0
product : 0x1
version : 0
name : "Power Button"
phys : "PNP0C0C/
bits ev : EV_SYN EV_KEY
waiting for events
11:17:05.881107: EV_KEY KEY_POWER (0x74) pressed
However, they never make it through X.org, with xev I don't get XF86XK_PowerOff. g-p-m doesn't directly listen to input events, just to X.org key presses. So am I right in assuming that we need to fix the xorg driver to propagate KEY_POWER -> XF86XK_PowerOff, or is it meant to work in a different way?
Thank you!