https://bugzilla.novell.com/show_bug.cgi?id=371927
User hmacht@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=371927#c8
--- Comment #8 from Holger Macht
(In reply to comment #6 from Holger Macht)
(In reply to comment #5 from JP Rosevear)
Yes, I'm beyond alpha2, I have: kernel-default-2.6.25-rc5.git3.6
The setting "stuck" after I echo'ed to enable it. I checked and I also have the problem described in bug 370220.
Do you mean that you cannot disable bluetooth anymore after enabling it once?
No, just that its not persisten.
Right, 'disabled' is the default, which is the correct choice IMHO.
We currently have no support for enabling/disabling this setting via a FN-Keypress. This was done by a powersave script in the past, which got removed.
Can we resurrect it into PM utils? If not, what desktop app makes the most sense to hook it up to.
I think either some standard way in gnome or KDE to assign the appropriate keycode to an action, or of course, gnome-bluetooth and kbluetoothd. But that's not possible at the moment, see below...
Can you also please take a look at /proc/bus/input/devices and look for 'ThinkPad'. In this section, you'll find something like 'S: Sysfs=/class/input/input6'. Now please do 'evtest /dev/input/event6' (with the correct event number figured out before). Now press FN-F5 and report what you get. Thanks.
I: Bus=0019 Vendor=1014 Product=5054 Version=4101 N: Name="ThinkPad Extra Buttons" P: Phys=thinkpad_acpi/input0 S: Sysfs=/devices/virtual/input/input5 U: Uniq= H: Handlers=kbd event5 B: EV=13 B: KEY=1e8c0000 0 2 100100 0 0 0 1000b 2000 0 1004000 0 0 0 1 B: MSC=10
and: gambit:~ # evtest /dev/input/event5 Input driver version is 1.0.0 Input device ID: bus 0x19 vendor 0x1014 product 0x5054 version 0x4101 Input device name: "ThinkPad Extra Buttons" Supported events: Event type 0 (Sync) Event type 1 (Key) Event code 0 (Reserved) Event code 142 (Sleep) Event code 152 (Coffee) Event code 205 (Suspend) Event code 224 (Brightness down) Event code 225 (Brightness up) Event code 227 (?) Event code 240 (Unknown) Event code 360 (Vendor) Event code 372 (Zoom) Event code 385 (Radio) Event code 466 (?) Event code 467 (?) Event code 471 (?) Event code 473 (?) Event code 474 (?) Event code 475 (?) Event code 476 (?) Event type 4 (Misc) Event code 4 (ScanCode) Testing ... (interrupt to exit) Event: time 1206456170.465429, type 1 (Key), code 385 (Radio), value 1 Event: time 1206456170.465440, -------------- Report Sync ------------ Event: time 1206456170.465443, type 1 (Key), code 385 (Radio), value 0 Event: time 1206456170.465446, -------------- Report Sync ------------
So it's keycode 385. Unfortunately, the X server is not capable to handle keycodes above 255, so it doesn't show up in X (xev). However, I'm about to create a feature (FATE) for this for SLE11. Maybe this is even possible for openSUSE 11.0, but that's not in my responsibility. In the meanwhile, we could readd some script, somewhere. Maybe a plain acpid script if we do not get the feature for 11.0. pm-utils wouldn't be suitable for that. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.