[ltp] debugging Fn-F* keys...

Frédéric BOITEUX linux-thinkpad@linux-thinkpad.org
Thu, 13 Mar 2008 13:05:46 +0100


Le mer 12 mar 2008 14:42:20 CET, Henrique de Moraes Holschuh
<hmh@hmh.eng.br> a écrit :

> On Wed, 12 Mar 2008, Frédéric BOITEUX wrote:
> > Then, I tried to seek this event at the input level, using
> > input-events :
> ...
> >  ... But nothing appears here (no trace when pressing Fn-F* keys) ; I've
> > tried to add some debug acpi_fakekey in ACPI scripts, and then the code
> 
> Check if something else did not open the event device and grabbed it
> (requested exclusive access).

	Hello,

  Thanks for the tip, you're all right, it should be someone like hal
or dbus whick transmit it to applications like gnome-power-manager.

  In fact, trying some changes in /etc/acpi/*.sh scripts, I've found
that :
- the acpi scripts are well called when corresponding suspend buttons
are pressed (sleepbtn.sh for Fn-F4, hibernatebtn.sh for Fn-F12)
- these 2 scripts sleepbtn.sh and hibernatebtn.sh send a key to input
via acpi_fakekey, either $KEY_SLEEP or $KEY_SUSPEND
- only the $KEY_SLEEP is received by hal/dbus/gnome-power-manager, but
don't figure out why (and hal/dbus isn't well documented...).

I've found similar reports on the web :
http://library.pantek.com/Mailing%20Lists/lists.debian.org/debian-user/07/0=
7/2301.html
but without solution yet...

I've tried on a Lenny system, but with same behaviour.

	Fred.