Bobby, to force compiz to run, you should disable the blacklist. It
works on my latop, which is also Intel GM965. However, some effects
(blur, rain...) don't work, and sometimes your framerates drops really
low. Overall its ok though. (I simply commented the blackline in the
compiz script, all the
Max, the compositor is enabled by default. So if compiz just segfaulted
or got replaced by metacity in any case, it would stay. Tilll you do
something about it, that is.
--
compiz doesn't start if metacity compositor is enabled
https://bugs.launchpad.net/bugs/178953
You received this bug notific
Metacity compositing manager is enabled by default if compiz fails.
--
compiz doesn't start if metacity compositor is enabled
https://bugs.launchpad.net/bugs/178953
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to metacity in ubuntu.
--
A temporary workaround is not to put metacity into "restart" style in
sessions, and instead of "compiz --replace", use "killall metacity;
compiz --replace". They must be merged in 1 command because if metacity
is killed, it strangely becomes impossible to type at all.
--
compiz doesn't start if
In theory it would, because there is no compositor to fight with compiz,
but the problem is that it is turned on by default. For users who know
what they are doing it won't cause much more pain than 20 mins figuring
out the problem, but for less savvy users this is a potential problem.
--
compiz
