After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 521893 - gnome-wm should be updated to handle compiz-fusion correctly
gnome-wm should be updated to handle compiz-fusion correctly
Status: RESOLVED OBSOLETE
Product: gnome-session
Classification: Core
Component: general
unspecified
Other Linux
: Normal normal
: ---
Assigned To: Session Maintainers
Session Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-03-11 23:26 UTC by Jose M. daLuz
Modified: 2013-01-13 18:46 UTC
See Also:
GNOME target: ---
GNOME version: 2.23/2.24



Description Jose M. daLuz 2008-03-11 23:26:10 UTC
In the gnome-wm script, the following cases handle compiz/beryl:

case `basename $WINDOW_MANAGER` in
  compiz)
    export LIBGL_ALWAYS_INDIRECT=1
    gtk-window-decorator &
    OPT3=glib
    OPT4=gconf
    ;;
  beryl)
    emerald &
    ;;
esac

With compiz-fusion, compiz should now start with a single plugin, ccp, which loads the configuration from whichever config backend the user has chosen, with gconf being the default in Gnome. Using the gnome-wm script in its present state will cause compiz to start with all user configuration ignored entirely as there is no longer a gconf plugin. Also, a user can choose to use the flat file config backend instead of gconf even under Gnome.

The config for the decoration plugin can also start the window decorator, so for distros shipping compiz populating the default decorator in the compiz config makes more sense than starting it here. Also, users might choose to use the emerald decorator with compiz under Gnome, even though it does not respect Gnome themes the way gtk-window-decorator does, because of the extra bling it provides.

Finally, beryl has been replaced by compiz-fusion, so you should drop beryl entirely from this file.
Comment 1 Jose M. daLuz 2008-03-11 23:38:39 UTC
Two clarifications - there is no gconf plugin any longer, it has been replaced by ccp which uses different backends to store config settings. 

Also, in distros where compiz is an add-on rather than included by default, the decorator plugin does not necessarily get enabled by default. In those cases, starting gtk-window-decorator in this script is worse than useless since without the decorator plugin enabled gtk-window-decorator (or emerald for that matter) will do nothing.
Comment 2 Jose M. daLuz 2008-08-24 19:00:00 UTC
Since gnome-session 2.23.x seems to still use gnome-wm to start compiz, this needs fixing more than ever. The existing gnome-wm breaks compiz by not loading the ccp plugin (which loads user config and, in turn, causes the user's chosen window decorator to run). User settings disappear unless the user edits gnome-wm to correct it and then re-runs compiz with the ccp plugin.
Comment 3 Bastien Nocera 2013-01-13 18:46:59 UTC
gnome-wm doesn't exist anymore in GNOME 3.