if dconf database corrupted, compiz/unity spins at 100% trying to reopen it
Bug #1339711 reported by
Gerry Boland
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Unity |
New
|
Low
|
Unassigned | ||
unity (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
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/.
WARN 2014-07-09 14:21:18 unityinit <unknown>:0 failed to commit changes to dconf: GDBus.Error:
Would be nice if it didn't try to reopen in a loop as much as it can
To post a comment you must log in.
Status changed to 'Confirmed' because the bug affects multiple users.