Bug 803907 - Keyboard is non-functional in gdm-simple-greeter
Keyboard is non-functional in gdm-simple-greeter
Product: Fedora
Classification: Fedora
Component: gdm (Show other bugs)
x86_64 Linux
unspecified Severity high
: ---
: ---
Assigned To: Ray Strode [halfline]
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2012-03-15 19:02 EDT by David M. Lloyd
Modified: 2012-08-07 14:31 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2012-08-07 14:31:50 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description David M. Lloyd 2012-03-15 19:02:25 EDT
Description of problem:
When the GDM login screen appears, it comes up normally, however it doesn't accept keyboard input.  Instead you get beeps when you hit keys (including modifier keys).  You cannot even do a ctrl-alt-backspace or ctrl-alt-Fn to switch consoles.  Interestingly though, if you hit shift 5 times the sticky keys dialog comes up.

Version-Release number of selected component (if applicable):

How reproducible:
Difficult to say.  It happens on my computer, not on my wife's, which is also an Intel F15 x86_64 system.  It was also reported in a completely different distro here: http://forums.linuxmint.com/viewtopic.php?f=55&t=93286&p=543409

Steps to Reproduce:
1. Get to login screen
2. Try to type your password
3. Fail
Actual results:
Beeps when you hit keys.

Expected results:
Keystrokes work.

Additional info:
Can be worked around by enabling automatic login in GDM.  Not very wise for security reasons, but it might give a hint as to what's going on.  Switching to XDM or similar also works, though if you choose XDM then NetworkManager may not work (and presumably other things as well) if you don't use Gnome due to Gnome security stuff not being started.
Comment 1 David M. Lloyd 2012-03-15 19:03:33 EDT
Forgot to give my GDM info:

Name        : gdm
Arch        : x86_64
Epoch       : 1
Version     : 3.0.4
Release     : 1.fc15
Size        : 5.8 M
Repo        : installed
From repo   : updates
Summary     : The GNOME Display Manager
URL         : http://download.gnome.org/sources/gdm
License     : GPLv2+
Description : GDM provides the graphical login screen, shown shortly after boot up,
            : log out, and when user-switching.
Comment 2 David M. Lloyd 2012-03-15 19:14:18 EDT
Possible related incidents in other distros:

https://bbs.archlinux.org/viewtopic.php?id=132955 - similar symptoms but hard to say if it's the same problem
http://forum.elivecd.org/read.php?12,2144,2144 - might be a clue?
Comment 3 Fedora End Of Life 2012-08-07 14:31:52 EDT
This message is a notice that Fedora 15 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 15. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. At this time, all open bugs with a Fedora 'version'
of '15' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that
we were unable to fix it before Fedora 15 reached end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora, you are encouraged to click on
"Clone This Bug" (top right of this page) and open it against that
version of Fedora.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

The process we are following is described here:

Note You need to log in before you can comment on or make changes to this bug.