My curiosity led me to disable wayland in GDM.
# cat /etc/gdm3/daemon.conf
[daemon]
WaylandEnable=false
Strangely enough, nothing appears on seat0, and a GDM session opens on seat1!
(the reverse situation from previously).
# loginctl list-sessions
SESSION UID USER SEAT TTY
2 1000 user seat1
# loginctl show-session 2 -p Type
Type=x11
Looking at the logs, it seems that I hit another bug this time (which is
different from the previous setup with wayland) :
https://bugzilla.redhat.com/show_bug.cgi?id=1404849
In this case, the bug is related to GDM more than systemd : is is possible to
reaffect the bug to GDM and wayland?
For the record, I tried LDM instead of GDM, and it works OK : no wayland at all
but 2 seats working...
---------------------------------
root@live:~# loginctl list-sessions
SESSION UID USER SEAT TTY
4 0 root seat0 /dev/tty2
c11 120 lightdm seat0
11 1002 user1 seat1
7 1000 user2 seat0
4 sessions listed.
root@live:~# loginctl show-session 4 -p Type
Type=tty
root@live:~# loginctl show-session c11 -p Type
Type=x11
root@live:~# loginctl show-session 11 -p Type
Type=x11
root@live:~# loginctl show-session 7 -p Type
Type=x11
As a summary :
Normal configuration : only seat0 working (GDM on wayland, session on X11)
disable wayland in GDM : only seat1 working, probably bug Fedora/1404849 on
seat0
use LDM everywhere (and no wayland) : everything working with X11
