There's only one GDM greeter in this case. The bug is that if there's *any* other PAM/loginctl session for the user of type "x11", GDM will fail to log the user in without the above patch.
When Chrome Remote Desktop starts at boot, it creates such a user session (via PAM) under the user who has configured it. This session is used to run the Chrome Remote Desktop host process, an instance of Xvfb, and, if the user hasn't configured a custom CRD session script to run at boot, a very simple session chooser. Even if the session only contains sleep 5000, however, its mere presence is enough to break GDM for that user. I experimented with setting the session type used by CRD to "unspecified", but that ended up breaking programs running with the CRD session, so fixing the GDM bug seems to be the only path forward. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874262 Title: User session does not start: Problem with chrome-remote-desktop To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1874262/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
