Possibly? When I manually run unity to collect the logs, my screen goes black except for the cursor exactly as described, and compiz starts to spin (100% CPU) and has to be SIGKILLed. This happens consistently when running manually, but never when logging in from lightdm. GDB doesn't seem to produce a backtrace though, even when I run unity with --debug.
I'm fairly code-savvy, so I can try more detailed debugging if you'll point in the right direction. I'll see what valgrind spits out, for lack of any better ideas at this point. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/963465 Title: Unity 5.8: Can't login to Unity since upgrade to 5.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/963465/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
