lightdm fails to bring up X display automatically after boot

Bug #946116 reported by Peter Belew
14
This bug affects 3 people
Affects Status Importance Assigned to Milestone
xserver-xorg-video-nouveau (Ubuntu)
New
Undecided
Unassigned

Bug Description

I recently installed Xubuntu 12.04 alpha2 and have updated it equivalent to beta1. The X display does not automatically bring up a login screen. What I currently have to do is to get a login (using Alt-F2 or Alt-F1), login as root, then run lightdm from the bash command line, which brings up a login, and I can login with my user ID, after which X appears to run normally with Xfce etc.

Ubuntu version and kernel version
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=12.04
DISTRIB_CODENAME=precise
DISTRIB_DESCRIPTION="Ubuntu precise (development branch)"
Linux compaq 3.2.0-17-generic #27-Ubuntu SMP Fri Feb 24 15:37:36 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
model name : AMD Athlon(tm) 64 Processor 3800+
cpu MHz : 1000.000

This problem doesn't seem to depend on whether I have an xorg.conf file in /etc/X11

I have appended a gzip file which includes Xorg.0.* at various stages, my xorg.conf file, and dmesg output.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: lightdm 1.1.4.is.1.1.3-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-17.27-generic 3.2.6
Uname: Linux 3.2.0-17-generic x86_64
ApportVersion: 1.94-0ubuntu1
Architecture: amd64
Date: Sat Mar 3 22:08:11 2012
InstallationMedia: Xubuntu 12.04 "Precise Pangolin" - Alpha amd64 (20120201.1)
ProcEnviron:
 LANGUAGE=en_US:en
 TERM=xterm
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: lightdm
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Peter Belew (peterbe) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in lightdm (Ubuntu):
status: New → Confirmed
Revision history for this message
Jane Atkinson (irihapeti) wrote :

This sounds very similar to Bug #935591. The difference seems to be that another window manager is involved.

Revision history for this message
Robert Ancell (robert-ancell) wrote :

Could you attach /var/log/lightdm/lightdm.log to confirm if lightdm is at fault?

Changed in lightdm (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Peter Belew (peterbe) wrote :

Here are two instances of lightdm.log, before and after running lightdm as root:

lightdm.log before
lightdm1.log after

in a tar archive.

Revision history for this message
Robert Ancell (robert-ancell) wrote :

Thanks,

The relevant logs from lightdm are:
[+0.78s] DEBUG: Logging to /var/log/lightdm/x-0.log
[+0.79s] DEBUG: Launching process 1221: /usr/bin/X :0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch -background none
[+2.17s] DEBUG: Process 1221 exited with return value 1

Which shows that the X server failed to start.

From Xorg.0.log-0 there is a failure (not sure if this is the correct log, /var/log/lightdm/x-0.log would tell you for sure):
[ 16.934] (II) NOUVEAU(0): NVEnterVT is called.
[ 16.961] (EE) NOUVEAU(0): failed to set mode: Invalid argument
Fatal server error:
[ 16.961] failed to create screen resources
[ 16.961]
Please consult the The X.Org Foundation support
  at http://wiki.x.org
 for help.
[ 16.961] Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[ 16.961]
[ 16.961] (II) AIGLX: Suspending AIGLX clients for VT switch
[ 16.961] (II) NOUVEAU(0): NVLeaveVT is called.
[ 16.984] ddxSigGiveUp: Closing log
[ 16.985] Server terminated with error (1). Closing log file.

So it appears nouveaux has a problem starting on boot. I'll reassign this to the xorg team who can better diagnose this.

affects: lightdm (Ubuntu) → xorg (Ubuntu)
Changed in xorg (Ubuntu):
status: Incomplete → New
Revision history for this message
Peter Belew (peterbe) wrote :

Thanks, Robert, for reviewing the lightdm.log output. I´m sure you are right - this is mainly an xorg issue. I´ve filed earlier bug reports on this hardware - see in particular Bug #707755 against development versions of Natty 11.04. :´

Ubuntu version and kernel version
 DISTRIB_ID=Ubuntu
 DISTRIB_RELEASE=11.04
 DISTRIB_CODENAME=natty
 DISTRIB_DESCRIPTION="Ubuntu natty (development branch)"
 Linux hp 2.6.37-12-generic #26-Ubuntu SMP Wed Jan 5 18:42:49 UTC 2011 i686 athlon i386 GNU/Linux
 model name : AMD Athlon(tm) 64 Processor 3800+
 cpu MHz : 1000.000

As mentioned in that bug report, I was able to come up with a workaround involving installing an xorg.conf file. Currently I´m putting that in /etc/X11/ - maybe I should try /usr/share/X11 ?

Revision history for this message
Peter Belew (peterbe) wrote :

After filing comment #7, I rebooted the compaq system. As I was awaiting the system to complete booting, after the Grub2 screen closed - I was alternately hitting Alt F1 and Alt F2 and possibly Enter - somethow this time the lightdm login greeter appeared and I was able to log in. I'll attach the lightdm.log ...

Revision history for this message
Peter Belew (peterbe) wrote :

I assume there is some sort of race condition in system startup.

I am also attaching Xorg.0.log

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Timo Aaltonen (tjaalton)
affects: xorg (Ubuntu) → xserver-xorg-video-nouveau (Ubuntu)
Changed in xserver-xorg-video-nouveau (Ubuntu):
status: New → Confirmed
bugbot (bugbot)
tags: added: xubuntu
Revision history for this message
Peter Belew (peterbe) wrote :

Apparently this problem is already known:

http://ubuntuforums.org/showthread.php?t=1613132

Since I'm able to boot to a shell, what I just did was to add nomodeset to /etc/default/grub and run update-grub, as described on the ubuntuforums page above. So now the altered line in /etc/default/grub looks like

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nomodeset"

Revision history for this message
Peter Belew (peterbe) wrote :

#11 is a good workaround, but not really a fix to the nouveau driver bug.

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

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.