Comment 12 for bug 1091708

Or, it *could* be a problem with the desktop startup itself. Looking at a chart for a good boot, we see that unity-panel-service is started over dbus by gtk-window-decorator, with gtk-window-decorator itself being launched by some part of compiz after a call to /usr/lib/nux/unity_support_test. In the bad boot, we see unity_support_test called, using a bit of CPU, and exiting. So I don't think this is just a timing thing, I think the desktop hasn't started correctly.

Could someone from the desktop team have a look at this?