Am 14.04.2016 um 17:00 schrieb Michael Biebl: > On Wed, 26 Nov 2014 15:39:15 +0300 =?UTF-8?B?VmxhZCBPcmxvdg==?= > <[email protected]> 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 > environment. > > Afaics, there is not to fix on the libpam-systemd/systemd side here.
To verify that point: Open a shell unset XDG_RUNTIME_DIR gksu xterm → XDG_RUNTIME_DIR won't be set I studied the su man page and it resets $HOME, $SHELL, $USER, $LOGNAME, $PATH, and $IFS Contrary to sudo, which by default clears the environment (or pkexec). -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
