GDM dies on initial login attempt when passed specific keypresses in password field
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gdm (Ubuntu) |
Invalid
|
Medium
|
Ubuntu Desktop Bugs |
Bug Description
Binary package hint: gdm
Strange issue here. On a fresh boot GDM will die and restart when entering "-12" (no quotes) in any part of the password field box. Additionally, other key sequences appear to activate the scroll-lock on the keyboard. After GDM auto-restarts the password dialog works as expected, however this issue is constantly reproducible on each subsequent reboot. Testing on an IBM A21p and I have verified this with two separate partition installs of a fully updated Ubuntu daily-live (2010.02.10). This particular PC works correctly with a current install of Karmic.
I've included a few logs - not sure if there is anything useful in them...
ProblemType: Bug
Architecture: i386
Date: Fri Feb 12 11:24:47 2010
DistroRelease: Ubuntu 10.04
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha i386 (20100211.1)
Package: gdm 2.29.6-0ubuntu3
ProcEnviron:
LANG=en_US.utf8
SHELL=/bin/bash
ProcVersionSign
SourcePackage: gdm
Uname: Linux 2.6.32-13-generic i686
Thank you for taking the time to report this bug and helping to make Ubuntu better. However, your crash report is either missing or challenging to deal with as a '.crash' file. Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer.
If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart.
If you are using Ubuntu with the Gnome desktop environment - launch nautilus and navigate to your /var/crash directory and double click on the crash report you wish to submit.
If you are using Kubuntu or Xubuntu you can file the crash using /usr/share/ apport/ apport- qt --crash- file=/var/ crash/_ my_crash_ report. crash in a terminal - where _my_crash_ report. crash is the crash you would like to report.
I'm closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently. Thanks in advance for your cooperation and understanding.