GNOME Bugzilla – Bug 103584
using keyboard shortcuts to open applications sometimes blocks keyboard input
Last modified: 2005-01-26 17:11:10 UTC
Description of Problem: I have configured metacity so that pressing break brings up an xterm by setting keybindings with gconf-editor. Occasionally, when I press break to bring up an xterm, it will bring up 3 of them and then block keyboard input to any application. I can recover control of the keyboard by closing the xterms it opened, clicking on the desktop, pressing break, clicking again on the desktop and again pressing break. Alternatively changing to a console and then back to X will fix the problem. Steps to reproduce the problem: 1. Configure a keybinding with gconf-editor to load xterm when break is pressed. 2. press break to open an xterm 3. work with this shortcut for some time, eventually the aforementioned bug will surface. It seems to occur more frequently when the machine is under heavy load. Actual Results: varied. Expected Results: 3 xterms and blocked keyboard input. How often does this happen? Currently I have this occur about every 3rd or 4th time I press break. It is not consistent however. Additional Information: n/a
If you open "xev" while keyboard input is locked, does it receive key events? If so can you post the output from xev when you press some keys while locked and while not locked? Can you focus windows, just not type in them?
I can reproduce by holding down my "Menu" key, which I have bound to launch an xterm. It launched about 25 xterms and then my keyboard was completely dead; no Ctrl-Alt-Backspace, no Ctrl-Alt-F1. Also, the gnome menu stopped working. I was able to restore only by sshing in from a different computer and killing metacity.
And I could focus windows. I suspect that metacity had a keyboard grab. And an, um, gnome-menu grab. Yea.
does the log file show metacity taking a grab and not releasing it? And if so, what else is happening in the log file that causes that?
I have the same problem (with metacity 2.4.55 and 2.6.2), and it seems this only happens if my system is under heavy load!
It seems that this bug is fixed in 2.6.5. I can't reproduce it any longer.
See also bug 143154, which I believe may be a duplicate. Julien: Thanks for following up; I'm going to mark this as fixed. If anyone can reproduce with a recent version, feel free to reopen.
*** Bug 143154 has been marked as a duplicate of this bug. ***