Because of incorrect system shutdown (system was hang) gvdb is destroyed. Are possible to making gvdb self-recoverable ?
@mikhail.v.gavrilov
Submitted by Mikhail Gavrilov Assigned to dco..@..e.bugs
Link to original bug (#753667)
Description
Because of incorrect system shutdown (system was hang) gvdb is destroyed. Are possible to making gvdb self-recoverable ?
$ rpm -q dconf dconf-0.24.0-2.fc23.x86_64
$ journalctl | grep dconf
авг 15 19:46:58 localhost.localdomain org.gnome.Totem[1949]: (totem:22182): 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 авг 15 19:46:58 localhost.localdomain org.gnome.Totem[1949]: (totem:22182): 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 авг 15 19:48:39 localhost.localdomain gnome-session[1954]: (gnome-shell:2178): 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 авг 15 19:48:39 localhost.localdomain gnome-session[1954]: (gnome-shell:2178): 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 авг 15 22:01:11 localhost.localdomain gnome-calculator.desktop[10634]: (gnome-calculator:10634): 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 авг 15 22:01:11 localhost.localdomain gnome-calculator.desktop[10634]: (gnome-calculator:10634): 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
Version: 0.24.x