GNOME Bugzilla – Bug 794336
Start gdm-session-worker earlier
Last modified: 2018-05-24 11:48:22 UTC
Created attachment 369688 [details] SVG file created by systemd-bootchart On the Dell XPS 13 9370 with Debian Sid/unstable with only one local user, it looks like GDM 3.28 waits for the NetworkManger before starting the session worker(?) to render the user list. See the attached SVG generated by systemd-bootchart, showing that NetworkManager takes 1.6 seconds, and the gdm-session-worker starts at 4.1 s. Then another 300 ms pass by before gdm-wayland-session starts. It’d be great, if the user list could be display much earlier to improve the user experience on fast systems.
Following the advise from #gdm@irc.gnome.org, disabling NetworkManager didn’t change anything, so there might be a different dependency. Maybe enabling debug logs helps. Below 0.5 seconds seem to pass. ``` Mar 15 16:43:17.544279 xps139370 gdm3[612]: GdmManager: GDM starting to manage displays Mar 15 16:43:17.544892 xps139370 gdm3[612]: Could not ping plymouth: Failed to execute child process “/bin/plymouth” (No such file or directory) Mar 15 16:43:18.032450 xps139370 gdm3[612]: GdmLocalDisplayFactory: Adding display on seat seat0 ```
Created attachment 369745 [details] GDM debug log (`journalctl -o short-precise -b -u gdm`)
Created attachment 369746 [details] Graph from systemd-bootchart with NetworkManager disabled
Created attachment 369872 [details] SVG file created by systemd-bootchart with automatic login of user
-- GitLab Migration Automatic Message -- This bug has been migrated to GNOME's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gdm/issues/368.