The start script for compiz (compiz-start) hard codes the list of plug-ins to run. When in fact it, should use the ccsm/gconf backend and only run one. If options are set via ccsm compiz will crash with random segfaults. Replacing one line fixes this problem. The fix: Change line 41 of compiz-start compiz $COMPIZ_OPTIONS gconf move resize minimize place decoration wobbly fa de cube rotate scale switcher zoom dbus to: compiz $COMPIZ_OPTIONS ccp Reference: http://wiki.zenwalk.org/index.php?title=Compiz_Fusion Item #6 bottom of page. As another note, this was tested on both ~amd64 and ~x86. Not sure if you wanted to modify the keywords for amd64.
I agree. The default compiz-start doesn't work for me and destroys KDE decoration. There are two more recommended options: compiz $COMPIZ_OPTIONS --sm-disable --ignore-desktop-hints ccp ps. I guess the script will be replaced with fusion-icon in future.
btw, it would be logical to have compiz-fusion-stop script as well. It should do something like that: kwin --replace &
from #compiz-fusion 01:24 < Betelgeuse> crdlb: Well do you think we should fix it? 01:24 < crdlb> yes :) 01:24 < crdlb> although there is a small problem in that ccp is provided by libcompizconfig
The current compiz-start script is simply broken. It does not work. So... Why still install it with the ebuild? Or, even better, why not just fix the script? So simple to do! And yet haven't been done in more then one month...
Created attachment 142574 [details, diff] compiz-start changes This patch changes compiz-start to accept an argument regarding which window decorator to start. Lacking an argument, it will try to start a decorator that looks like your current one.
Surely compiz-config settings should be used not arguments to the script. If it requires libcompizconfig you should just add that as a dependancy. 90% of compiz users must have it installed anyway.
The updated compiz-0.7.8 uses the new compiz-manager startup script and fusion-icon has been added to the tree as a better replacement to start compiz.
*** Bug 212267 has been marked as a duplicate of this bug. ***
