XDMCP to GDM display delay

General support questions
Post Reply
davymatt
Posts: 28
Joined: 2013/06/12 16:21:14
Location: Salisbury, UK
Contact:

XDMCP to GDM display delay

Post by davymatt » 2020/02/11 10:00:55

Hi
I'm having a bit of trouble with GDM using a remote connection via XDMCP. It works OK connecting to a MATE desktop, but there is a dramatic delay (about 20s) between connecting and the login screen appearing.

Does anyone have any idea how I might reduce this delay?

From my searching I did the following
I disabled PulseAudio. We don't use audio anyway. Reduced delay by about 2s
Added [service]Type=idle to custom.conf. No noticeable effect.

journalctl output below

Code: Select all

Feb 11 09:00:21 test.example.com gdm[2611]: GdmSession: type (null), program? yes, seat (null)
Feb 11 09:00:21 test.example.com gdm-launch-environment][2989]: GdmSessionWorker: session display mode set to reuse-vt
Feb 11 09:00:21 test.example.com gdm-launch-environment][2989]: GdmSessionWorker: Set PAM environment variable: 'XDG_SESSION_TYPE=x11'
Feb 11 09:00:21 test.example.com gdm-launch-environment][2989]: GdmSessionWorker: attempting to change state to ACCOUNT_DETAILS_SAVED
Feb 11 09:00:21 test.example.com gdm-launch-environment][2989]: GdmSessionWorker: user gdm, not fully loaded yet, will save account details later
Feb 11 09:00:21 test.example.com gdm-launch-environment][2989]: AccountsService: ActUserManager: trying to track new user with username gdm
Feb 11 09:00:21 test.example.com gdm-launch-environment][2989]: AccountsService: ActUserManager: finding user 'gdm' state 1
Feb 11 09:00:21 test.example.com gdm-launch-environment][2989]: AccountsService: ActUserManager: finding user 'gdm' state 2
Feb 11 09:00:21 test.example.com gdm-launch-environment][2989]: AccountsService: ActUserManager: Looking for user 'gdm' in accounts service
Feb 11 09:00:21 test.example.com gdm-launch-environment][2989]: AccountsService: ActUserManager: Found object path of user 'gdm': /org/freedesktop/Accounts/User42
Feb 11 09:00:21 test.example.com gdm-launch-environment][2989]: AccountsService: ActUserManager: finding user 'gdm' state 3
Feb 11 09:00:21 test.example.com gdm-launch-environment][2989]: AccountsService: ActUserManager: user 'gdm' fetched
Feb 11 09:00:21 test.example.com gdm-launch-environment][2989]: AccountsService: ActUserManager: user gdm is now loaded
Feb 11 09:00:21 test.example.com gdm-launch-environment][2989]: AccountsService: ActUserManager: user gdm was not yet known, adding it
Feb 11 09:00:21 test.example.com gdm-launch-environment][2989]: AccountsService: ActUserManager: tracking user 'gdm'
Feb 11 09:00:21 test.example.com gdm-launch-environment][2989]: AccountsService: ActUserManager: not yet loaded, so not emitting user-added signal
Feb 11 09:00:21 test.example.com gdm-launch-environment][2989]: AccountsService: ActUserManager: no pending users, trying to set loaded property
Feb 11 09:00:21 test.example.com gdm-launch-environment][2989]: AccountsService: ActUserManager: already loaded, so not setting loaded property
Feb 11 09:00:21 test.example.com gdm-launch-environment][2989]: GdmSessionSettings: saved session is
Feb 11 09:00:21 test.example.com gdm-launch-environment][2989]: GdmSessionSettings: saved language is
Feb 11 09:00:21 test.example.com gdm-launch-environment][2989]: GdmSessionWorker: saving account details for user gdm
Feb 11 09:00:21 test.example.com gdm-launch-environment][2989]: AccountsService: ActUserManager: finished handling request for user 'gdm'
Feb 11 09:00:21 test.example.com gdm-launch-environment][2989]: AccountsService: ActUserManager: unrefing manager owned by fetch user request
Feb 11 09:00:21 test.example.com gdm-launch-environment][2989]: GdmSessionWorker: attempting to change state to SESSION_OPENED
Feb 11 09:00:21 test.example.com gdm-launch-environment][2989]: GdmSessionWorker: not setting XDG_VTNR since not seat0
Feb 11 09:00:21 test.example.com gdm[2611]: GdmSession: Emitting 'session-opened' signal
Feb 11 09:00:21 test.example.com gdm[2611]: GdmDisplay: Greeter session opened
Feb 11 09:00:21 test.example.com gdm[2611]: GdmDisplay: session id: c2
Feb 11 09:00:21 test.example.com gdm[2611]: GdmSession: Stopping all conversations except for gdm-launch-environment
Feb 11 09:00:21 test.example.com gdm[2611]: GdmSession: type (null), program? yes, seat (null)
Feb 11 09:00:21 test.example.com gdm[2611]: GdmSession: type (null), program? yes, seat (null)
Feb 11 09:00:21 test.example.com gdm[2611]: GdmSession: Emitting 'session-started' signal with pid '2993'
Feb 11 09:00:21 test.example.com gdm[2611]: GdmDisplay: Greeter started
Feb 11 09:00:40 test.example.com gdm[2611]: GdmManager: trying to open new session
Feb 11 09:00:40 test.example.com gdm[2611]: GdmDBusServer: new connection 0x55d08a784b80
Feb 11 09:00:40 test.example.com gdm[2611]: GdmSession: Handling new connection from outside
Feb 11 09:00:40 test.example.com gdm[2611]: GdmManager: client connected
The initial connection completes at 09:00:21, but the login prompt does not appear until 09:00:40.

custom.conf

Code: Select all

# GDM configuration storage

[daemon]
WaylandEnable=false
AddGtkModules=false
[security]

[xdmcp]
Enable=true
HonorIndirect=false
PingIntervalSeconds=5
DisplaysPerHost=4

[chooser]

[service]
Type=idle

[debug]
# Uncomment the line below to turn on debugging
Enable=true
CentOS Linux release 7.7.1908 (Core) (fully updated)
HP Proliant DL380G7 30Gb memory

Dave

Post Reply

Return to “CentOS 7 - General Support”