Keyboard settings for Suspend and resume disappeared

Hi ,

I recently switched to KDE 4.3.1 (from 3.5.10) and noticed that the hotkeys
for suspend to RAM/Disk are not working any more. xev gives:

S2Disk:
KeyRelease event, serial 34, synthetic NO, window 0x5200001,
    root 0x6d, subw 0x0, time 678796, (854,917), root:(858,942),
    state 0x0, keycode 165 (keysym 0x0, NoSymbol), same_screen YES,
    XLookupString gives 0 bytes:                                  
    XFilterEvent returns: False                                    

S2Ram:
KeyPress event, serial 34, synthetic NO, window 0x5200001,
    root 0x6d, subw 0x0, time 682263, (854,917), root:(858,942),
    state 0x0, keycode 223 (keysym 0x0, NoSymbol), same_screen YES,
    XLookupString gives 0 bytes:                                  
    XmbLookupString gives 0 bytes:                                
    XFilterEvent returns: False                

I assume that KDE4 is blocking the keys. Any idea how to restore the
settings?

Thx
Axel
--
Linux on a ThinkPad: http://www.axxite.com/brn

--
The linux-thinkpad mailing list home page is at:
http://mailman.linux-thinkpad.org/mailman/listinfo/linux-thinkpad

[fred_]

Le Sat, 10 Oct 2009 20:22:30 +0200,
Axel Braun <axel.braun@...> a écrit :

> Hi ,
>
> I recently switched to KDE 4.3.1 (from 3.5.10) and noticed that the
> hotkeys for suspend to RAM/Disk are not working any more. xev gives:
>
> S2Disk:
> KeyRelease event, serial 34, synthetic NO, window 0x5200001,
>     root 0x6d, subw 0x0, time 678796, (854,917), root:(858,942),
>     state 0x0, keycode 165 (keysym 0x0, NoSymbol), same_screen YES,
>     XLookupString gives 0 bytes:                                  
>     XFilterEvent returns: False                                    
>
> S2Ram:
> KeyPress event, serial 34, synthetic NO, window 0x5200001,
>     root 0x6d, subw 0x0, time 682263, (854,917), root:(858,942),
>     state 0x0, keycode 223 (keysym 0x0, NoSymbol), same_screen YES,
>     XLookupString gives 0 bytes:                                  
>     XmbLookupString gives 0 bytes:                                
>     XFilterEvent returns: False                
>
> I assume that KDE4 is blocking the keys. Any idea how to restore the
> settings?

        Hello,

  Usually, these keys are not handled through X input events, but
directly by acpid or hal. try 'lshal -m' to see if there are correctly
detected. I don't know KDE, but it should have a daemon managing power
which should react to these HAL events…

   Hope it helps,
        Fred.
--
The linux-thinkpad mailing list home page is at:
http://mailman.linux-thinkpad.org/mailman/listinfo/linux-thinkpad

Frédéric Boiteux wrote:

>> I assume that KDE4 is blocking the keys. Any idea how to restore the
>> settings?

>   Usually, these keys are not handled through X input events, but
> directly by acpid or hal. try 'lshal -m' to see if there are correctly
> detected. I don't know KDE, but it should have a daemon managing power
> which should react to these HAL events?

Thanks for your input. Indeed, the buttons are determiend correctly:

axel@z60m:~> lshal -m

Start monitoring devicelist:
-------------------------------------------------
^@12:47:38.495: computer_logicaldev_input_3 condition ButtonPressed =
hibernate
12:47:43.766: computer_logicaldev_input_3 condition ButtonPressed = sleep

 ..seems to be the link to the Power management module.

Thanks

Axel

--
Linux on a ThinkPad: www.axxite.com/brn

--
The linux-thinkpad mailing list home page is at:
http://mailman.linux-thinkpad.org/mailman/listinfo/linux-thinkpad