Bug 412515

Summary:	KDE3 ACPI Controls for Thinkpad R61i
Product:	[openSUSE] openSUSE 11.0	Reporter:	Anshul Jain <anshulajain>
Component:	KDE4 Workspace	Assignee:	E-mail List <kde-maintainers>
Status:	RESOLVED DUPLICATE	QA Contact:	E-mail List <qa-bugs>
Severity:	Normal
Priority:	P3 - Medium	CC:	forgotten_vXTZVacoSi, Vinarek.Jan
Version:	Final
Target Milestone:	---
Hardware:	i686
OS:	openSUSE 11.0
Whiteboard:
Found By:	---	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Anshul Jain 2008-07-27 16:54:19 UTC

The special buttons for Thinkpad R61i do not work for the KDE3 version of Opensuse 11.0. However, they do work for the GNOME edition. Only Volume, Suspend to Disk/Ram work successfully. My info from lshal | grep hardware is:-

anshul@sagarika:~> lshal | grep hardware
  system.hardware.primary_video.product = 10754  (0x2a02)  (int)
  system.hardware.primary_video.vendor = 32902  (0x8086)  (int)
  system.hardware.product = '8937A13'  (string)
  system.hardware.serial = 'L3A0826'  (string)
  system.hardware.uuid = 'E4740601-489F-11CB-92E4-A8E6BF53565C'  (string)
  system.hardware.vendor = 'LENOVO'  (string)
  system.hardware.version = 'ThinkPad R61/R61i'  (string)
  laptop_panel.brightness_in_hardware = true  (bool)
  laptop_panel.brightness_in_hardware = true  (bool)
  info.product = 'HDA Intel ALSA hardware specific Device'  (string)
anshul@sagarika:~>


Most importantly, the brightness control which is controlled through nvram and kmilo dosen't work at all! There is a package in the Packman repo called hotkey-setup which does enable the keys to a certain degree...but the native HAL method which would otherwise work with GNOME doesnt work on KDE3.

-Anshul

Comment 1 Anshul Jain 2008-08-20 10:11:58 UTC

KDE devs, any input on how to get the extra keys working?

Comment 2 Jan Vinárek 2008-09-25 18:59:40 UTC

I'd just like to add that when booting in failsafe mod, brightness can be decreased/increased with special keys.

Comment 3 Jan Vinárek 2008-12-22 15:40:29 UTC

Updated to hal 0.5.11-8.2, brightness controls do some random changes of brightness when pressed. Other keys except volume/suspend2ram/disk don't work, hotkey-setup does enable locking session and turning the screen off buttons. 

I'm not sure whether this bug is relevant to bug #382855, since that bug is addressed to kde 4, not kde 3.

Comment 4 Jan Vinárek 2009-04-11 12:39:47 UTC

hal 0.5.11-8.6, kde 3.5.10, still not working.

Comment 5 Lubos Lunak 2009-04-20 15:47:35 UTC

We no longer fix non-critical KDE3 problems, sorry. Can the problem be also reproduced with KDE4?

Comment 6 Anshul Jain 2009-04-21 03:18:57 UTC

Yes, it does not work on KDE 4.2.2 at all either...whether 11.0 or 11.1. GNOME has integrated the Thinkpad keys perfectly, why can't we have the same with KDE4?

Comment 7 Jan Vinárek 2009-05-20 20:25:20 UTC

Interesting... I upgraded to openSUSE 11.1 (due to some experiments with unsupported kernel, which resulted into not working network). Installed from KDE 3 Live CD. Brightness keys do work now (although not perfectly - I can decrease brightness just three times and increase four times, whereas in Windows XP I am offered with 15 brightness levels); however, the bad news are that locking session and turning off the screen doesn't work (even if I install the hotkey-setup). Hal 0.5.12-10.13.1.

Comment 8 Lubos Lunak 2009-05-26 13:15:23 UTC

What is the output from 'xev' for keypresses of the keys that do not work?

Comment 9 Anshul Jain 2009-06-06 05:22:54 UTC

The xev responses are:-
Fn+Home
KeyRelease event, serial 34, synthetic NO, window 0x2a00001,
    root 0x57, subw 0x0, time 5317781, (9,-1), root:(1107,590),
    state 0x0, keycode 212 (keysym 0x1008ff05, XF86KbdBrightnessUp), same_screen YES,
    XLookupString gives 0 bytes:
    XFilterEvent returns: False

Fn+End
KeyRelease event, serial 34, synthetic NO, window 0x2a00001,
    root 0x57, subw 0x0, time 5343642, (57,-7), root:(1155,584),
    state 0x0, keycode 101 (keysym 0x1008ff06, XF86KbdBrightnessDown), same_screen YES,
    XLookupString gives 0 bytes:
    XFilterEvent returns: False

Fn+F2

KeyRelease event, serial 34, synthetic NO, window 0x2a00001,
    root 0x57, subw 0x0, time 5359249, (59,-9), root:(1157,582),
    state 0x0, keycode 146 (keysym 0x0, NoSymbol), same_screen YES,
    XLookupString gives 0 bytes:
    XFilterEvent returns: False

Fn+F3
KeyRelease event, serial 34, synthetic NO, window 0x2a00001,
    root 0x57, subw 0x0, time 5397952, (-855,122), root:(243,713),
    state 0x0, keycode 241 (keysym 0x1008ff4b, XF86LaunchB), same_screen YES,
    XLookupString gives 0 bytes:
    XFilterEvent returns: False

Fn+F9
KeyRelease event, serial 34, synthetic NO, window 0x2a00001,
    root 0x57, subw 0x0, time 5415861, (62,-15), root:(1160,576),
    state 0x0, keycode 207 (keysym 0x0, NoSymbol), same_screen YES,
    XLookupString gives 0 bytes:
    XFilterEvent returns: False

Comment 10 Anshul Jain 2009-06-06 05:23:22 UTC

The xev responses are:-
Fn+Home
KeyRelease event, serial 34, synthetic NO, window 0x2a00001,
    root 0x57, subw 0x0, time 5317781, (9,-1), root:(1107,590),
    state 0x0, keycode 212 (keysym 0x1008ff05, XF86KbdBrightnessUp), same_screen YES,
    XLookupString gives 0 bytes:
    XFilterEvent returns: False

Fn+End
KeyRelease event, serial 34, synthetic NO, window 0x2a00001,
    root 0x57, subw 0x0, time 5343642, (57,-7), root:(1155,584),
    state 0x0, keycode 101 (keysym 0x1008ff06, XF86KbdBrightnessDown), same_screen YES,
    XLookupString gives 0 bytes:
    XFilterEvent returns: False

Fn+F2

KeyRelease event, serial 34, synthetic NO, window 0x2a00001,
    root 0x57, subw 0x0, time 5359249, (59,-9), root:(1157,582),
    state 0x0, keycode 146 (keysym 0x0, NoSymbol), same_screen YES,
    XLookupString gives 0 bytes:
    XFilterEvent returns: False

Fn+F3
KeyRelease event, serial 34, synthetic NO, window 0x2a00001,
    root 0x57, subw 0x0, time 5397952, (-855,122), root:(243,713),
    state 0x0, keycode 241 (keysym 0x1008ff4b, XF86LaunchB), same_screen YES,
    XLookupString gives 0 bytes:
    XFilterEvent returns: False

Fn+F9
KeyRelease event, serial 34, synthetic NO, window 0x2a00001,
    root 0x57, subw 0x0, time 5415861, (62,-15), root:(1160,576),
    state 0x0, keycode 207 (keysym 0x0, NoSymbol), same_screen YES,
    XLookupString gives 0 bytes:
    XFilterEvent returns: False

Comment 11 Jan Vinárek 2009-06-06 06:13:27 UTC

My xev responses:

Fn+Home
KeyRelease event, serial 34, synthetic NO, window 0xe00001,
    root 0x7d, subw 0x0, time 30400582, (814,180), root:(819,224),
    state 0x10, keycode 212 (keysym 0x0, NoSymbol), same_screen YES,
    XLookupString gives 0 bytes:
    XFilterEvent returns: False

Fn+End
KeyRelease event, serial 34, synthetic NO, window 0xe00001,
    root 0x7d, subw 0x0, time 30476945, (954,171), root:(959,215),
    state 0x10, keycode 101 (keysym 0x0, NoSymbol), same_screen YES,
    XLookupString gives 0 bytes:
    XFilterEvent returns: False

Fn+F2
KeyRelease event, serial 34, synthetic NO, window 0xe00001,
    root 0x7d, subw 0x0, time 30520094, (896,157), root:(901,201),
    state 0x10, keycode 146 (keysym 0x0, NoSymbol), same_screen YES,
    XLookupString gives 0 bytes:
    XFilterEvent returns: False

Fn+F3
KeyRelease event, serial 34, synthetic NO, window 0xe00001,
    root 0x7d, subw 0x0, time 30573121, (924,92), root:(929,136),
    state 0x10, keycode 241 (keysym 0x1008ff4b, XF86LaunchB), same_screen YES,
    XLookupString gives 0 bytes:
    XFilterEvent returns: False

Fn+F9
KeyRelease event, serial 34, synthetic NO, window 0xe00001,
    root 0x7d, subw 0x0, time 30668910, (935,18), root:(940,62),
    state 0x10, keycode 207 (keysym 0x0, NoSymbol), same_screen YES,
    XLookupString gives 0 bytes:
    XFilterEvent returns: False

Comment 12 Forgotten User vXTZVacoSi 2009-06-08 13:36:36 UTC

Instead of just copy and pasting my xev here as well, this is also broken on T400
keycodes are the same, just Symbol is missing

Isn't this a hal issue?
/usr/share/hal/fdi/information/10freedesktop/30-keymap-module-thinkpad-acpi.fdi provides info for the special keys.

The broken backlight control is kernel related afaik from thinkpad-linux list.

Comment 13 Forgotten User vXTZVacoSi 2009-06-08 14:01:31 UTC

Closing here, T and R series share same firmware / keyboards

*** This bug has been marked as a duplicate of bug 462878 ***

Comment 14 Jan Vinárek 2009-06-08 14:27:59 UTC

Then how come some issues in bug #462878 are different, for instance sleep button works on thinkpad r61i and doesn't on t61.