Compiz should use gsettings for decorator theme

[Michael Mueller]

Steps to reproduce:

- Run Ubuntu quantal with Unity
- Open the System Settings, go to "Appearance" panel
- Set theme to "Radiance"

Expected: window decorations should change to use "Radiance" style (light one).

Got instead: the Gtk theme is updated, but window decorations are still using "Ambiance" style.

How to fix: Compiz should read the decorator theme from GSettings (org.gnome.desktop.wm.preferences:theme), not from gconf.

ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: gnome-control-center 1:3.4.2-0ubuntu13
ProcVersionSignature: Ubuntu 3.5.0-13.14-generic 3.5.3
Uname: Linux 3.5.0-13-generic i686
ApportVersion: 2.5.1-0ubuntu4
Architecture: i386
Date: Thu Sep 6 17:24:00 2012
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha i386 (20120724.2)
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-control-center
UpgradeStatus: No upgrade log present (probably fresh install)
usr_lib_gnome-control-center:
 activity-log-manager-control-center 0.9.4-0ubuntu3
 deja-dup 23.90-0ubuntu1
 gnome-control-center-signon 0.0.13-0ubuntu1
 indicator-datetime 12.10.0-0ubuntu1

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Adolfo Jayme Barrientos (fitojb)]

This is caused because metacity now uses gsettings, see https://bugs.launchpad.net/compiz/+bug/1035261/comments/15, ubuntu needs to update the appearance patch

[Dmitry Shachnev (mitya57)]

The appearance patch has been updated since 1:3.4.2-0ubuntu9. The new key is in org.gnome.desktop.wm.properties gsettings schema.

Do you use Metacity? If yes, what version?

[Dmitry Shachnev (mitya57)]

Ignore that, I can reproduce this bug on up-to-date quantal with Unity. The control-center correctly sets the theme in gsettings, but it seems that Compiz is still looking for gconf value (/apps/metacity/general/theme), and changing it makes compiz change the theme.

[Dmitry Shachnev (mitya57)]

This will maybe get fixed in 0.9.8.2 (see bug 1042323).

[Daniel van Vugt (vanvugt)]

I'm going to assume this will be fixed by the fix for bug 1042323. Please un-duplicate if that proves not to be the case.