I've been messing around with Unity and broke something, how do I "start over"?
For 12.10 - 13.04
I, along with jokerdino and amithkk have created a python script that cleanly resets Unity for Quantal and above.
It is hosted on github at https://github.com/phanimahesh/unity-revamp
The script is now bundled with Unity Tweak Tool. You can install it using
sudo add-apt-repository ppa:freyja-dev/unity-tweak-tool-daily sudo apt-get update sudo apt-get install unity-tweak-tool
For 13.10 & 14.04
sudo apt-get install unity-tweak-tool
To reset Unity, do
Note - if this does not resolve your Unity issues then the following Q&A may apply to you:
What happens behind the scenes?
Simple. We chase each individual setting that Unity uses, and reset them to their default values, and then reload unity to apply changes. Ah yes, we also kill Unity and compiz before we start, since it is known to get tricky if we change settings under compiz's nose.
Why is this better compared to using
dconf reset ?
- Didier Roche (didrocks), the author of unity python wrapper says
dconf resetdoes not work in all cases.
- The consensus among Unity developers is that the settings be modified using Gsettings instead of dconf directly.
What exactly is
A little history
- The configuration settings were managed by gconf earlier.
- Gnome provides Gsettings as a replacement for gconf.
- Gsettings is a high level api that manipulates the settings stored in a backend.
- Unity stores its settings in the backend dconf since it can be loaded much faster than gconf.
As Kees said, running
will reset all of the launcher options, but it won't remove your custom favorites. To also remove any launchers you've added to the launcher, run
Or manually by:
gsettings reset com.canonical.Unity.Launcher favorites
I would recommend running the gsettings command before
unity --reset, so that you won't have to restart unity for the gsettings key reset to take effect.
For Ubuntu 12.10 (Revised, again)
OK, here it is. You can use 'dconf reset' as previously outlined and will do exactly what 'unity --reset' used to do.
dconf reset -f /org/compiz/
compiz --replace & disown
Apparently it would actually be better to stop compiz before using the 'dconf reset'. Which I'm currently working on.
You can also look at the settings you have:
dconf dump /org/compiz/
To reset the unity icons you can still use
This information is from a variety of sources, after much googling.
If you've messed with the indicators and need to reset those see this question:
Sometimes people accidentally turn off the Unity plugin or setting an unsupported option in CCSM can cause it to break.
You can turn it back on by following these directions:
For 12.10 — 13.04 [maybe older]
I use this workaround to reset the unity configuration. But with Unity, it resets all configurations such as the custom wallpaper, themes, icon themes etc.
Delete the user specific dconf database file:
Then Logout and Login again.
IMPORTANT! Be sure that you BACKUP this file, because you lose ALL Unity's settings and switch to default!
For 11.10 and later
cd ~; rm -rf .gnome .gnome2 .gconf .gconfd .metacity .compiz-1 .config/compiz-1 .config/dconf
I ran across this thread after my Unity 2d desktop suddenly refused to display launchpad and title bar (for all users), for no apparent reason. Autohide was disabled. Reenabling Unity in CCSM as sugggested in other threads was part of the solution, but none of the other measures suggested in this and several other related threads, including, but not limited to:
Reinstalling unity Reinstalling ubuntu desktop Removing all relevant (e.g. compiz, gconf, etc.) configuration information
helped me to completely resolve these symptoms.
would not work for me. After delivering a variety of error and information messages, it would always hang at:
Setting Update "run_key"
as shown in the log posted in the thread titled "unity has vanished" for unity run with no arguments.
I noticed that the error message delivered by:
was similar to some of the errors reported by unity --reset:
error while loading shared libraries: libGL.so.1:
cannot open shared object file: No such file or directory.
After extensive searching, I found the following solution (courtesy of J.D. Bartlett):
Get the path of libGL.so.1 by using the command locate libGL.so.1. Add a link to the library in /usr/lib/ as shown in the following example: sudo ln -s /usr/lib/i386/mesa/libGL.so.1 /usr/lib Restart the computer.
This not only allowed both unity_support_test-p and unity --reset to run, it also allowed Unity 2d to start. Like the author of the above-mentioned post, I have no idea what caused my problems. I am also still not sure whether the link is a complete solution, or whether I should reinstall the graphics libraries completely, but since creating the link, everything has worked fine for a few weeks now.