Bug#732209: Re: dconf-CRITICAL **: unable to create file '/run/user/1000/dconf/user': Permission denied.

Michael Biebl biebl at debian.org
Thu Apr 14 16:00:12 BST 2016

On Wed, 26 Nov 2014 15:39:15 +0300 =?UTF-8?B?VmxhZCBPcmxvdg==?=
<monsta at inbox.ru> wrote:
> reassign 732209 libpam-systemd 215-6
> thanks
> Hi,
> Messing with /run/user/1000/dconf/user ownership seems to be the work
> of libpam-systemd - somewhat similar things had been happening before,
> as reported in [1] (and the merged reports).

I'm not convinced it is libpam-systemd which is responsible here.

In all cases I read so far, the user was using gksu or su "without -".
So the environment is not cleared and the
XDG_RUNTIME_DIR environment still points to the one from the calling user.

As soon as a dconf-using program is started, this will change the
permissions of the dconf db (as expected).

The user should use "su -" and gksu should make sure to clear the

Afaics, there is not to fix on the libpam-systemd/systemd side here.


Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-systemd-maintainers/attachments/20160414/b20525ef/attachment.sig>

More information about the Pkg-systemd-maintainers mailing list