Comment 6 for bug 963465

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.