GNOME Bugzilla – Bug 134613
Keybindings cause keyboard to be unusable in GNOME
Last modified: 2017-04-08 07:22:25 UTC
Description of Problem: I have an IBM Rapid Access II. When I bind the audio keys, the only extras I use, I can use them to control rhythmbox only for the rest of that session. When I log in again, the keyboard cannot be used while in GNOME -- e.g typing into gnome-terminal just causes the cursor to flash, but nothing is typed. I've also tried it in the run dialog and mini-commander. Resolved when I log out and rm -rf ~/.gconf/apps/gnome_settings_daemon/keybindings Steps to reproduce the problem: 1. Select IBM Rapid Access II 2. Bind audio keys 3. Log out then back in Actual Results: No keyboard input is recieved by GNOME apps Expected Results: Being able to type How often does this happen? Every time Additional Information: control-center-2.5.3, all GNOME stuff is latest available on ftp Slackware 9.1, kernel 2.4.24, gcc 3.2.3
Sergey this looks like a dup. Any thoughts ?
I have experienced the same behavior. I open they keybindings capplet, assign my extra keys (volume, prev/play/stop/next, www, mail) on HP XE3GF laptop to corresponding actions. I see XF86WWW, XF86AudioNext etc. as assigned keys. Those keys do not start to work, though. After I close they capplet, keyboard stops working. When I type something in terminal, cursor flashes but nothing is entered, nothing happens when I type into any other text entry fields. Only modifiers (Alt, Ctrl, Shift) mean something, i.e. I can drag windows with Alt+mouse, and default X shortcuts (Ctrl+Alt+<num>, Ctrl+Alt+Del) work. I use gconftool-2 --recursive-unset "/apps/gnome_settings_daemon/keybindings" from console to regain my keyboard. This happens only to my account which was used with GNOME 2.4, so has old settings. I used acme earlier, but it is uninstalled now. To fresh accounts everything works as expected, but I can't find what settings should I delete to make my account work the same.
reopening, since i can't see any pending information requests
Well, I've just had another look at it as I've also had problems with keyboard repeat settings [got float, expected int for rate... and doubled kkeeyypprreesssseesssseessss] and a warning that there are problems with xbd config. Deleted ~/.gconf* && /etc/gconf, recompiled GConf 2.6.0 and control-centre-2.6.0.3 && libgnome 2.6.0 [just to replace some schemas] -- all seems okay now. I guess there's some problem with the upgrade procedure for the keyboard stuff and old system schemas are left around/not updated. Deleting just ~/.gconf, I always got the same problems. Long story short -- my fault(?)
Oh, and I don't know if it matters, but I install through the checkinstall program. Can that affect the upgrade procedure?
I built 2.6.0 from source myself and have the same problem. The extra keys on my Logitech keyboard produce keycodes like 144, 153, 162 and 164 (previous, next, play, stop). They are not bound to any keysyms so when entered into the Keyboard Shortcuts control panel they are shown as 0x90 etc. The only actions I can bind these keys to without losing all keyboard functionality are Play, Stop playback, Skip to Previous and Skip to Next. If these 0xsomething keysyms are bound to the other actions like Volume mute all keyboard functionality is lost UNTIL any (!) keyboard shortcut is changed using the control panel. However, when logging out and logging in again, the keyboard is broken again if these keysyms are bound. Naturally removing ~/.gconf/apps/gnome_settings_daemon/keybindings/ fixes the problem since all bindings are removed. This is how it seems to be but I'm not 100% sure since I haven't tried every possible combination. I also have not given keysyms to the keycodes using xmodmap and tested whether it works better if the keys are not "0x90" but "F13", for example.
Forgot to mention that I completely removed GNOME 2.4 before installing 2.6 and also completely removed ~/.gnome2 and ~/.gconf before logging in for the first time.
Putting this on the 2.6.1 milestone, seems it's fairly major and biting a lot of people.
*** This bug has been marked as a duplicate of 135031 ***
Reopening; this may or may not be the same bug but we're getting reports for 2.6.0 so one of these bugs has to stay open. I choose this one :) but with a heavy pointer at bug 135031 at potentially providing useful information.
Reverting the patch from bug 135031 seems to fix the problem here... apparently, it fixes shortcuts to keys with keysyms, but breaks those to keys without keysyms? (See also http://lists.debian.org/debian-gtk-gnome/2004/debian-gtk-gnome-200404/msg00019.html) Makes any sense?
Michel : I'm not seeing the problem. Can you expand on how and what you see ? I've patched cvs to allow you to assign bindings to keys with no keysym but can not freeze my keyboard. The early pieces of this report are likely unrelated.
I'm getting this too! Only with my remote control, which is recognized as an extention to my keyboard. I'm running gnome 2.6 from Fedora Devel.
Can michel or sigge replicate this problem with 2.6.1 ?
No, 2.6.1 works fine here. (Except that gnome-settings-daemon crashes when I press the power button to log out, but that's probably a different story)
Please file the crash as a distinct bug report. I'll assume this problem is fixed and close it.
Created attachment 349514 [details] briefly
Comment on attachment 349514 [details] briefly Garbage.