After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 323690 - gnome-settings-daemon grabs the keyboard if an unknown key is present in the gconf database
gnome-settings-daemon grabs the keyboard if an unknown key is present in the ...
Status: RESOLVED FIXED
Product: gnome-control-center
Classification: Core
Component: [obsolete] Keybinding
2.10.x
Other All
: High critical
: ---
Assigned To: Control-Center Maintainers
Control-Center Maintainers
Depends on:
Blocks:
 
 
Reported: 2005-12-10 03:22 UTC by Philippe Troin
Modified: 2006-06-24 17:43 UTC
See Also:
GNOME target: ---
GNOME version: 2.9/2.10

Attachments
Patch to gnome-settings-daemon (1.63 KB, patch)
2005-12-10 03:23 UTC, Philippe Troin 		none Details | Review

Description Philippe Troin 2005-12-10 03:22:31 UTC 
Steps to reproduce:
As a test user:

  gconftool-1 -t string -s /apps/gnome_settings_daemon/keybindings/www Help

(this assumes that your keyboard has no Help key)

Logout from your gnome session if you were logged in, and log back in.
Open a window and try typing.  It won't work.

---

How this can happen in real life?

 1. Machine A and B share home directories.
 2. Machine A has an "Internet" keyboard, B has a standard 104-key keyboard.
 3. Login on A, go to Desktop->Preferences->Keybindings
 4. Set a multimedia key.
 5. Now login on B. You now have a keysym which is defined and known to XFree,
but which has no keycode.  The bug then happens.

I've traced it to gnome-settings-daemon call XGrabKey with a 0 keycode.



Stack trace:


Other information:
Comment 1 Philippe Troin 2005-12-10 03:23:25 UTC 
Created attachment 55831 [details] [review]
Patch to gnome-settings-daemon

This patch should apply on CVS head, as far as I can tell from cvsview.
Comment 2 Writser Cleveringa 2005-12-10 17:15:25 UTC 
I had this problem too after selecting another keyboard. My solution was rm -rf
~/.gconf.. Very annoying, thanks for the patch!
Comment 3 Rodrigo Moya 2005-12-12 12:01:37 UTC 
Ok, patch applied to HEAD. Writser, can you confirm it fixed it for you?
Comment 4 Philippe Troin 2006-06-24 17:43:37 UTC 
I confirm 2.14.2 to work fine for me.
Therefore marking as Fixed.