The issue specifically: 'dconf update' emits a signal that says "everything has changed"
Meanwhile, we have the configuration migration stuff watching for changes and assuming that if there was a change in dconf it means that we should sync it up to gconf. The trouble comes that "everything has changed" actually only means "everything has *potentially* changed". One way we can work around this is the "change-event" signal on GSettings. It allows two things: 1) We can find out the difference between "everything changed" and "one thing changed". 2) We can return TRUE here to stop the signal from going further. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1071950 Title: gnome-settings-daemon dconf to gconf plugin causes settings to be lost To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1071950/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
