FS#35865 - Gnome 3.8 : unable to change settings using dconf
Attached to Project:
Arch Linux
Opened by raymoncal (raymondcal) - Thursday, 20 June 2013, 10:52 GMT
Last edited by Jan de Groot (JGC) - Monday, 15 July 2013, 15:22 GMT
Opened by raymoncal (raymondcal) - Thursday, 20 June 2013, 10:52 GMT
Last edited by Jan de Groot (JGC) - Monday, 15 July 2013, 15:22 GMT
|
Details
Description:
Since this morning, all the settings of my Gnome Shell have been reset, and I can’t change them anymore : everytime I check an option in Gnome-control-center, or in the Terminal options, or in Empathy options, the check-mark disappear immediatly, and nothing is saved. When I’m lauching gnome-control-center via the Terminal, and try to change settings, here is what it says : (gnome-control-center:2692): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._g_2dfile_2derror_2dquark.Code17: Cannot open dconf database: invalid gvdb header (systemctl tells that Dbus is running and active) After googling, it seems to be a bug, related to dconf. Some Fedora’s guys have noticed it too : https://bugzilla.redhat.com/show_bug.cgi?id=975521 Additional info: * package version(s) dconf 0.16.0-1 dbus 1.6.12-1 * config and/or log files etc. Steps to reproduce: Once in Gnome, launch a program that uses dconf to save its settings (typically, gnome-control-center or gnome-terminal) and try to change an option : it won’t be saved, not even will the check-mark stay as you want it to be. |
This task depends upon
Closed by Jan de Groot (JGC)
Monday, 15 July 2013, 15:22 GMT
Reason for closing: Fixed
Additional comments about closing: Fixed in latest glib2 package. In testing at this moment.
Note that we can't fix a corrupt database, you'll have to delete it yourself in that case.
Monday, 15 July 2013, 15:22 GMT
Reason for closing: Fixed
Additional comments about closing: Fixed in latest glib2 package. In testing at this moment.
Note that we can't fix a corrupt database, you'll have to delete it yourself in that case.
That corrected the bug, thanks.
But this is still a strange behaviour, for I always shut down the correct way…
https://bbs.archlinux.org/viewtopic.php?id=165485
But reading the Fedora bugreport, I’m pretty sure there is a bug somewhere, with dconf, or ext4…
By the way : I’m sure I _didn’t_ shutdown uncleanly.