How to fix a messed up Compiz/Unity installation

Asked by MC Return on 2012-07-16

During work on https://code.launchpad.net/~mc-return/compiz/compiz.merge-plugin-simple-animations/+merge/115048 I accidentially sudo make installed a fresh build of lp:compiz in Quantal (my intention was to just install the built plug-in).
After running compiz --replace to test the fresh install the unity plug-in in CCSM was missing and Unity seemed to be messed up, but Compiz was running.
So I decided it would be best to make a "sudo make uninstall" in compiz/build and to reinstall the latest version via Synaptic.
After a reboot Compiz/Unity failed to start up and I was forced to switch to Unity-2d (hopefully just temporarily).
To get back to a working Compiz/Unity combination I tried to rename the .compiz and .compiz-1 folders in my home dir, completely remove Unity and Compiz via synaptic and reinstall afterwards, but still Unity/Compiz both still fail to start.

How can I get back to a working Compiz/Unity desktop when things are messed up like that ?

Question information

Language:
English Edit question
Status:
Solved
For:
Compiz Edit question
Assignee:
No assignee Edit question
Solved by:
MC Return
Solved:
2012-07-18
Last query:
2012-07-18
Last reply:
2012-07-17
Jessica Lambiase (siliconjey) said : #1

Did you try

    gconftool-2 --recursive-unset /apps/compiz-1

and then

    unity --reset

after your unity/compiz fresh reinstall? Anyway try to post some error message, think you can find something interesting in /var/log/Xorg.0.log.

MC Return (mc-return) said : #2

siliconjey, thanks for the suggestions, but I tried that and it did not work. Nothing special in Xorg.0.log either.

I think the main problem is that the fresh build of Compiz installed to /usr/local, while the original Compiz in Ubuntu lives in /usr.

When I try to run unity --replace this happens:
compiz (core) - Info: Loading plugin: core
compiz (core) - Info: Starting plugin: core
unity-panel-service: no process found
compiz (core) - Warn: Attempted to restack relative to 0xe00048 which is not a child of the root window or a window compiz owns

MC Return (mc-return) said : #3

Ok, I got it. Back on a fully working Unity-3d :)

The solution was to remove/rename all Compiz related files in usr/local.

MC Return (mc-return) said : #4

Ok, I got it. Back on a fully working Unity-3d :)

The solution was to remove/rename all Compiz related files in usr/local.

Jessica Lambiase (siliconjey) said : #5

That's good. :)