X/GDM crashes on first login attempt (sounds a LOT like the plymouth bug)

Bug #540897 reported by Jeff Lane on 2010-03-18
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
plymouth (Ubuntu)
Undecided
Unassigned

Bug Description

Binary package hint: plymouth

Installed 64bit and 32bit Lucid Beta using the Alternate ISOs as of
17 March.

After install, on the first reboot, in GDM I clicked on my username
and entered my password. After entering the password, I hit enter
instead of clicking the button.

At this point, X died, leaving a few control characters in the upper left
hand corner of the screen. Shortly afterwards, X restarted, and I was
able to log in successfully.

This situation occurs after every reboot for the first login attempt.

Also, if I click the button instead of hitting enter, I am able to log in
but the first time I hit the enter key AFTER logging in, X dies, and
restarts.

This also occurred AFTER updating plymouth to the -16 level.

ProblemType: Bug
Architecture: amd64
CurrentDmesg: [ 27.355820] eth0: no IPv6 routers present
Date: Thu Mar 18 08:54:30 2010
DistroRelease: Ubuntu 10.04
InstallationMedia: Error: [Errno 13] Permission denied: '/var/log/installer/media-info'
Lsusb:
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: innotek GmbH VirtualBox
Package: plymouth 0.8.0~-16
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-16-generic root=UUID=c7e266d7-383c-46a7-b114-78cb12a8cf06 ro quiet splash
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 VGA16 VGA
ProcVersionSignature: Ubuntu 2.6.32-16.25-generic
SourcePackage: plymouth
Uname: Linux 2.6.32-16-generic x86_64
dmi.bios.date: 12/01/2006
dmi.bios.vendor: innotek GmbH
dmi.bios.version: VirtualBox
dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:
dmi.product.name: VirtualBox
dmi.product.version: 1.2
dmi.sys.vendor: innotek GmbH

Jeff Lane (bladernr) wrote :
Steve Langasek (vorlon) wrote :

This looks to be bug #540256, as I suspected. Please upgrade to plymouth *-17*, and confirm that the problem goes away.

Changed in plymouth (Ubuntu):
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers