remote lightdm not working after update to 7.4

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

remote lightdm not working after update to 7.4

Post by davymatt » 2017/11/10 17:22:15

Hi

I have a problem with lightdm since updating a server to 7.4. I cannot connect to the server using a remote PC (using X-Win32 14.0.54 2017 if that is an issue)
Can connect to a server running 7.3 with very similar setup. The change to the lightdm configuration file where SeatDefaults was changed to Seat:* looks OK to me, but remote systems seem to be allocated Seat (null), which I don't understand. lightdm works OK on the console.

Could anyone give me any clues on what might make this work?

Configuration file not very complicated

Code: Select all

[LightDM]

[Seat:*]
greeter-hide-users=true

[XDMCPServer]
enabled=true

[VNCServer]
Messages in /var/log/lightdm/lightdm.conf (only hostname sanitised)

Code: Select all

[+1365.42s] DEBUG: Got Query(authentication_names=[]) from 10.97.80.198:54254
[+1365.42s] DEBUG: Send Willing(authentication_name='' hostname='server.example.com' status='') to 10.97.80.198:54254
[+1365.42s] DEBUG: Got Request(display_number=1 connections=[10.97.80.198] authentication_name='' authentication_data= authorization_names=['MIT-MAGIC-COOKIE-1' 'XDM-AUTHORIZATION-1'] manufacturer_display_id='') from 10.97.80.198:54254
[+1365.42s] CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
[+1365.43s] DEBUG: Send Accept(session_id=27065 authentication_name='' authentication_data= authorization_name='MIT-MAGIC-COOKIE-1' authorization_data=0F694582FBB494B335F2BBF3ADBB1BBF) to 10.97.80.198:54254
[+1365.43s] DEBUG: Got Manage(session_id=27065 display_number=1 display_class='MIT-unspecified') from 10.97.80.198:54254
[+1365.43s] DEBUG: Seat (null): Loading properties from config section Seat:*
[+1365.43s] DEBUG: Seat (null): Starting
[+1365.43s] DEBUG: Seat (null): Creating greeter session
[+1365.43s] DEBUG: Seat (null): Creating display server of type x
[+1365.43s] DEBUG: DisplayServer x-10.97.80.198-1: Connecting to XServer 10.97.80.198:1
[+1365.43s] DEBUG: Seat (null): Display server ready, starting session authentication
[+1365.43s] DEBUG: Session: Not setting XDG_VTNR
[+1365.43s] DEBUG: Session pid=1509: Started with service 'lightdm-greeter', username 'lightdm'
[+1365.43s] DEBUG: Registering seat with bus path /org/freedesktop/DisplayManager/Seat1
[+1365.45s] DEBUG: Session pid=1509: Authentication complete with return value 0: Success
[+1365.45s] DEBUG: Seat (null): Session authenticated, running command
[+1365.45s] DEBUG: Session pid=1509: Not setting XDG_VTNR
[+1365.45s] DEBUG: Session pid=1509: Running command /usr/sbin/lightdm-gtk-greeter
[+1365.45s] DEBUG: Session pid=1509: Logging to /var/log/lightdm/(null)-greeter.log
[+1365.47s] DEBUG: Activating login1 session c2
[+1365.47s] WARNING: Error activating login1 session: GDBus.Error:org.freedesktop.DBus.Error.NotSupported: Operation not supported
[+1365.50s] DEBUG: Greeter closed communication channel
[+1365.50s] DEBUG: Session pid=1509: Exited with return value 11
[+1365.50s] DEBUG: Seat (null): Session stopped
[+1365.50s] DEBUG: Seat (null): Stopping; failed to start a greeter
[+1365.50s] DEBUG: Seat (null): Stopping
[+1365.50s] DEBUG: Seat (null): Stopping display server
[+1365.50s] DEBUG: Seat (null): Display server stopped
[+1365.50s] DEBUG: Seat (null): Stopped
lightdm.x86_64 1.18.3-5.el7 @epel
CentOS Linux release 7.4.1708 (Core) updates from 9 Nov 2017
HP Proliant DL380G7

Thanks.

Dave

As a little addition I have noted in dmesg output the following:

Code: Select all

[Tue Nov 14 08:46:24 2017] lightdm-gtk-gre[3726]: segfault at 0 ip 00007f9b1fdfa01f sp 00007ffdf24bf5c8 error 4 in libc-2.17.so[7f9b1fd6a000+1b8000]
that I presume matches the G_IS_OBJECT failure in lightdm.log, so I suspect this just will not work until some links are put right.

Post Reply