Problem assigning hotkey to XF86AudioMedia
I have quite a strange problem: I am currently using SUSE 10.1/64Bit and recent KDE Packages for this distro (which are since today 3.5.3, but the problem was already there with all previous KDE packages for SUSE 10.1). Everything worked perfectly with SUSE 10.0. I cannot set the key XF86AudioMedia on my Logitech Cordless Desktop to start Amarok (or any other application, by the way)! All other "multimedia"-keys on the keyboard (as far as they are recognized by the kernel) can be set up via the KDE Control Center to do something. The key is, however, recognized. Both "xev" and the KDE Control Center show "XF86AudioMedia" when it is pressed. But the action assigned to this key, doesn't matter which kind of action, won't be executed. I tried several of the possibilites in the KDE Control Center to assign Hotkeys. BTW the way hotkeys are handled in KDE is quite a mess, several possibilities to set this up, and it's not quite clear how they interact. Any idea what might be going wrong?
On Wednesday 31 May 2006 1:55 am, Alex wrote:
I have quite a strange problem:
I am currently using SUSE 10.1/64Bit and recent KDE Packages for this distro (which are since today 3.5.3, but the problem was already there with all previous KDE packages for SUSE 10.1). Everything worked perfectly with SUSE 10.0.
I cannot set the key XF86AudioMedia on my Logitech Cordless Desktop to start Amarok (or any other application, by the way)! All other "multimedia"-keys on the keyboard (as far as they are recognized by the kernel) can be set up via the KDE Control Center to do something.
The key is, however, recognized. Both "xev" and the KDE Control Center show "XF86AudioMedia" when it is pressed. But the action assigned to this key, doesn't matter which kind of action, won't be executed.
I tried several of the possibilites in the KDE Control Center to assign Hotkeys. BTW the way hotkeys are handled in KDE is quite a mess, several possibilities to set this up, and it's not quite clear how they interact.
Any idea what might be going wrong?
When I've seen this for other key sequences I was trying to setup it was due to that key sequence already being assigned to something else somewhere in the KDE hotkey assigning system. The trick was finding it! Once unassigned, my key combos worked until the next KDE update, SUSE Linux update, etc. Stan
Am Mittwoch, 31. Mai 2006 22:44 schrieb S Glasoe:
On Wednesday 31 May 2006 1:55 am, Alex wrote:
.... I cannot set the key XF86AudioMedia on my Logitech Cordless Desktop to start Amarok (or any other application, by the way)! All other "multimedia"-keys on the keyboard (as far as they are recognized by the kernel) can be set up via the KDE Control Center to do something. .... When I've seen this for other key sequences I was trying to setup it was due to that key sequence already being assigned to something else somewhere in the KDE hotkey assigning system. The trick was finding it! Once unassigned, my key combos worked until the next KDE update, SUSE Linux update, etc.
That's what I thought, too. But I really don't find any place where XF86AudioMedia is assigned to something else - at least in the different possibilities accessible by the KDE control center (components in German: Kontrollleisten, Tastaturkombinationen, Tastaturkürzel). Is there somewhere else to look? A search for the sting "XF86AudioMedia" in ~/.kde , /opt/kde3/share and /etc/opt/ turned up nothing but my own khotkeysrc. And on some other occasion when I tried to use a key already in use for some other hotkey (XF86Homepage), there was a warning requester. I don't have that with XF86AudioMedia. I already tried deleting the khotkeysrc (very cryptic config file, btw) and disabling kmilo, which is one more programm dealing with the keyboard. btw, I hope that the mess concerning hotkeys will be cleaned up in some future KDE version - why is this chaos necessary???
I'll try to push my problem up on the list ... ;-) Am Mittwoch, 31. Mai 2006 08:55 schrieb Alex:
I have quite a strange problem:
I am currently using SUSE 10.1/64Bit and recent KDE Packages for this distro (which are since today 3.5.3, but the problem was already there with all previous KDE packages for SUSE 10.1). Everything worked perfectly with SUSE 10.0.
I cannot set the key XF86AudioMedia on my Logitech Cordless Desktop to start Amarok (or any other application, by the way)! All other "multimedia"-keys on the keyboard (as far as they are recognized by the kernel) can be set up via the KDE Control Center to do something.
The key is, however, recognized. Both "xev" and the KDE Control Center show "XF86AudioMedia" when it is pressed. But the action assigned to this key, doesn't matter which kind of action, won't be executed.
I tried several of the possibilites in the KDE Control Center to assign Hotkeys. BTW the way hotkeys are handled in KDE is quite a mess, several possibilities to set this up, and it's not quite clear how they interact.
Any idea what might be going wrong?
Have run "xev" to see if the event is actually being sent by X? Usually the extended keys on a logitech keyboard need to be "set" in the OS keyboard driver. And then a map from these to the relevant X events need to be made. Fimmtudaginn 8 júní 2006 06:52 skrifaði Alex:
I'll try to push my problem up on the list ... ;-)
Am Mittwoch, 31. Mai 2006 08:55 schrieb Alex:
I have quite a strange problem:
I am currently using SUSE 10.1/64Bit and recent KDE Packages for this distro (which are since today 3.5.3, but the problem was already there with all previous KDE packages for SUSE 10.1). Everything worked perfectly with SUSE 10.0.
I cannot set the key XF86AudioMedia on my Logitech Cordless Desktop to start Amarok (or any other application, by the way)! All other "multimedia"-keys on the keyboard (as far as they are recognized by the kernel) can be set up via the KDE Control Center to do something.
The key is, however, recognized. Both "xev" and the KDE Control Center show "XF86AudioMedia" when it is pressed. But the action assigned to this key, doesn't matter which kind of action, won't be executed.
I tried several of the possibilites in the KDE Control Center to assign Hotkeys. BTW the way hotkeys are handled in KDE is quite a mess, several possibilities to set this up, and it's not quite clear how they interact.
Any idea what might be going wrong?
xev output seems quite normal to me, the XF86AudioMedia-Key is definitely recognized. Even the KDE control center recognizes the key, if I want to assign it to some action: The problem is that then no action assigned to this key will be ececuted... Here the xev output, maybe this gives someone a hint what's going wrong: KeyPress event, serial 31, synthetic NO, window 0x3000001, root 0x108, subw 0x0, time 4431908, (29,72), root:(883,99), state 0x0, keycode 237 (keysym 0x1008ff32, XF86AudioMedia), same_screen YES, XKeysymToKeycode returns keycode: 129 XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: False KeyRelease event, serial 31, synthetic NO, window 0x3000001, root 0x108, subw 0x0, time 4432014, (29,72), root:(883,99), state 0x0, keycode 237 (keysym 0x1008ff32, XF86AudioMedia), same_screen YES, XKeysymToKeycode returns keycode: 129 XLookupString gives 0 bytes: Am Donnerstag, 8. Juni 2006 07:28 schrieb Orn E. Hansen:
Have run "xev" to see if the event is actually being sent by X? Usually the extended keys on a logitech keyboard need to be "set" in the OS keyboard driver. And then a map from these to the relevant X events need to be made.
Fimmtudaginn 8 júní 2006 06:52 skrifaði Alex:
I'll try to push my problem up on the list ... ;-)
Am Mittwoch, 31. Mai 2006 08:55 schrieb Alex:
I have quite a strange problem:
I am currently using SUSE 10.1/64Bit and recent KDE Packages for this distro (which are since today 3.5.3, but the problem was already there with all previous KDE packages for SUSE 10.1). Everything worked perfectly with SUSE 10.0.
I cannot set the key XF86AudioMedia on my Logitech Cordless Desktop to start Amarok (or any other application, by the way)! All other "multimedia"-keys on the keyboard (as far as they are recognized by the kernel) can be set up via the KDE Control Center to do something.
The key is, however, recognized. Both "xev" and the KDE Control Center show "XF86AudioMedia" when it is pressed. But the action assigned to this key, doesn't matter which kind of action, won't be executed.
I tried several of the possibilites in the KDE Control Center to assign Hotkeys. BTW the way hotkeys are handled in KDE is quite a mess, several possibilities to set this up, and it's not quite clear how they interact.
Any idea what might be going wrong?
Fimmtudaginn 8 júní 2006 07:42 skrifaði Alex:
xev output seems quite normal to me, the XF86AudioMedia-Key is definitely recognized.
After doublechecking on my own system, I have to concur that I am having the same problem with KDE 3.5.3 (I usually start by pressing the play button).
Thanks for cross-checking... that means that not only my machine is behaving weird. Is this more a KDE or a SUSE error? Am Freitag, 9. Juni 2006 07:06 schrieb Orn E. Hansen:
Fimmtudaginn 8 júní 2006 07:42 skrifaði Alex:
xev output seems quite normal to me, the XF86AudioMedia-Key is definitely recognized.
After doublechecking on my own system, I have to concur that I am having the same problem with KDE 3.5.3 (I usually start by pressing the play button).
participants (3)
-
Alex -
Orn E. Hansen -
S Glasoe