custom keyboard shortcut inactive on login

[Brandon Williams]

Binary package hint: gnome-control-center

On the Dell mini, the wireless key (Fn+2) issues keycode 171, XF86AudioNext. I have configured a 'Custom Shortcut' with the 'Keyboard Shortcuts' capplet that should run a command to toggle the WLAN state when I press the wireless key. This shortcut is inactive after I log in. If I open the 'Keyboard Shortcuts' capplet, change the short key, and then change it back to XF86AudioNext, the wireless key functions as expected in this session. However, if I log out and log back in, the shortcut key no longer functions and I have to re-enable again in the capplet.

[Brandon Williams (opensource-subakutty)]

As a work-around, I wrote this script:

#!/bin/sh
setxkbmap
gconftool-2 --set --type=string /desktop/gnome/keybindings/custom0/binding XF86WLAN
gconftool-2 --set --type=string /desktop/gnome/keybindings/custom0/binding XF86AudioNext

I then configured the script to run at login using the 'Startup Applications' capplet. Neither setxkbmap nor the set/reset operation on its own appeared to be adequate. Both were required.

[Brandon Williams (opensource-subakutty)]

I experimented a little more and discovered that, no, setxkbmap is not required. The two calls to gconftool-2 are enough to enable the desired shortcut.

[Luca Ferretti (elle.uca)]

I played a little on this. Setting the shortcut to a different keycode/keybinding (e.g. Alt+F12) gnome-control-center (or maybe better gnome-settings-daemon) seems able to remember the value after logout/login and even after reboot.

Instead, setting the keycode/keybindint to Fn+2, I think you simple have to set again the value on login, i.e. your workaround script should be simply

----------------------------
#!/bin/sh
gconftool-2 --set --type=string /desktop/gnome/keybindings/custom0/binding XF86AudioNext
----------------------------

Could be good perform more tests, using a "working" keycode on a custom shortcut. I'll try on m standard keybord in next days

 PS I've just opened a separate bug (#375656) for wrong keycode hitting Fn+2, following instructions provided here: https://wiki.ubuntu.com/Hotkeys/Troubleshooting

[Brandon Williams (opensource-subakutty)]

For me, the call to setxkbmap was required.

I'm not sure whether both calls to gconftool-2 were required. I will try to remember to try this again later.

[Brandon Williams (opensource-subakutty)]

Oops ... no ... setxkbmap is not required, but both calls to gconftool-2 _are_ required. With only the one that Luca recommends, the workaround does not achieve the desired effect.

[Sebastien Bacher (seb128)]

Thank you for your bug report, is the issue specific to some combinaisons? Do you have xfce installed?

[Brandon Williams (opensource-subakutty)]

This is a problem with gnome + metacity + UNR (I don't know whether it also happens without UNR). I believe that it is specific to some key combinations. The only key combination that I am aware of that is problematic is the one I indicated in the bug report. It might be a problem for some others, too, I'm not sure.

[Jerone Young (jerone)]

@Brandon,
            There is no issue here. Try a 10.04 live image. These are mapped by default correctly.

[Ilya Konyakhin (ilyakon)]

Bug still exits.
Additional info is here:
https://bugs.launchpad.net/netbook-remix/+bug/295216

[penalvch (penalvch)]

Brandon Williams, thank you for reporting this and helping make Ubuntu better. Jaunty reached EOL on October 23, 2010.
Please see this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We were wondering if this is still an issue in a supported release? If so, could you please test for this with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the kernel in the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested and remove the tag:
needs-upstream-testing

This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the text:
needs-upstream-testing

If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested.

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested.

If you are unable to test the mainline kernel, please comment as to why specifically you were unable to test it and add the following tags:
kernel-unable-to-test-upstream
kernel-unable-to-test-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested.

Please let us know your results. Thank you for your understanding.

Helpful Bug Reporting Tips:
https://help.ubuntu.com/community/ReportingBugs

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]