This does look very likely to be a gdm3 bug, specifically gdm-wayland-
session,
11:11:30.919 worker 4161 starts /usr/libexec/gdm-wayland-session
"gnome-session --session=ubuntu" (pid 5407)
11:11:30.927 gdm-wayland-session: session message bus already running, not
starting another one
11:11:30.930 gdm-wayland-session: Session will register itself
11:11:30.944 old user@1000 finishes stopping dbus.service <- the bus it just
reused dies
11:11:30.944 worker: child (pid:5407) done (status:0)
11:11:30.946 GdmDisplay: Session never registered, failing
* Force Stop kills the local session; its user@1000 teardown (including
the user D-Bus session bus) is still running when GDM releases the
pending remote session.
* gdm-wayland-session probes for an existing user bus, finds the dying
one, reuses it. Bus stops 15ms later. It exits "cleanly" (status 0) 25ms
after starting. gnome-session never registers, then GDM fails the
display and RDP client stranded on the dead virtual monitor.
* Second connect works because teardown completed long ago so no stale
bus, fresh bus started.
Didn't find anything exactly the same upstream: gdm#1085 is a different
remote-display race, gdm#1062 same log line but boot-time trigger.
** Changed in: gdm3 (Ubuntu)
Importance: Undecided => High
** Changed in: gnome-remote-desktop (Ubuntu)
Status: Triaged => Invalid
** Changed in: gnome-remote-desktop (Ubuntu)
Assignee: Charles (charles05) => (unassigned)
** Changed in: gnome-remote-desktop (Ubuntu)
Importance: High => Undecided
** Changed in: gdm3 (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2169088
Title:
Remote Login: black screen after force-stopping local session
("GdmDisplay: Session never registered")"
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2169088/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs