The GDM tries to locate the session to complete the registration, but (because of the logic here) ends up trying to register the oldest graphical session, which was the one started by CRD at boot, rather that the one that was just created.Once X is running, gdm-session tries to register with the parent GDM process.GDM spins up a session on a new VT for the user and launches X.After some digging, it appears this is what is happening: We have received some reports that setting up Chrome Remote Desktop on a system prevents that user from logging in locally after a reboot. When the user logs out with the session (not just disconnects), Xvfb and the user session are torn down, and the process restarts at step 1.When the user connects, they pick their session type (e.g., GNOME), and it launches within the user session.On boot, it creates a session for the user of type "x11", spins up Xvfb, and displays a session chooser. By default, Chrome Remote Desktop currently works as follows when enabled on a host:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |