| Summary: | Gnome gconf added keybindings "magically" remove all keycodes (leaving a useless keyboard) | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | voidptr <voidptr> |
| Component: | [OLD] GNOME | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
| Status: | RESOLVED NEEDINFO | ||
| Severity: | normal | ||
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | x86 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
And what happens if you actually use the gnome provided application to rebind those keys? we suggest you use the gnome capplet to handle this. no reply, so closing |
After adding some extra keycodes via xmodmap everything worked fine. After a reboot (probably the same with logout/login ofcourse) the keyboard was unresponsive. Removing ~/.gconf/apps/gnome_settings_daemon/keybindings/ resulted in a working configuration. ("cured") After adding the same keycodes again with gconf-editor the same "result" was achieved.. keyboard "unresponsive"... actually I do see the cursor blink when pressing a key so I know the scancode arrives... but doesn't know what to "produce" I use the current "x86" gnome (this weekend). Reproducible: Always Steps to Reproduce: 1.Add a keycode via xmodmap or gconf-editor (apps/gnome_settings_daemon/keybindings) 2.Relogin 3.Watch you being only able to use your mouse :) Actual Results: Unresponsive keyboard Expected Results: Responsive keyboard ;) Not "erase/overwrite" the keycodes... (I assume it did something like that) The keys added were: keycode 174, 176, 160, 236, 178 corresponding respectively: volumeup, volumedown, mute, www, mail (i could have mixed a few but it's not that important)