Comment 48 for bug 1061149

Revision history for this message
Steve Langasek (vorlon) wrote :

What it comes down to, I think, is that something non-standard is killing lightdm that shouldn't be; /var/log/lightdm.log gives us enough info to know the pid of what's doing the killing, but not the name. Given that at and cron have just started, it *could* be a strange cronjob or at job; it's more likely to be something called from an upstart job; booting with --verbose and cross-referencing that output against the 'initctl list' output and the /var/log/lightdm.log from the same boot *may* help isolate this.

Further things to investigate:

 - is this reproducible with a freshly-installed raring userspace?
 - are there any modified or orphaned config files under /etc/? (sudo apt-get install debsums; sudo debsums -s -e; sudo find /etc -type f -print0 | sudo xargs -0 dpkg -S > /dev/null)
 - can you capture the guilty process on a bootchart? (apt-get install bootchart)