http://bugzilla.novell.com/show_bug.cgi?id=592447 http://bugzilla.novell.com/show_bug.cgi?id=592447#c5 Thomas Renninger <trenn@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED --- Comment #5 from Thomas Renninger <trenn@novell.com> 2010-08-05 14:42:01 UTC --- This site has quite some info how things should work: http://www.thinkwiki.org/wiki/How_to_get_special_keys_to_work Especially the "2.3 Configuration using HAL" and "2.1 thinkpad_acpi events" section look related. Hm, we had a mechanism that machines need to be whitelisted, does suspend work if you initiate it from KDE? If this works, it's not that. The buggy part may be this file: /usr/share/hal/fdi/information/10freedesktop/30-keymap-module-thinkpad-acpi.fdi or anything related to Lenovo in the fdi directory. To be honest, I am not that familiar with the hal syntax. You could use xev to get more detailed input device info from your key presses, somehow they have to be mapped correctly to the hal fdi file... Could you attach dmidecode. Just an idea, but eventually this is case sensitive: <match key="/org/freedesktop/Hal/devices/computer:system.hardware.vendor" prefix="LENOVO"> but your vendor has "Lenovo" and not "LENOVO" passed... -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.