Adding sleep 2, is definitely *not* a solution, nothing but an ugly and hopefully interim workaround. I'm wondering why the gdm gnome-settings- daemon is not yet dead when the logging user process kicks in. Either it's stalled waiting for something late, or it is just too slow to die. I'm tempted to think it may be second case, my machine is pretty fast (dual 6 core Xeon X5650), in such case it may be upstream bug.
PS1: Shall we consider changing the status of this bug? It seems confirmed. PS2: BTW, the title is wrong, it does affect production Maverick. I guess we don't care any longer about rc. -- maverick rc gnome-settings-dameon doesn't start https://bugs.launchpad.net/bugs/652929 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
