[cc'ing systemd maintainers for their input]
Hi all,
On a fresh qemu install dist-upgraded to sid (wheezy install;
dist-upgrade and lastly gnome install) I'm consistently getting the
issue described by Gabriel Mainberger, namely that gdm gets the wrong
XDG_RUNTIME_PATH and fails to start. But interestingly it only happens
if I restart gdm. So it actually works on boot, but if I try to restart
it, I get the following dbus calls from libpam-systemd:
-------------
method call sender=:1.59 -> dest=org.freedesktop.login1 serial=2
path=/org/freedesktop/login1; interface=org.freedesktop.login1$Manager;
member=CreateSession
uint32 117
uint32 3462
string "gdm-launch-environment"
string "x11"
string "greeter"
string "seat0"
uint32 7
string ""
string ":0"
boolean false
string ""
string ""
array [
]
array [
]
boolean false
method return sender=:1.17 -> dest=:1.59 reply_serial=2
string "2"
object path "/org/freedesktop/login1/session/_32"
string "/run/user/1000"
(dbus-monitor too dumb to decipher arg type 'h')
string ""
uint32 0
boolean true
-------------
Note that we're requesting a login for uid=117 and getting
runtime_path=/run/user/1000.
This is the result when run under "su". The returned path is
"/run/user/0" if run directly by root. This doesn't seem to be impacted
by the /proc/*/loginuid of systemd-logind (even if logind was started by
a su'ed uid 1000, we still get /run/user/<real uid> when running "gdm3
start").
At first I wasn't sure where gnome-session was getting the wrong
XDG_RUNTIME_PATH, so I attempted calling "env - /usr/sbin/service gdm3
restart", but this changed nothing.
Incidently, this system is also affected by #728180, so maybe the fact
that I had to kill Xorg (and with it gnome-session) after stopping gdm3
might have something to do with it?
I'm not sure if this is a problem with gdm3, gnome-session or
systemd-logind, and I'm unfortutately stumped as to ways of debugging
this better.
Cheers
--
Leo "costela" Antunes
[insert a witty retort here]
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
