After upgrading to initscripts-4.70, the keyboard intermittently locks up
in GNOME. All is well until without warning, any keypress causes a BEEP,
and is otherwise ignored. ALL keypresses beep, including any attempt to go
to another console. The mouse still works. Logging out (with the Gnome
logout button) and logging back in restores the keyboard, making this
clearly a GNOME or ENLIGHTENMENT problem.
Note that unplugging the keyboard and replugging the keyboard in has no
effect. Only logging off brings the keyboard back, allowing one to log
back in or switch to another console.
Since downgrading to initscripts-4.68, the problem has not recurred. The
problem first occurred shortly after I upgraded to 4.70.
You might try right-clicking on a gnome-terminal, and
seeing if 'secure keyboard' has been selected.
There's nothing in the initscripts update that should
affect the keyboard one way or another.
I am having the same problems with gnome-terminals since updating to RH6.1. The
terminal completely freezes and the only solution I have found is to kill it. I
havent seen any particular pattern as to when it occurs.
I have RH6.1 on a Gateway 2500 Solo Laptop.
I have gnome-core-1.0.39-10.
FYI ... this never happened before installing 4.70, and it has not happened at
all since I downgraded to 4.68. It's been a week since I downgraded and of
course I'd had Red Hat 6.1 installed for about a month before upgrading to
I agree that this doesn't seem to make sense, but initscripts is the only
This happened several times in the fewer-than-24 hours I had initscripts-4.70
I just figured out what is causing my gnome-terminal's to freeze - Shift+Tab.
Fortunately, Shift+Tab also
undoes the problem. I assume this is a bug and not a feature, or perhaps there
is some reason why
shift+tab should freeze the terminal.
Again, I have gnome-core-1.0.39-10 and initscripts-4.48-1.
Please get the GNOME errata from the Red Hat. This problem was fixed in
gnome-core after the 1.0.40 release.
Shift+Tab is normally used to switch widget focus within an application, and was
not being caught by only-one-thing-to-focus-on gnome-terminal.
I am pretty sure this problem has nothing to do with initscripts.
*** Bug 11330 has been marked as a duplicate of this bug. ***