SOLVED: wrong owner of /run/user/1000/dconf/user causes X to freeze
The problem was between the keyboard and the screen :-) I had started X/Gnome applications from the root terminal. And that overwrote the /run/user/1000/dconf/user which then caused the log file explosion. Reporting it as a bug was helpful, because a Michael Biebl there could solve the riddle: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=827639#10 Thanks to everyone who tried to help here. Have a good weekend Andreas On 07/06/2016 16:26, Andreas Krueger wrote: > I would like to file a bug into your bug tracking system, but I don't > know which package to assign it to. > Googling shows that several others are reporting the same problems, but > the exact originator is seemingly not yet pinpointed. > > Is there an open category, for bugs which are not yet assigned to a package? > > Thanks for your help. > > Andreas > > ---- > > > > ------------------------------------------------------------------------ > Bug report: wrong owner of /run/user/1000/dconf/user causes X to freeze > ------------------------------------------------------------------------ > > > I have literally millions of identical log entries of this type: > > cat /var/log/messages | grep /run/user/1000/dconf/user > > Jun 6 15:54:50 laptopacer01 gnome-session[3275]: > (gnome-settings-daemon:3354): > dconf-CRITICAL **: unable to create file '/run/user/1000/dconf/user': > Permission denied. dconf will not work properly. > > > It brings the X system to a total halt, because of: > > cat /var/log/messages | grep /run/user/1000/dconf/user | wc > 11395103 227899102 2277048187 > > > My system is dist-upgraded from wheezy to jessie (following the manual > exactly), and that upgrade seemed to have gone fine (Kudos for that > possibility, I am pretty impressed!) > > Not sure when exactly it happens; but definitely once, after purging > obsolete packages, and then 'apt-get upgrade'; and later once, after > ending eclipse. > > > > On the console I could identify the problem to be a wrong owner: > > ls -la /run/user/1000/dconf > drwx------ 2 andreas andreas 60 Jun 6 17:10 . > drwx------ 9 andreas andreas 180 Jun 6 17:10 .. > -rw------- 1 root root 2 Jun 6 17:10 user > > > The error explosion stopped when I simply tried > chmod a+rwx /run/user/1000/dconf/user > > or even > rm /run/user/1000/dconf/user > > but only after > killall Xorg > I could continue to work. After logging back in. > > (Actually, what would be a softer thing to kill than Xorg ?) > > > > This is how it probably should look like? > > ls -la /run/user/1000/dconf > drwx------ 2 andreas andreas 60 Jun 6 17:10 . > drwx------ 9 andreas andreas 180 Jun 6 17:10 .. > -rw------- 1 andreas andreas 2 Jun 6 17:10 user > > > So for now, my workaround is this one: > > echo "sudo chown andreas:andreas /run/user/1000/dconf/user" > > /usr/local/bin/dconf-repair.sh > chmod 777 /usr/local/bin/dconf-repair.sh > > And when it happens, I quickly switch to a textscreen console, and > execute 'dconf-repair.sh'. I am wondering if I should perhaps put a cron > job that is executing it every 10 seconds? > > > But: What to do? Anyone got a good idea how to fix this? Or how to > identify which package is causing it? Is there a way to install a > watcher, which logs all the programs which are changing a certain file? > > > And: Isn't it better now to remove those 11.3 million lines from > /var/log/messages? How? > > > > Thanks a lot! > Andreas > > > > > >
