On Mon, Feb 02, 2009 at 01:33:32PM -0000, Chris Bainbridge wrote:
> With it stopped I get:
> keycode 150 = (keysym 0x1008ff2f, XF86Sleep), state = 0x0
> keycode 150 = (keysym 0x1008ff2f, XF86Sleep), state = 0x0
This is the expected behavior; one of these is the KeyPress event, the other
is the KeyRelease event.
> I wonder if it is possible that these two events (press and release)
> both get mapped onto XF86Sleep keycode events, generating two suspend
> calls?
AIUI, the remaining issue is that gnome-power-manager is responding both to
the X keypress and the hal event. (I.e., look at the output of 'lshal -m'.)
It's not clear to me why this affects some systems and not other.
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developer http://www.debian.org/
<email address hidden> <email address hidden>
On Mon, Feb 02, 2009 at 01:33:32PM -0000, Chris Bainbridge wrote:
> With it stopped I get:
> keycode 150 = (keysym 0x1008ff2f, XF86Sleep), state = 0x0
> keycode 150 = (keysym 0x1008ff2f, XF86Sleep), state = 0x0
This is the expected behavior; one of these is the KeyPress event, the other
is the KeyRelease event.
> I wonder if it is possible that these two events (press and release)
> both get mapped onto XF86Sleep keycode events, generating two suspend
> calls?
AIUI, the remaining issue is that gnome-power-manager is responding both to
the X keypress and the hal event. (I.e., look at the output of 'lshal -m'.)
It's not clear to me why this affects some systems and not other.
For me, lshal -m shows:
17:05:11.878: computer_ logicaldev_ input_4 condition ButtonPressed = sleep
and no other events when hitting Fn+F4.
-- www.debian. org/
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developer http://
<email address hidden> <email address hidden>