https://bugzilla.novell.com/show_bug.cgi?id=833709 https://bugzilla.novell.com/show_bug.cgi?id=833709#c0 Summary: glib/dconf data corruption ... Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Critical Priority: P5 - None Component: GNOME AssignedTo: bnc-team-gnome@forge.provo.novell.com ReportedBy: mmeeks@suse.com QAContact: qa-bugs@suse.de Found By: --- Blocker: --- Ran out of power on my laptop and lost all my dconf settings [ not ideal ]. Seems it's a known issue in glib / dconf; a friend wrote: [snip] We hit the dconf data loss bug in Fedoraland back around the end of the f19 cycle, and fixed it. IIRC, dconf relied on the kernel to behave a certain way in order to preserve data integrity, then a kernel update showed up which changed that behaviour, there was much recrimination back and forth, and then someone fixed it somehow (HANDWAVES FURIOUSLY). Here's some links that should cover the story: https://bugzilla.gnome.org/show_bug.cgi?id=701560 https://bugzilla.gnome.org/show_bug.cgi?id=702394 https://bugzilla.redhat.com/show_bug.cgi?id=975521 I guess you're somehow still running a build of dconf that has the offending code? [/snip] My up-stream bug is: https://bugzilla.gnome.org/show_bug.cgi?id=705563 I guess we should check whether we have the fix: if we do, then there is another problem underneath this one ... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.