Re: wrong owner of /run/user/1000/dconf/user causes X to freeze
On Saturday 25 June 2016 10:20:27 posti...@andreaskrueger.de wrote: > 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. > It may have been PEBAC, but that has exposed a bug. No way that a root session of anything should over-write or change a single bit in /run/usr/1000. Whatever it did, should have taken place in /run/usr/0, aka root/. > 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 rootroot 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 Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) Genes Web page <http://geneslinuxbox.net:6309/gene>
Re: wrong owner of /run/user/1000/dconf/user causes X to freeze
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 rootroot 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 > > > > > >
Re: wrong owner of /run/user/1000/dconf/user causes X to freeze
Thanks for your answers. Helpful - and funny :-) > no, this is a perfectly fine list to ask that question. Good. > The problem is that the answer is "systemd". > In this case dconf, So I have 2 choices now. Thanks! > and ask the maintainer to reassign the bug if it's wrong. Good point, thanks! > In this case it has already been reported (quite a few times): > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769889 ... and wow - all the way back to Nov 2014 even. Interesting. Feels good not to be alone in this ;-) There in that thread, I like this sentence > it makes the system quite unstable in an undebian way. :-) Perhaps I should rather post into that existing "libpam-systemd" thread, instead of starting a new bug report. Last question: What about my idea - anyone knows such a tool? > > 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? Plus which specific change they have done. In this case: Change owner to "root" / Re-create, owned by root. Because then after logging for a while, I could submit a list of all culprits. If such a watcher tool does not exist yet ... then I have found a new niche that can be filled with to-be-created code, right? Best starting point for such a script? First idea would be dumb regular polling, and comparing to last stored state, and logging all changes. But then I would still only know WHEN it happens, not WHO has caused it. Which level of the stack all the way down to the file sytem does know about the actor of a file change? Thx. And *hahaha*: > > The problem is that the answer is "systemd". > > > Even before June is over you win this month's prize > for the most useless post to -user. The committee is > unaminous on this. Well done! Wear your badge > with pride. The question was > How can I file a Debian bug report, > without assigning it to a specific package? > Your answer is so tangential it requires use of the > axe-to-grind package to make headway with a response. Not even sure what exactly that might mean, but I guess: 100 out of 100 points for the sarcastic comment of the day. I just ... love the people of the internets :-)
Re: wrong owner of /run/user/1000/dconf/user causes X to freeze
On Wed 08 Jun 2016 at 12:31:48 -0400, Dan Ritter wrote: > On Wed, Jun 08, 2016 at 05:36:51PM +0200, posti...@andreaskrueger.de wrote: > > > > About my question: > > wrong owner of /run/user/1000/dconf/user causes X to freeze > > https://lists.debian.org/debian-user/2016/06/msg00275.html > > > > > > Is debian-user@ perhaps the wrong list for such a question? Which one > > would be better? > > > > no, this is a perfectly fine list to ask that question. > > The problem is that the answer is "systemd". Even before June is over you win this month's prize for the most useless post to -user. The committee is unaminous on this. Well done! Wear your badge with pride. The question was How can I file a Debian bug report, without assigning it to a specific package? Your answer is so tangential it requires use of the axe-to-grind package to make headway with a response.
Re: wrong owner of /run/user/1000/dconf/user causes X to freeze
On Tue, 2016-06-07 at 16:26 +0200, posti...@andreaskrueger.de 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? You can usually make a best guess for the package. In this case dconf, and ask the maintainer to reassign the bug if it's wrong. In this case it has already been reported (quite a few times): https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769889 You can also file bugs against the "general" pseudo package, but it's generally discouraged. Better to ask for guidance on the list. -- Cheers, Sven Arvidsson http://www.whiz.se PGP Key ID 6FAB5CD5 signature.asc Description: This is a digitally signed message part
Re: wrong owner of /run/user/1000/dconf/user causes X to freeze
On Wed, Jun 08, 2016 at 05:36:51PM +0200, posti...@andreaskrueger.de wrote: > > About my question: > wrong owner of /run/user/1000/dconf/user causes X to freeze > https://lists.debian.org/debian-user/2016/06/msg00275.html > > > Is debian-user@ perhaps the wrong list for such a question? Which one > would be better? > no, this is a perfectly fine list to ask that question. The problem is that the answer is "systemd". -dsr-
Re: wrong owner of /run/user/1000/dconf/user causes X to freeze
About my question: wrong owner of /run/user/1000/dconf/user causes X to freeze https://lists.debian.org/debian-user/2016/06/msg00275.html Is debian-user@ perhaps the wrong list for such a question? Which one would be better? How can I file a Debian bug report, without assigning it to a specific package? What do you think about my ideas? > ... 'dconf-repair.sh'. I am wondering if I should perhaps > put a cron job that is executing it every 10 seconds? > ... 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? I don't want to repost my -long, sorry- error description. You find the full text here: https://lists.debian.org/debian-user/2016/06/msg00275.html Thanks!
wrong owner of /run/user/1000/dconf/user causes X to freeze
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 rootroot 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
