Bug#732209: dconf-CRITICAL **: unable to create file '/run/user/1000/dconf/user': Permission denied.
linasvepstas at gmail.com
Thu Sep 15 18:21:25 BST 2016
On Thu, Sep 15, 2016 at 6:45 AM, Vlad Orlov <monsta at inbox.ru> wrote:
> Is su actually used for running graphical apps?
In my case, I either accidentally typed into an su window, or possibly ran
the gconf editor as root, for some possibly good or bad reason, possibly
having to do with xdm, gdm whateverdm, or possibly some intentional or
unintentional debugging of audio or video playback. This is the "shit
happens" category, and based on the rate of reports streaming in, "shit
happens" every now and then for everyone. If it happened a lot, the problem
would be fixed. If it happened very rarely, there would be no heat.
> There's also this problem... no one still volunteered to actually help
> su or gksu/libgksu.
"fixing" su could have very long-running reprecussions: it is a
40-year-old utility, and I know for a fact that there are people out there
who run 40-year-old shell scripts (I have a friend who works at a company
that specializes in porting ancient, undocumented code to modern systems.)
If you "fix" it, the various vendors (red-hat, ubuntu, debian) will very
slowly start accumulating bug reports related to the change. These reports
will arrive at the rate of a few a year, for a decade (similar to the rate
of reporting on this bug-- which is now 3-4 years old, and gets a new
complaint every now and then). The knee-jerk reaction will be to undo
whatever the "fixes" were. So the volunteer needs to not only fix the
problem, update the man page, etc. but then be persistent for many years.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Pkg-systemd-maintainers