After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 795120 - quit plymouth when xdmcp is the only allowed connection.
quit plymouth when xdmcp is the only allowed connection.
Status: RESOLVED FIXED
Product: gdm
Classification: Core
Component: general
3.28.x
Other Linux
: Normal normal
: ---
Assigned To: GDM maintainers
GDM maintainers
Depends on:
Blocks:
 
 
Reported: 2018-04-10 06:39 UTC by Yifan J
Modified: 2018-04-24 07:45 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Patch to quit plymouth in the described situaton. (2.01 KB, patch)
2018-04-10 06:42 UTC, Yifan J 		committed Details | Review

Description Yifan J 2018-04-10 06:39:52 UTC 
gdm is responsible to kill plymouth by spawning the "plymouth quit"
subprocesses in gdm-manager.c. The current code pathes of quiting
plymouth can never be reached when xdmcp is the only connection
allowed. Consequently in the case of

    !show_local_greeter && xdmcp_enabled

the plymouth-quit-wait.service will never quit and the login prompt
will not popup without manual interference. This issue could be
more obviously observed when a downstream like openSUSE which
allows a customized sysconfig to switch the corresponding two
options on a headless server (s390), where the setup is usually:

    DISPLAYMANAGER_REMOTE_ACCESS="yes"
    DISPLAYMANAGER_STARTS_XSERVER="no"
Comment 1 Yifan J 2018-04-10 06:42:39 UTC 
Created attachment 370723 [details] [review]
Patch to quit plymouth in the described situaton.
Comment 2 Ray Strode [halfline] 2018-04-10 13:37:26 UTC 
Thanks