Ask Ubuntu is a question and answer site for Ubuntu users and developers. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Unity has just crashed and the following is displayed when I try to restart it by running the command unity:

Initializing bailer options...done
Initializing detection options...done
Initializing composite options...done
Compiz (opengl) - Fatal: No valid GL extensions string found.
Compiz (bailer) - Info: Ensuring a shell for your session
Cannot register the panel shell: there is already one running

This computer has been running Unity for the last few days with no problems, so this is not likely a hardware issue.

What do I have to do to get Unity to restart?

share|improve this question

closed as off topic by Marco Ceppi Feb 1 '12 at 20:23

Questions on Ask Ubuntu are expected to relate to Ubuntu within the scope defined by the community. Consider editing the question or leaving comments for improvement if you believe the question can be reworded to fit within the scope. Read more about reopening questions here.If this question can be reworded to fit the rules in the help center, please edit the question.

If you don't do much Compiz customizations try resetting Compiz. – Oxwivi Jun 6 '11 at 7:21
And the restart command is unity --reset not unity. – Oxwivi Jun 6 '11 at 7:21
This question should instead be filed as a bug report, thanks! Instructions here. – Marco Ceppi Feb 1 '12 at 20:23

Try CTRL + ALT + F1

login to TTY1


unity --reset &

then CTRL + ALT + F7 to see if Unity was reset successfullly.

share|improve this answer
This did not work. Actually it just ended up restarting gdm... thereby causing me to lose all my open windows. – Nathan Osman May 1 '11 at 20:52
OK, sounds like a Compiz/Unity crash. Does this happen all the time when you login? Does it happen with another user account? Maybe one of the startup applications is causing Compiz/Unity to crash. – fossfreedom May 1 '11 at 20:55
It happened when I ran a D3D app in Wine. See here. – Nathan Osman May 1 '11 at 20:56

Try starting unity-window-decorator when it crashes the next time. When Natty was still in beta and apport was still enabled, apport told the name of the crashed process (and for me, it was always unity-window-decorator). You can also look in /var/log/syslog, it should have a line with "segfault".

share|improve this answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.