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) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1061149 Title: boot occasionally hangs while "Checking battery state..." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1061149/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
