GDM dies on initial login attempt when passed specific keypresses in password field

Bug #521075 reported by QPrime
This bug affects 3 people
Affects Status Importance Assigned to Milestone
gdm (Ubuntu)
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
ProcVersionSignature: Ubuntu 2.6.32-13.18-generic
SourcePackage: gdm
Uname: Linux 2.6.32-13-generic i686

Revision history for this message
QPrime (mwells) wrote :
Revision history for this message
Sebastien Bacher (seb128) wrote :

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.

Changed in gdm (Ubuntu):
assignee: nobody → Ubuntu Desktop Bugs (desktop-bugs)
importance: Undecided → Medium
status: New → Invalid
Revision history for this message
QPrime (mwells) wrote :

Hi Sebastian, there was no crash report included because there was no crash report produced. Not really sure what to do with this particular bug... I would pass it upstream, but I can't really verify that it's not Ubuntu specific as I'm exclusively testing Lucid (as delivered via nightlies and official Canonical package updates) right now. Let me know what else you might need me to do on this to either dismiss this issue or focus attention on it. Would love to get input from others to help determine if it's this particular PC, this particular model of PC or perhaps a wider software based issue.

Revision history for this message
QPrime (mwells) wrote :

errr... make that "Hi Sebastien". I hate it when I get names wrong :P

Revision history for this message
QPrime (mwells) wrote :

I can confirm that removing Plymouth seems to correct this issue (and a host of other apparent ati kms problems)

Revision history for this message
Sebastien Bacher (seb128) wrote :

thank you for looking into details there and updating the bug

Revision history for this message
Yotam Benshalom (benshalom) wrote :

I have the same problem using nvidia 9500m with the nvidia-current driver. My gdm restarts as soon as I type "2" in the password field, and then I can login normally.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers