Hi On Fri, Jan 3, 2014 at 3:24 PM, Matthew Monaco <m...@0x01b.net> wrote: > I was having trouble getting a session on seat1 with v208, so I moved to git > which has a nicer error message than EINVAL: > > pam_systemd(lightdm:session): Asking logind to create session: uid=1000 > pid=637 > service=lightdm type=x11 class=user seat=seat1 vtnr=2 tty= display=:1 > remote=no > remote_user= remote_host=
Yeah, that vtnr=2 line is wrong. You really shouldn't set any VTNR if seat!=seat0. I think the correct fix would be to set "vtnr=0" in get_seat_from_display() in pam-module.c if we're not on seat0. As Lennart changed that during the sd-bus transition (if I read the history correctly..), maybe he can comment on that. Another related commit is this: http://cgit.freedesktop.org/systemd/systemd/commit/src/login?id=c506027af881a9e4210845a7a8a6ec5910aa0f3b Which I am still not sure is the correct thing to do. Thanks David > > pam_systemd(lightdm:session): Failed to create session: Seat has no VTs but VT > number not 0 > > I'm using lightdm 1.8.5. My X servers are > > /usr/sbin/X :0 -config xorg-seat0.conf -seat seat0 -auth /run/lightdm/root/:0 > -nolisten tcp vt1 -novtswitch > > /usr/sbin/X -sharevts :1 -config xorg-seat1.conf -seat seat1 -auth > /run/lightdm/root/:1 -nolisten tcp vt2 -novtswitch > > (I have no problems with seat0). > > This same setup used to work with systemd ~v205, but I have used multiseat in > a > while do to a move. > > So, I don't understand where the failure is. Is lightdm starting X on the > wrong > vt? Why is vt2/tty2 not allowed for a second seat? > _______________________________________________ > systemd-devel mailing list > systemd-devel@lists.freedesktop.org > http://lists.freedesktop.org/mailman/listinfo/systemd-devel _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
