if dconf database corrupted, compiz/unity spins at 100% trying to reopen it

[Gerry Boland]

I manged to corrupt my dconf database by using up all my disk space.

Once I freed some space and rebooted, I discovered my dconf database was corrupted.

I also found that compiz was using 100% of one CPU core. $HOME/.local/upstart/unity7.log was filled with this error repeating continually:

WARN 2014-07-09 14:21:18 unityinit <unknown>:0 failed to commit changes to dconf: GDBus.Error:org.gtk.GDBus.UnmappedGEr^Cr.Quark._g_2dfile_2derror_2dquark.Code17: Cannot open dconf database: invalid gvdb header

Would be nice if it didn't try to reopen in a loop as much as it can

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.