Comment 11 for bug 390733

From what I can see, on bootup its starting a metacity process, and calling anything with --replace isnt removing that original metacity process. Killing the plain metacity process fixes it for me every time.

For instance, if I boot with no compiz and change metacity to use compositing via gconf-editor, it starts a new metacity --replace process but leaves the old one there and I get 100% cpu usage with 10% cpu usage in gconfd-2 being the highest visible thing.

robert 3813 2.9 0.7 21488 11092 ? S 19:59 0:03 metacity --replace
robert 4563 0.0 0.4 18868 6640 ? R 20:01 0:00 metacity

Killing the 4563 metacity process cures it. The same thing happens when I use compiz --replace.