Lightdm killed during boot (kills itself?)

Bug #1080082 reported by Ivo Anjo
44
This bug affects 10 people
Affects Status Importance Assigned to Milestone
Light Display Manager
New
Undecided
Unassigned
fglrx-installer (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

I'm running 12.10, and since installing the stable release in October I didn't install any upgrades. This week, after installing the latest upgrades, lightdm stopped working: the Xserver starts, and dies immediately, leaving me on a tty7 with remains of log messages.

If I log in and manually restart lightdm, it works.

I think I am not alone in this, as a user had reported exactly the same back in July in the xubuntu-users mailing list:
https://lists.ubuntu.com/archives/xubuntu-users/2012-July/004252.html

I've done some tests and:
- If I disable plymouth (by removing splash from GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub) the bug goes away
- If I press 'esc' to exit plymouth before lightdm triess to start the bug also goes away

Looking at the lightdm log, it seems that it decides to kill itself:
...
[+1.22s] DEBUG: Starting Light Display Manager 1.4.0, UID=0 PID=1138 (notice the pid)
...
[+5.59s] DEBUG: New display ready, switching to it
[+5.59s] DEBUG: Activating VT 7
[+6.53s] DEBUG: Greeter start authentication for knuckles
[+6.54s] DEBUG: Started session 1862 with service 'lightdm', username 'knuckles'
[+6.54s] DEBUG: Greeter start authentication for knuckles
[+6.54s] DEBUG: Session 1862: Sending SIGTERM
[+6.54s] DEBUG: Started session 1863 with service 'lightdm', username 'knuckles'
[+6.54s] DEBUG: Got signal 15 from process 1138 (signal to die received from itself!!)
[+6.54s] DEBUG: Caught Terminated signal, shutting down
...

This is what leads me to believe that the bug is in lightdm.

ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: xorg 1:7.7+1ubuntu4
ProcVersionSignature: Ubuntu 3.5.0-19.30-generic 3.5.7
Uname: Linux 3.5.0-19-generic x86_64
NonfreeKernelModules: fglrx
.tmp.unity.support.test.0:

ApportVersion: 2.6.1-0ubuntu6
Architecture: amd64
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
Date: Sat Nov 17 14:06:16 2012
DistUpgraded: Fresh install
DistroCodename: quantal
DistroVariant: ubuntu
DkmsStatus:
 fglrx-updates, 9.000, 3.5.0-18-generic, x86_64: installed
 fglrx-updates, 9.000, 3.5.0-19-generic, x86_64: installed
EcryptfsInUse: Yes
ExtraDebuggingInterest: Yes
GraphicsCard:
 Advanced Micro Devices [AMD] nee ATI Wrestler [Radeon HD 6310] [1002:9802] (prog-if 00 [VGA controller])
   Subsystem: Lenovo Device [17aa:397b]
InstallationDate: Installed on 2012-10-21 (26 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
MachineType: LENOVO 10382JG
MarkForUpload: True
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.5.0-19-generic root=UUID=9a791902-1e8f-4073-b59c-de19842fdff8 ro rootflags=subvol=@ crashkernel=384M-2G:64M,2G-:128M quiet
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/10/2011
dmi.bios.vendor: LENOVO
dmi.bios.version: 4BCN24WW
dmi.board.asset.tag: Base Board Asset Tag Unknown
dmi.board.name: Inagua
dmi.board.vendor: LENOVO
dmi.board.version: 109-B78210-00A
dmi.chassis.asset.tag: Chassis Asset Tag Unknown
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Chassis Version Unknown
dmi.modalias: dmi:bvnLENOVO:bvr4BCN24WW:bd08/10/2011:svnLENOVO:pn10382JG:pvrIdeapadS205:rvnLENOVO:rnInagua:rvr109-B78210-00A:cvnLENOVO:ct10:cvrChassisVersionUnknown:
dmi.product.name: 10382JG
dmi.product.version: Ideapad S205
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.8.4+bzr3407-0ubuntu1
version.fglrx-installer: fglrx-installer N/A
version.ia32-libs: ia32-libs 20090808ubuntu36
version.libdrm2: libdrm2 2.4.39-0ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 9.0-0ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 9.0-0ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu6
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.99.99~git20120913.8637f772-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.9-0ubuntu2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.2-0ubuntu3

Revision history for this message
Ivo Anjo (knuckles) wrote :
bugbot (bugbot)
tags: added: xubuntu
bugbot (bugbot)
affects: xorg (Ubuntu) → fglrx-installer (Ubuntu)
Revision history for this message
Ivo Anjo (knuckles) wrote :

Might be related to bug #838586 and question #208880 ?

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

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

Changed in fglrx-installer (Ubuntu):
status: New → Confirmed
Revision history for this message
Ivo Anjo (knuckles) wrote :

Just to add, I've tried multiple workarounds, and the best one (works every time) and less intrusive is modifying the file /etc/init/lightdm.conf adding "respawn" like this:

...
stop on runlevel [016]

respawn

emits login-session-start
emits desktop-session-start
emits desktop-shutdown
---

Revision history for this message
TitusX (titusx) wrote :

I have a Problem wich sounds linke hat:
- after an update/restart lightdm stops
- I saw only tty messages

After 2 reboots lightdm works, but now ...
- I can't login anymore (only as guest)
- the password is okay, because login at tty1 works
- /var/log/lightdm/x-1-greeter.log shows some messages marked with "DEBUG" and "CRITICAL", and last message "PID xxxxx (we are xxxxx) sent signal 15, shutting down ..."
- /var/log/lightdm/x-2-greeter.log, too - but last line is: "XIO: fatal IO error 11"

Revision history for this message
TitusX (titusx) wrote :

So, finally I managed it - and sorry, maybe this was not the same issue:
- After digging the logfiles, stopping lightdm and try to manually "startx" ...
- it seemed that there must be an lock from an older xsession
- nothing unusual in the"/var/lock/" and "/var/run/" directories
- but there where 3 files in my home directory
- "rm /home/<user>/.Xauthority* " and a reboot
- done

I'm not shure what happend (I'm no linux master mind)
- but: I got the error described in the bug
- after some (2) reboots (I tried a "touch /forcefsck") this bug vanished, but left these files.

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.