As I've already described in an earlier comment, it was not gnome- screensaver particularly blocking but the second instance of dbus-launch (dbus-launch --autolaunch) gnome-screensaver initiated when it attempted to send a dbus message with no active session (before my SRU, dbus- launch (dbus-launch --sh-syntax --exit-with-session) was called after gnome-screensaver). The actual freeze/block is caused by the libxcb race/architecture issues. I was able to determine this via research, extensive time spent in gdb, and some good ol' intuition.
Your last point is a good one. The sleep statement probably should be removed - I simply added it "just in case". My rationale was that users would rather wait an extra second then for the login process to freeze all together. However, on my computer after applying my changes (with out the sleep), I've had no trouble what so ever. -- dbus-launch hangs at session start waiting on socket output in libxcb https://bugs.launchpad.net/bugs/232364 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
