disable compiz when disabling nvidia

We cannot fix this in restricted-manager, since it runs as root and thus should not modify user settings. Also, when disabling the nvidia module, we do not need to immediately stop compiz and start metacity (which would interrupt the users's desktop session heavily), but it is enough to detect this at session start and start metacity instead of compiz.

Seb, do you have a recommendation how to solve this?

That's something compiz should handle better, the bug I opened on compiz has been marked duplicate from this one:
"When compiz can't be used it would be nice to run the GNOME window manager instead"

Do you think it would do the trick?

That's fixed with this upload:

 compiz (1:0.3.6-1ubuntu9) feisty; urgency=low
 .
   * debian/compiz.wrapper:
     - run gnome-wm if compiz can't be used correctly (Ubuntu: #93734)
   [ Nicolas Bruguier ]
   * debian/patches/011_snap-by-default.patch:
     disable patch (close #88733, #89592).
   * debian/patches/016-add-ignore-desktop-hints.patch:
     Add --ignore-desktop-hints command line option, which can be used
     to make compiz not read "number of desktops" and "current desktop"
     hints left by previous WM.
   * debian/compiz.wrapper:
     Add --ignore-desktop-hints in default options
   * debian/patches/086-workspaces-terminal-keybindings.patch:
   * debian/patches/088-gnome-bridge-keybindings-plugin.patch:
   * debian/patches/093-add-toggle-window-on-all-desktop.patch:
     Add toggle window on all desktop keybinding (close #94402)
   * debian/patches/094-fix-gtk-window-decorator-no-argb-crash.patch:
     Fix gtk-window-decorator crash when ARGB isn't enabled and only
     that, in this case window-decoration are invisible
     (Close #94140, #82205).
   * debian/patches/098-schemas:
     Schemas regeneration
   * debian/patches/088-gnome-bridge-keybindings-plugin-schemas.patch:
     Dropped.
   * debian/compiz-plugins.gconf-defaults:
     Add left click to TopRight corner scale activation (Close #92493)
     Add zoom plugin by default (Close #93046) Keenan Pepper patch

No, it hasn't been fixed. This doesn't work correctly, see bug 99269

not a duplicate

This was fixed with Compiz 0.3.6-1ubuntu11 , wasn't it?

Argh, that was too fast. As I already explained to myself above, we cannot fix this in r-m.

No, latest compiz still doesn't get along with this. When being started with nv, you just get a white screen and compiz is running.

I just changed nvidia to nv in my xorg.conf and restarted X, I could log in fine, it started metacity instead for me. No white screen. no compiz running. It used to not work but it's worked ever since Compiz 0.3.6-1ubuntu11 was released.

So it's working fine here.

First cut at a solution: This Xsession.d script disables compiz if nv is configured in xorg.conf.

Itch: if people have both KDE and Gnome installed and run KDE, they will have a lingering gconfd.

This behavior is now in Gutsy.

Could this fix also be applied to the ati side of things?

I am running the latest packages after an install of hardy beta and ran into the white screen when going from the fglrx back to the default ati or radeon driver.

The gconf key setting (from the "proposed Xsession.d script" above) back to metacity works fine and should just have a flag for the ati/radeon driver I think. Does that sound right?

Can you please open a new bug against desktop-effects for the fglrx issue?