summaryrefslogtreecommitdiff
path: root/po/zh_TW.po
diff options
context:
space:
mode:
authorYifan J <yfjiang@suse.com>2018-04-10 14:17:30 +0800
committerRay Strode <rstrode@redhat.com>2018-04-10 09:37:06 -0400
commitef9977bf2118b2b7810a7669e128249d5ee91eab (patch)
tree036a6a3f55a8c803673246d15d1ad87e3cdc8d07 /po/zh_TW.po
parent9c85139cad544069eefaa87766b5aa9d98082b72 (diff)
downloadgdm-ef9977bf2118b2b7810a7669e128249d5ee91eab.tar.gz
daemon/gdm-manager.c: quit plymouth when xdmcp is the only allowed connection.
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" The proposed patch handles this edge case by quit plymouth immediately when the condition is detected. https://bugzilla.gnome.org/show_bug.cgi?id=795120
Diffstat (limited to 'po/zh_TW.po')
0 files changed, 0 insertions, 0 deletions