Update to systemd 198 causes logind/lxdm trouble

Eishorn · 2013-03-16 17:12:03

Hi,

after upgrading systemd 197-4 to 198-1 yesterday, I have some trouble with session management.
First login to xfce via lxdm works fine, but if I log out and into my second user account (user2, UID=1001), loginctl shows the following (with root on tty1):

#loginctl list-sessions
   SESSION        UID USER             SEAT            
         3          0 root             seat0           
         4       1000 user1            seat0           

2 sessions listed.

This, of course, causes some problems, eg. pulse failing to start. If I log out again, lxdm occasionally crashes with

(lxdm-greeter-gtk:819): GLib-GObject-WARNING **: invalid (NULL) pointer instance

(lxdm-greeter-gtk:819): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed

in lxdm.log - journalctl shows nothing related.
Downgrading systemd and systemd-sysvcompat to 197-4 again solves the problem - I've read that there were some major changes in 198, maybe I'm just bad at googling stuff and missed something that needs to be changed?

Eishorn · 2013-03-18 13:14:48

Ok, I managed to find some journalctl output (I wonder why I didn't see it two days ago):

Mär 18 13:28:25 hostname lxdm-binary[307]: pam_unix(lxdm:session): session opened for user user2 by (uid=0)
Mär 18 13:28:25 hostname lxdm-binary[307]: pam_loginuid(lxdm:session): set_loginuid failed
Mär 18 13:28:26 hostname systemd-coredump[602]: Process 578 (compiz) dumped core.

Besides, I'm sorry If I posted this in the wrong subforum since this is a problem after updating packages, not while updating them...

hoschi · 2013-03-25 13:51:34

Would you mind to check this: https://bugs.freedesktop.org/show_bug.cgi?id=62676

Maybe their is a relation.

Eishorn · 2013-03-26 11:21:04

Thanks, I can reproduce the behaviour described there.
Here are the logfiles, I am logged into xfce via lxdm on tty7 and did a login and logout as root on tty1:

loginctl list-sessions
   SESSION        UID USER             SEAT            
         1       1000 user1            seat0

journalctl -f
Mär 26 11:50:55 blechdepp-lin64 login[610]: pam_unix(login:session): session opened for user root by LOGIN(uid=0)
Mär 26 11:50:55 blechdepp-lin64 systemd-logind[295]: New session 3 of user root.
Mär 26 11:50:55 blechdepp-lin64 login[610]: ROOT LOGIN ON tty1
Mär 26 11:53:04 blechdepp-lin64 login[610]: pam_unix(login:session): session closed for user root
Mär 26 11:53:04 blechdepp-lin64 systemd[1]: getty@tty1.service holdoff time over, scheduling restart.
Mär 26 11:53:04 blechdepp-lin64 systemd[1]: Stopping Getty on tty1...
Mär 26 11:53:04 blechdepp-lin64 systemd[1]: Starting Getty on tty1...
Mär 26 11:53:04 blechdepp-lin64 systemd[1]: Started Getty on tty1.
Mär 26 11:53:04 blechdepp-lin64 systemd-logind[295]: Removed session 3.

ls /run/systemd/sessions
1  1.ref  3

#loginctl seat-status seat0:
http://pastebin.com/7nZ7YnzS

loginctl session-status 3
Failed to issue method call: No such file or directory

I guess there's a relation, it's obviously more than a lxdm issue. Session 3 shouldn't have a file in /run/systemd/sessions anymore, should it? My workaround here https://bbs.archlinux.org/viewtopic.php?id=159958 is still pretty ugly and works for lxdm logouts only. Rebooting/shutting down with xfce4-session-logout works somehow, too. Think I'll check my files against David's post in the other thread and see if there's a hint.

hoschi · 2013-03-26 14:18:29

Thanks you.

Eishorn · 2013-03-27 11:41:22

I finally figured a way to do a #systemctl reboot with a normal user after loggin in and out with root/foobar on a random tty. After logging out of the tty accounts I checked /run/systemd/sessions/ again.
Here are 2 files for any active session ID x (x and x.ref). Also there was one file for each session I opened and closed on the ttys. After I deleted all of those files left over from a root shell in xfce (except the ones for the active session), I could reboot again from a user shell opened in xfce.

So it appears that the files in this dir are effectively blocking #systemctl shutdown/reboot - next step would be to have them deleted automatically when their session is closed. Don't know if this will affect the lxdm problem, too but I guess I'll find out

Eishorn · 2013-03-28 17:41:35

No luck with lxdm so far... apparently systemd believes the whole session belongs to the wrong user; here's what I get from a terminal when I switch users (logging out and in that is, not lxdm -c) without restarting lxdm in between:
http://pastebin.com/6N2hCGzR

Just for the record, here's what it looks like after restarting my login manager:
http://pastebin.com/ENc5BNia

I don't know if I'll have any time to go into the issue further within the next days, it's not urgent for me since I've got a workaround (https://bbs.archlinux.org/viewtopic.php?id=159958).
I know this will keep bugging me somehow though

Last edited by Eishorn (2013-03-28 17:43:11)

Arch Linux

#1 2013-03-16 17:12:03

Update to systemd 198 causes logind/lxdm trouble

#2 2013-03-18 13:14:48

Re: Update to systemd 198 causes logind/lxdm trouble

#3 2013-03-25 13:51:34

Re: Update to systemd 198 causes logind/lxdm trouble

#4 2013-03-26 11:21:04

Re: Update to systemd 198 causes logind/lxdm trouble

#5 2013-03-26 14:18:29

Re: Update to systemd 198 causes logind/lxdm trouble

#6 2013-03-27 11:41:22

Re: Update to systemd 198 causes logind/lxdm trouble

#7 2013-03-28 17:41:35

Re: Update to systemd 198 causes logind/lxdm trouble

Board footer