Good find! Perhaps I'll upload the patched X to my PPA.
> But multiseat still doesn't work. I can login only in one of two
> seats. Pasword field disappears when I want select other user for
> second seat. Or if correct user already is selected, I can write in
> password, but nothing happens when i try to login.
So my multiseat changes don't appear to affect this particular bug.
That's unfortunate.
I know that when selecting a user, LightDM (or maybe it's
unity-greeter, I can't remember) does some PAM stuff to see if it's
possible to log in without a password. Perhaps you have an uncommon
PAM setup that is confusing LightDM/unity-greeter?
> *) Tested with different seat names. First seat - seat01, second
> seat - seat1. Added udev rules to assign video card and usb hub for
> seat01. Both seats started up, i was able to login in first seat,
> but there was problems - huge memory leaks. In attached zip are log
> files for xorg and lightdm. My .xsession-errors was full of error
> lines:
I'll take a look when I next have the time.
> loginctl list-seats lists only one seat. shouldn't it list two
> seats?
Yes, it should. If I understand correctly, the 'master-of-seat' udev
tag should cause logind to create the second seat. (To avoid starting
an X server before a video card is detected, logind won't create a
seat until a device tagged with 'master-of-seat' appears.) Does
'udevadmin info --export-db' show the 'master-of-seat' tag on your
video card?
> Patched xorg with this /bugzilla. redhat. com/attachment. cgi?id= 751266& action= diff) /bugzilla. redhat. com/show_ bug.cgi? format= multiple& id=962907)
> (https:/
> patch from this
> (https:/
> bug report. And now lightdm shows up on second seat. Calvin Morrow
> says that fix probably even simplier, read comment #20.
Good find! Perhaps I'll upload the patched X to my PPA.
> But multiseat still doesn't work. I can login only in one of two
> seats. Pasword field disappears when I want select other user for
> second seat. Or if correct user already is selected, I can write in
> password, but nothing happens when i try to login.
So my multiseat changes don't appear to affect this particular bug.
That's unfortunate.
I know that when selecting a user, LightDM (or maybe it's unity-greeter?
unity-greeter, I can't remember) does some PAM stuff to see if it's
possible to log in without a password. Perhaps you have an uncommon
PAM setup that is confusing LightDM/
> *) Tested with different seat names. First seat - seat01, second
> seat - seat1. Added udev rules to assign video card and usb hub for
> seat01. Both seats started up, i was able to login in first seat,
> but there was problems - huge memory leaks. In attached zip are log
> files for xorg and lightdm. My .xsession-errors was full of error
> lines:
I'll take a look when I next have the time.
> loginctl list-seats lists only one seat. shouldn't it list two
> seats?
Yes, it should. If I understand correctly, the 'master-of-seat' udev
tag should cause logind to create the second seat. (To avoid starting
an X server before a video card is detected, logind won't create a
seat until a device tagged with 'master-of-seat' appears.) Does
'udevadmin info --export-db' show the 'master-of-seat' tag on your
video card?