Bug 6989

Summary: dconf-editor doesn't work
Product: Mageia Reporter: Ken Arromdee <arromdee2>
Component: RPM PackagesAssignee: Mageia Bug Squad <bugsquad>
Status: RESOLVED OLD QA Contact:
Severity: normal    
Priority: Normal CC: fundawang, nic, olav
Version: Cauldron   
Target Milestone: ---   
Hardware: i586   
OS: Linux   
Whiteboard:
Source RPM: dconf CVE:
Status comment:

Description Ken Arromdee 2012-08-09 00:59:23 CEST 
Description of problem:
Using dconf-editor does not allow changes to be made.

Version-Release number of selected component (if applicable):
0.12.0-1

How reproducible:
always

Steps to Reproduce:
1. Run dconf-editor
2. Try to change a setting.
3. The setting doesn't stay changed.  Checkboxes don't get checked, and selecting something from a dropdown doesn't change it, for instance.  Whether I am running Gnome or not makes no difference.  Also, the "set to default" button is greyed.  There is nothing in $HOME/.config/dconf.

Trying to run it as root sort of allows it to change.  If I make a change and immediately exit, then restart dconf-editor, the change appears.  For instance, I go into org/gtk/demo and see that color is "red".  I select "green".  The selection remains "red" but after I exit and restart it is "green".  At any rate, changing settings this way doesn't change the settings that affect a regular user.  The "set to default" button is not greyed.

I've also had other dconf-related setting problems and posted on the GTK forum board: http://www.gtkforums.com/viewtopic.php?f=3&t=178065
Manuel Hiebel 2012-08-19 13:19:25 CEST

CC: (none) => fundawang, jani.valimaa, olav
Source RPM: dconf-editor-0.12.0-1.mga2 => dconf

Jani Välimaa 2012-10-25 17:18:28 CEST

CC: jani.valimaa => (none)

Comment 1 Nic Baxter 2015-03-29 01:57:28 CET 
This is quite old. Any further comments? Still valid? Close?

CC: (none) => nic

Comment 2 Nic Baxter 2016-01-24 12:10:38 CET 
Since there are insufficient details provided in this report for us to investigate the issue further, and we have not received feedback to the information we have requested above, we will assume the problem was not reproducible, or has been fixed in one of the updates we have released for the reporter's distribution.

Users who have experienced this problem are encouraged to upgrade to the latest update of their distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information.

Closing as OLD.

Status: NEW => RESOLVED
Resolution: (none) => OLD