On Fri, 23 Nov 2012, Michael Lindner wrote:
It hangs for longer than normal on a service called plymouth-quit-wait.service
I had a bit of a look around, and /bin/plymouth (formerly unknown to me) is a fancy splash screen during boot that has to be cancelled before X can start (If I understand correctly) I find bug reports for Red Hat https://bugzilla.redhat.com/show_bug.cgi?id=710737 and Suse http://lists.opensuse.org/opensuse-bugs/2012-06/msg03718.html
I've gooogled it and tried the suggested "disable" commands for this, but it still happens.
I wonder whether you could symlink /bin/plymouth to /bin/true ;-) I wonder what happens if you try another minimal window manager. Does it have the delay too?
There is definitely something here, when I've used ubuntu on the same machine in it's default configuration I've not had this problem, also it seems to have occurred after an update, the fresh install didn't hang like this.
I believe I see a change in a recent update of a Ubuntu 12.04 LTS machine. I do not see the GRUB selection screen anymore. I am pretty sure I had that before but I was too lazy to figure out what changed (I don't have the boot delay). On Sat, 24 Nov 2012, Jeremy Visser wrote,
On 22/11/2012 15:01, Peter Ross wrote:
The OP may have a problem with some weird daemon that is stuck when he logs in.
With Windowmaker that daemon would not start in the first place. Problem solved.
I cannot even begin to express just how completely dumb the logic is in the above statement, and just how far removed it is from the concept of problem solving.
Sometimes it is more efficient to swap the tools, instead of fiddling around with broken or complicated ones. There are fancy corkscrews and basic ones. I am confident to open the bottle in 10 seconds. If I choose the basic model. IMHO Gnome became so complicated it "just works" (lucky you) or it doesn't, and then you end up with bug reports as quoted above. Now systemd seems to add another dimension to it. Cheers Peter