Arch Linux

verndog

Member

Registered: 2007-09-21

Posts: 55

lightdm.log "CRITICAL"

After examining lightdm.log, I found a CRITICAL error. google reveal nothing relating to lightdm.
Twice: "g_object_unref: assertion 'G_IS_OBJECT (object)' failed "

[+0.01s] DEBUG: Logging to /var/log/lightdm/lightdm.log
[+0.01s] DEBUG: Starting Light Display Manager 1.24.0, UID=0 PID=286
[+0.01s] DEBUG: Loading configuration dirs from /usr/share/lightdm/lightdm.conf.d
[+0.01s] DEBUG: Loading configuration dirs from /usr/local/share/lightdm/lightdm.conf.d
[+0.01s] DEBUG: Loading configuration dirs from /etc/xdg/lightdm/lightdm.conf.d
[+0.01s] DEBUG: Loading configuration from /etc/lightdm/lightdm.conf
[+0.01s] DEBUG: Registered seat module local
[+0.01s] DEBUG: Registered seat module xremote
[+0.01s] DEBUG: Registered seat module unity
[+0.01s] DEBUG: Using D-Bus name org.freedesktop.DisplayManager
[+0.03s] DEBUG: Monitoring logind for seats
[+0.03s] DEBUG: New seat added from logind: seat0
[+0.03s] DEBUG: Seat seat0: Loading properties from config section Seat:*
[+0.03s] DEBUG: Seat seat0: Starting
[+0.03s] DEBUG: Seat seat0: Creating user session
[+0.03s] WARNING: Error getting user list from org.freedesktop.Accounts: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.Accounts was not provided by any .service files
[+0.03s] DEBUG: Loading user config from /etc/lightdm/users.conf
[+0.09s] DEBUG: User me added
[+0.16s] DEBUG: Seat seat0: Creating display server of type x
[+0.17s] DEBUG: Could not run plymouth --ping: Failed to execute child process “plymouth” (No such file or directory)
[+0.17s] DEBUG: Using VT 7
[+0.17s] DEBUG: Seat seat0: Starting local X display on VT 7
[+0.17s] DEBUG: XServer 0: Logging to /var/log/lightdm/x-0.log
[+0.17s] DEBUG: XServer 0: Writing X server authority to /run/lightdm/root/:0
[+0.17s] DEBUG: XServer 0: Launching X Server
[+0.18s] DEBUG: Launching process 294: /usr/sbin/X :0 -seat seat0 -auth /run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
[+0.18s] DEBUG: XServer 0: Waiting for ready signal from X server :0
[+0.18s] DEBUG: Acquired bus name org.freedesktop.DisplayManager
[+0.18s] DEBUG: Registering seat with bus path /org/freedesktop/DisplayManager/Seat0
[+2.79s] DEBUG: Got signal 10 from process 294
[+2.79s] DEBUG: XServer 0: Got signal from X server :0
[+2.79s] DEBUG: XServer 0: Connecting to XServer :0
[+2.80s] CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed     <<=========!
[+2.80s] DEBUG: Seat seat0: Display server ready, starting session authentication
[+2.80s] DEBUG: Session pid=348: Started with service 'lightdm-autologin', username 'me'
[+2.95s] DEBUG: Session pid=348: Authentication complete with return value 0: Success
[+2.95s] DEBUG: Seat seat0: Session authenticated, running command
[+2.95s] DEBUG: Registering session with bus path /org/freedesktop/DisplayManager/Session0
[+2.95s] CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed    <<=========!
[+2.95s] DEBUG: Session pid=348: Running command /etc/lightdm/Xsession startxfce4
[+2.95s] DEBUG: Creating shared data directory /var/lib/lightdm-data/me
[+2.95s] DEBUG: Session pid=348: Logging to .xsession-errors
[+3.39s] DEBUG: Activating VT 7
[+3.39s] DEBUG: Activating login1 session c1
[+3.39s] DEBUG: Seat seat0 changes active session to c1
[+3.39s] DEBUG: Session c1 is already active

Last edited by verndog (2017-12-06 00:24:05)

cfr

Member

From: Cymru

Registered: 2011-11-27

Posts: 7,198

Re: lightdm.log "CRITICAL"

Does it cause you any problems?

---

CLI Paste | How To Ask Questions

Arch Linux | x86_64 | GPT | EFI boot | refind | stub loader | systemd | LVM2 on LUKS
Lenovo x270 | Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz | Intel Wireless 8265/8275 | US keyboard w/ Euro | 512G NVMe INTEL SSDPEKKF512G7L

verndog

Member

Registered: 2007-09-21

Posts: 55

Re: lightdm.log "CRITICAL"

No. I just noticed it while creating auto-login. Thought that might be the issue. Removed auto-login. Same result. All the same, critical, should be investigated.

justasug

Member

Registered: 2014-08-03

Posts: 174

Re: lightdm.log "CRITICAL"

I just checked mine and I have the same messages. Try bringing it up on the LightDM bugtracker upstream, you will get information easier on there.

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 25,435

Re: lightdm.log "CRITICAL"

From a quick googler, this is GTK/GLIBs equivalent of

QXcbConnection: XCB error: 2 (BadValue), sequence: 37140, resource id: 79692329, major code: 142 (Unknown), minor code: 3

read: This is an error thrown when a window is closed and that window is still being referenced somewhere due to Xorgs async nature. Meaning: This is completely harmless and if there are only 2 lines of it likely completely normal.

verndog

Member

Registered: 2007-09-21

Posts: 55

Re: lightdm.log "CRITICAL"

I just checked mine and I have the same messages. Try bringing it up on the LightDM bugtracker upstream, you will get information easier on there.

Thanks for checking. Glad to know its not just my system. I'll check that bugtracker you suggested. Most likely harmless as V1del stated.