Okay, trying to get gdm to work with a Multiseat configuration. The issue is getting the gdm login to work correctly.
-
When I first boot up the computer gdm only shows the login screen on one terminal of the multiseat configuration.
-
If I logout or perform a “systemctl restart gdm” then both seats get the login screen.
-
But if after that I logout from the second seat then I get booted out of both seats (like a systemctl restart gdm). Also I loose the login screen for the second seat. Basically I return to the beginning…
-
If I logout from seat0 then everything remains okay with the second seat until I logout from it.
-
After I logout from the second seat, and then I login back to the first seat and logout from the first seat (seat0), then I once again get the login screen on the second seat.
On the first boot up “systemctl status gdm” shows:
● gdm.service - GNOME Display Manager
Loaded: loaded (/usr/lib/systemd/system/gdm.service; enabled; vendor preset: disabled)
Active: active (running) since Sat 2020-08-15 23:23:59 EDT; 37s ago
TriggeredBy: ● gdm.path
Process: 895 ExecStartPre=/usr/libexec/gdm-wait-for-drm (code=exited, status=0/SUCCESS)
Main PID: 896 (gdm)
Tasks: 4 (limit: 77002)
Memory: 81.8M
CGroup: /system.slice/gdm.service
└─896 /usr/bin/gdm
Aug 15 23:24:20 clr-joshuamy gdm-password][1543]: pam_unix(gdm-password:session): session opened for user admin by (uid=0)
Aug 15 23:24:20 clr-joshuamy gdm-password][1543]: gkr-pam: gnome-keyring-daemon started properly and unlocked keyring
Aug 15 23:24:22 clr-joshuamy gdm[896]: Child process -961 was already dead.
Aug 15 23:24:22 clr-joshuamy gdm[896]: GdmDisplay: Session never registered, failing
Aug 15 23:24:22 clr-joshuamy gdm[896]: Child process -1156 was already dead.
Aug 15 23:24:22 clr-joshuamy gdm-Xorg-:0[944]: (II) event13 - Logitech M705: device removed
Aug 15 23:24:22 clr-joshuamy gdm-Xorg-:0[944]: (II) event14 - Logitech MK700: device removed
Aug 15 23:24:22 clr-joshuamy gdm-Xorg-:0[944]: (II) UnloadModule: “libinput”
Aug 15 23:24:22 clr-joshuamy gdm-Xorg-:0[944]: (II) UnloadModule: “libinput”
_____________________-
After I performed a logout and reglogin (getting both seats to now show up the gdm login screen) I get the following from a “systemctl status gdm”:
● gdm.service - GNOME Display Manager
Loaded: loaded (/usr/lib/systemd/system/gdm.service; enabled; vendor preset: disabled)
Active: active (running) since Sat 2020-08-15 23:23:59 EDT; 6min ago
TriggeredBy: ● gdm.path
Process: 895 ExecStartPre=/usr/libexec/gdm-wait-for-drm (code=exited, status=0/SUCCESS)
Main PID: 896 (gdm)
Tasks: 46 (limit: 77002)
Memory: 134.9M
CGroup: /system.slice/gdm.service
├─ 896 /usr/bin/gdm
└─2757 /usr/bin/X :1 -background none -noreset -verbose 3 -logfile /dev/null -auth /var/run/gdm/auth-for-gdm-7TSMP0/database -seat seat1 -nolisten tcp
Aug 15 23:29:41 clr-joshuamy gdm-Xorg-:1[2757]: (II) AMDGPU(0): Modeline "1280x960"x0.0 108.00 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync (60.0 kHz e)
Aug 15 23:29:41 clr-joshuamy gdm-Xorg-:1[2757]: (II) AMDGPU(0): Modeline "1024x768"x0.0 94.50 1024 1072 1168 1376 768 769 772 808 +hsync +vsync (68.7 kHz e)
Aug 15 23:29:41 clr-joshuamy gdm-Xorg-:1[2757]: (II) AMDGPU(0): Modeline "800x600"x0.0 56.25 800 832 896 1048 600 601 604 631 +hsync +vsync (53.7 kHz e)
Aug 15 23:29:41 clr-joshuamy gdm-Xorg-:1[2757]: (II) AMDGPU(0): Modeline "640x480"x0.0 36.00 640 696 752 832 480 481 484 509 -hsync -vsync (43.3 kHz e)
Aug 15 23:29:41 clr-joshuamy gdm-Xorg-:1[2757]: (II) AMDGPU(0): Modeline "640x400"x70.0 23.35 640 656 720 800 400 401 404 417 -hsync +vsync (29.2 kHz e)
Aug 15 23:29:53 clr-joshuamy gdm-password][3525]: gkr-pam: unable to locate daemon control file
Aug 15 23:29:53 clr-joshuamy gdm-password][3525]: gkr-pam: stashed password to try later in open session
Aug 15 23:29:53 clr-joshuamy gdm-password][3525]: pam_unix(gdm-password:session): session opened for user admin by (uid=0)
Aug 15 23:29:53 clr-joshuamy gdm-password][3525]: gkr-pam: gnome-keyring-daemon started properly and unlocked keyring
Aug 15 23:29:56 clr-joshuamy gdm[896]: Child process -2768 was already dead.
Can anyone help me understand how to correct this behavior. Also a more general question is simply is this the right forum for this question, or should I simply file it as a “bug”