The eject button does not work on Dell Inspiron 510m in KDE

[mmaurer]

Binary package hint: hotkey-setup

On a Dell Inspiron 510m the hotkey (Fn+F10) that should eject the DVD-drive does not work in KDE.
Though it does work in Gnome. (As documented in Bug #33778)

I don't know if it helps, but this is my xev output for this key:

KeyRelease event, serial 28, synthetic NO, window 0x3c00001,
    root 0x4d, subw 0x0, time 21003931, (725,532), root:(728,556),
    state 0x0, keycode 204 (keysym 0x1008ff2c, XF86Eject), same_screen YES,
    XLookupString gives 0 bytes:
    XFilterEvent returns: False

[Alex Lowe (lengau)]

This Keycode (204) is the same for Apple USB keyboards. This bug is confirmed in Kubuntu Gutsy with all the latest updates.

I have attached a version of khotkeysrc (~/.kde/share/config/khotkeysrc) that only has this event in it. It's not actually a patch (though I've marked it as a patch because it fixes the problem).

If you have other input actions (kcontrol -> Regional & Accessibility -> Input Actions), you should add it yourself.
You can do this by going there (you'll need to open kcontrol through the run command) and making a new action of type "Keyboard Shotcut -> Command/URL (simple)", using your Eject key for the shortcut, and 'kdeeject cdrom' as the command.

I would suggest adding khotkeysrc back to kubuntu-default-settings with this key included. (This bug is really a kubuntu-default-settings bug in that case).

[Alex Lowe (lengau)]

I've attached a fix, but it's not final (I don't know what else is in the file)

[mmaurer (mbfmaurer)]

Thanks for your efforts.

I have attached my khotkeysrc to give you an idea what mine looks like.

I have also tested your khotkeysrc and it works for me :-).

If you need anything else, let me know.

[Alex Lowe (lengau)]

Thanks.
This khotkeysrc should be included in kubuntu-default-settings. It is based on the one that you gave me, which seems to be what's created by KDE. We could also put this into the file that creates the file (I don't know which file that is).

[mmaurer (mbfmaurer)]

Well not that I would really know, but wouldn't it be much better to detect the system during installation and only use a modified version of the khotkeysrc if the system is one where the keycode 204 is supposed to open the CD-drive.

Unless of course this is some kind of standardized keycode for opening CD-drive the same keycode could be used for different things on different keyboards.

I guess all I am trying to say is if your Khotkeysrc is put by default on every computer running kubuntu it could break special keys on other keyboards by fixing the bug for me.

On that note
 /usr/share/hotkey-setup/dell.hk seems to be a table actually describing dell specific keys and it lists Fn+F10 as $KEY_EJECTCD

[Daniel Hahler (blueyed)]

There's nothing committed for Ubuntu.
khotkeyrc has been removed in Gutsy (from looking at the changelog).
Anthony, can you say something about it? Or anyone else? :)

[Rich Johnson (nixternal)]

Buttons aren't anywhere in the k-d-s package, I just spent a bit looking for where all of the files are coming from. xkb-data has a list of keyboards and such, however kmilo does some modification to the keyboard as well. This same issue is also valid for the E1505.

[Yuriy Kozlov (yuriy-kozlov)]

"In Progress"? Is anyone still/currently working on this? Alex?

[Jonathan Thomas (echidnaman)]

KMilo is dead in Intrepid (key support has been patched in to the relevant applications) so this shouldn't be an issue anymore.

[pauls (paulatgm)]

I've just done a fresh install on my Dell Inspiron E1505 of intrepid ubuntu. The same problem is back in both gnome and kde. The Fn-F10 (eject) combination does nothing.

xev with the Fn-F10 combo shows:

KeyRelease event, serial 37, synthetic NO, window 0x3a00001,
    root 0x8b, subw 0x0, time 10826132, (-935,768), root:(206,819),
    state 0x0, keycode 170 (keysym 0x1008ff2c, XF86Eject), same_screen YES,
    XKeysymToKeycode returns keycode: 169
    XLookupString gives 0 bytes:
    XFilterEvent returns: False

It seems the key 170 is properly assigned to XF86Eject, but gnome does not seem to want to respond to XF86Eject.

Is there any way to manually fix this in gnome on 8.10?

regards

[pauls (paulatgm)]

This is still a problem on jaunty with kde4.2.1. It works ok on gnome on jaunty, but does nothing on kde. Any ideas how to fix?