[oneiric] gconf settings don't get set properly

Bug #836443 reported by Jeremy Bícha
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gconf
New
High
gconf (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Using gconf-editor to set settings doesn't work. The new theme section of System Settings sets every setting except for the Window theme which is the only setting changed there that is still gconf and isn't gsettings. When I try to Edit>Keyboard Shortcuts in gnome-terminal, my changes don't stick after closing gnome-terminal because the gconf settings aren't actually set.

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: gconf2 3.1.6-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-9.14-generic 3.0.3
Uname: Linux 3.0.0-9-generic x86_64
Architecture: amd64
Date: Mon Aug 29 01:45:06 2011
SourcePackage: gconf
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Jeremy Bícha (jbicha) wrote :
Revision history for this message
Jeremy Bícha (jbicha) wrote :

An exception to the broken gconf is gnome-tweak-tool which is still able to set gconf values (like the previously mentioned window theme). gnome-tweak-tool uses the following code:

from gi.repository import GConf

class GConfSetting:
    def __init__(self, key, _type):
        self._key = key
        self._type = _type
        assert(self._type in (str, bool))
        self._client = GConf.Client.get_default()

    def set_value(self, value):
        if self._type == bool:
            self._client.set_bool(self._key, value)
        elif self._type == str:
            self._client.set_string(self._key, value)
        else:
            assert(False)

Revision history for this message
Jeremy Bícha (jbicha) wrote :

Nevermind the theme part. The new theme selector needs to set both gconf settings /desktop/gnome/shell/windows/theme and /apps/metacity/general/theme .

gnome-terminal and gconf-editor still don't work right with gconf.

Revision history for this message
Jeremy Bícha (jbicha) wrote :

Ok, things seem to be working fine for me now with gconf. I believe there was a bug here previously (as seen with the linked GNOME bug report) but as I can no longer reproduce, I'm closing this.

Changed in gconf:
importance: Unknown → High
status: Unknown → New
Changed in gconf (Ubuntu):
status: New → Invalid
importance: Undecided → Medium
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.