Red Hat Bugzilla – Bug 50930
Keyboard doesn't work in Failsafe mode.
Last modified: 2007-04-18 12:35:29 EDT
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.5; Windows 98)
Description of problem:
When I start a failsafe session from the kdm login screen, my mouse works;
however, my keyboard. The focus is on the console, meaning the cursor is
in the console.
Steps to Reproduce:
1.Login on kdm login screen into failsafe session
2.Place focus on the console
3.Try to type in the console.
Actual Results: No ability to type in the failsafe console. Even when
focus is on the console.
Expected Results: Ability to type in the console at the command prompt.
We (Red Hat) should try to fix this for the next release.
Don't see how this has anything to do with X... KDE issue.
See Bug#: 50847 for the assesment by email@example.com, who told me that it was
an X problem and not a kde problem.
I can't reproduce it, and since KDE isn't running, I don't think it's a KDE
Might be a usability problem though: Are you aware of the fact that in twm
(which is used in the failsafe session), you need to move the mouse over the
window you're trying to type in?
Yes, I am arare that I need to have the mouse cursor over the window that I am
typing in; however, it doesn't change anything. The window seems to get the
focus when the cursor is over the window, but I still cannot type.
This sounds like this is related to the problem I found in Bug 51615.
"Whenever the X server is restarting, either after a CTRL-ALT-Backspace or
normal logout and subsequent X restart, if you attempt to switch to a
virtual terminal with CTRL-ALT-F[1-6] during this time, X appears to load
and display properly. It does not respond to keyboard input."
(I'm quite sure this is an X problem, not KDE.)
Looks a lot like http://bugs.kde.org/db/30/30344.html, by the way.
Do you still experience this problem in Red Hat Linux 7.2, or our official
erratum release of XFree86 4.1.0-15? I'm not able to reproduce it yet.
If the problem persists, I'll have to try it on a duplicated setup.
No, it doesn't happen in 7.2. Seems to work fine now.
Ok, thanks. Closing bug as fixed in Enigma (7.2).