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

On Thu, Sep 15, 2016 at 6:45 AM, Vlad Orlov 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,

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

Hi, Just found a link to a pam module [1] (posted in the comment at [2]). > It's a pam module that removes the XDG_RUNTIME_DIR environment variable from > the environment if the user authenticating is different from the user owning > it. This is for the case of programs like gksu clobbering the

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

Hi, Is su actually used for running graphical apps? Most people seem to use gksu for that. But gksu --help shows a weird warning about using -l argument: --login, -l Make this a login shell. Beware this may cause problems with the Xauthority magic. Run xhost to allow the target

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

The suggestion below, that the core issue is that "su" is leaking the user-space env variables into the root shell, where they are then used to clobber the user-space, seems like a good root-cause analysis of the bug. I agree, it seems like "su" needs to be fixed. I the meanwhile, can we get a

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

CCing the login maintainer, maybe he has some input on this matter. Am 10.06.2016 um 16:03 schrieb Martin Pitt: > Control: tag -1 -moreinfo -unreproducible +wontfix > > Vlad Orlov [2016-04-20 17:00 +0300]: >> You can check [1] to get some info about libpam-systemd doing >> something wrong here.

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

Control: tag -1 -moreinfo -unreproducible +wontfix Vlad Orlov [2016-04-20 17:00 +0300]: > You can check [1] to get some info about libpam-systemd doing > something wrong here. > [1] https://bugzilla.redhat.com/show_bug.cgi?id=753882 This was fixed up to the extent possible in

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

Processing control commands: > tag -1 -moreinfo -unreproducible +wontfix Bug #732209 [libpam-systemd] unable to create file '/run/user/1000/dconf/user': Permission denied Bug #766464 [libpam-systemd] gksu pluma sets the ownership of /run/user/1000/dconf/user to root:root Bug #767173

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

Hi, > I'm not convinced it is libpam-systemd which is responsible here. You can check [1] to get some info about libpam-systemd doing something wrong here. Also we had this issue for months in Linux Mint before Clement Lefebvre made a patch [2] that fixed it. After the patched libpam-systemd

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

Hi, BTW, this only happens with GNOME sessions. With other window managers (e.g. LXDE, Openbox) it does *not*. Therefore, I do not think it's a systemd bug, rather it's related to GNOME. Do you agree to reassign this bug against either the 'gnome-session' or the 'gnome-shell' package? No, I

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

Hi, I just decided to nofity all the participants here, in case this new info might be interesting or useful :) ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org