You are not logged in.

#1 2025-10-21 11:55:53

jfk
Member
Registered: 2017-12-11
Posts: 130

[SOLVED] Coredump libglib 2.0 at boot

Last -Syu broke my booting process. Chrooting tells me something's wrong with gnome and libglib 2.0:

Oct 21 13:17:51 xps13-fpierreh systemd-coredump[2193]: Process 2178 (gnome-session-i) of user 1000 dumped core.
                                                       
                                                       Stack trace of thread 2178:
                                                       #0  0x000075221f2b9b8c g_log_structured_array (libglib-2.0.so.0 + 0x64b8c)
                                                       #1  0x000075221f2ba2e0 g_log_default_handler (libglib-2.0.so.0 + 0x652e0)
                                                       #2  0x000075221f2ba57a g_logv (libglib-2.0.so.0 + 0x6557a)
                                                       #3  0x000075221f2ba904 g_log (libglib-2.0.so.0 + 0x65904)
                                                       #4  0x000062154d5e9686 n/a (/usr/lib/gnome-session-init-worker + 0x2686)
                                                       #5  0x000075221f027675 n/a (libc.so.6 + 0x27675)
                                                       #6  0x000075221f027729 __libc_start_main (libc.so.6 + 0x27729)
                                                       #7  0x000062154d5e9c95 n/a (/usr/lib/gnome-session-init-worker + 0x2c95)
                                                       
                                                       Stack trace of thread 2189:
                                                       #0  0x000075221f11876d syscall (libc.so.6 + 0x11876d)
                                                       #1  0x000075221f2e47ee g_cond_wait (libglib-2.0.so.0 + 0x8f7ee)
                                                       #2  0x000075221f27b1cd n/a (libglib-2.0.so.0 + 0x261cd)
                                                       #3  0x000075221f2ed447 n/a (libglib-2.0.so.0 + 0x98447)
                                                       #4  0x000075221f2ec87c n/a (libglib-2.0.so.0 + 0x9787c)
                                                       #5  0x000075221f0969cb n/a (libc.so.6 + 0x969cb)
                                                       #6  0x000075221f11aa0c n/a (libc.so.6 + 0x11aa0c)
                                                       
                                                       Stack trace of thread 2190:
                                                       #0  0x000075221f09f042 n/a (libc.so.6 + 0x9f042)
                                                       #1  0x000075221f0931ac n/a (libc.so.6 + 0x931ac)
                                                       #2  0x000075221f0931f4 n/a (libc.so.6 + 0x931f4)
                                                       #3  0x000075221f10da36 ppoll (libc.so.6 + 0x10da36)
                                                       #4  0x000075221f2b5744 n/a (libglib-2.0.so.0 + 0x60744)
                                                       #5  0x000075221f2b5825 g_main_context_iteration (libglib-2.0.so.0 + 0x60825)
                                                       #6  0x000075221f2b5872 n/a (libglib-2.0.so.0 + 0x60872)
                                                       #7  0x000075221f2ec87c n/a (libglib-2.0.so.0 + 0x9787c)
                                                       #8  0x000075221f0969cb n/a (libc.so.6 + 0x969cb)
                                                       #9  0x000075221f11aa0c n/a (libc.so.6 + 0x11aa0c)
                                                       
                                                       Stack trace of thread 2191:
                                                       #0  0x000075221f09f042 n/a (libc.so.6 + 0x9f042)
                                                       #1  0x000075221f0931ac n/a (libc.so.6 + 0x931ac)
                                                       #2  0x000075221f0931f4 n/a (libc.so.6 + 0x931f4)
                                                       #3  0x000075221f10da36 ppoll (libc.so.6 + 0x10da36)
                                                       #4  0x000075221f2b5744 n/a (libglib-2.0.so.0 + 0x60744)
                                                       #5  0x000075221f2b59d7 g_main_loop_run (libglib-2.0.so.0 + 0x609d7)
                                                       #6  0x000075221f526264 n/a (libgio-2.0.so.0 + 0x11a264)
                                                       #7  0x000075221f2ec87c n/a (libglib-2.0.so.0 + 0x9787c)
                                                       #8  0x000075221f0969cb n/a (libc.so.6 + 0x969cb)
                                                       #9  0x000075221f11aa0c n/a (libc.so.6 + 0x11aa0c)
                                                       ELF object binary architecture: AMD x86-64
Oct 21 13:17:51 xps13-fpierreh systemd[1]: Failed to start Getty on tty1.
Oct 21 13:18:22 xps13-fpierreh dbus-broker-launch[787]: Activation request for 'org.freedesktop.nm_dispatcher' failed.
Oct 21 13:18:22 xps13-fpierreh dbus-broker-launch[787]: Activation request for 'org.freedesktop.nm_dispatcher' failed.
Oct 21 13:18:22 xps13-fpierreh dbus-broker-launch[787]: Activation request for 'org.freedesktop.nm_dispatcher' failed.

Last edited by jfk (2025-10-22 12:58:39)

Offline

#2 2025-10-21 12:15:37

seth
Member
From: Don't DM me only for attention
Registered: 2012-09-03
Posts: 70,052

Re: [SOLVED] Coredump libglib 2.0 at boot

1. Don't post pictures of text, post the text
2. get a swiffer?
3. the important bits are missing, please post your complete system journal for the boot:

sudo journalctl -b | curl -F 'file=@-' 0x0.st

But it kinda looks like youlikely do https://wiki.archlinux.org/title/GDM#Use_Xorg_backend - which doesn't work w/ gnome 49 (and yes, gnome shell "should" be aware of that and not crash and it most certainly "should" not try to fall back to X11 when wayland doesn't wok…
4. alternatively you might hit https://bbs.archlinux.org/viewtopic.php … 5#p2263495 (and GDM trying to fall back to X11)

Edit: fuck. I mean "five": please also don#t embed oversized images, the board has a 250x250 max rule to prevent threads from turning into scroll-fests.

Last edited by seth (2025-10-21 12:16:54)

Offline

#3 2025-10-21 13:35:25

jfk
Member
Registered: 2017-12-11
Posts: 130

Re: [SOLVED] Coredump libglib 2.0 at boot

journalctl -b

has no entries.

journalctl -p err | curl -F 'file=@-' 0x0.st

journalctl -b -1 | curl -F 'file=@-' 0x0.st


/etc/gdm/custom.conf

has

#WaylandEnable=false

Uncommentting does not seem to affect the outcome.

/etc/nsswitch.conf

  is properly set (shadow: files systemd).

Last edited by jfk (2025-10-21 13:36:00)

Offline

#4 2025-10-21 13:40:07

seth
Member
From: Don't DM me only for attention
Registered: 2012-09-03
Posts: 70,052

Re: [SOLVED] Coredump libglib 2.0 at boot

https://0x0.st/KjCD.txt ends abruptly and before reaching even the multi-user.target.
Don't reboot w/ the power button - you can most likely just switch the VT (ctrl+alt+f3) and login

If "sudo journalctl -b" has "no entries", what produced the backtrace you edited in #1 - OCR??
Edit: resp. how did you even get to see it on the original photo?

Last edited by seth (2025-10-21 13:40:34)

Offline

#5 2025-10-21 14:21:08

jfk
Member
Registered: 2017-12-11
Posts: 130

Re: [SOLVED] Coredump libglib 2.0 at boot

Don't reboot w/ the power button - you can most likely just switch the VT (ctrl+alt+f3) and login

I can't the keyboard is unresponsive after the crash.

If "sudo journalctl -b" has "no entries", what produced the backtrace you edited in #1 - OCR??

journalctl -b -1

But indeed, last boots stopped showing the original coredump. I can't explain it.

Last edited by jfk (2025-10-21 14:23:18)

Offline

#6 2025-10-21 14:25:58

seth
Member
From: Don't DM me only for attention
Registered: 2012-09-03
Posts: 70,052

Re: [SOLVED] Coredump libglib 2.0 at boot

Can you reboot w/ the https://wiki.archlinux.org/title/Keyboa … el_(SysRq) (+REISUB)
Can you boot the multi-user.target (2nd link below)?
Does an older boot like

sudo journalctl -b -3

still have the original coredump?
(The precise boot doesn't matter - just the information about the crash)

Offline

#7 2025-10-21 15:40:07

jfk
Member
Registered: 2017-12-11
Posts: 130

Re: [SOLVED] Coredump libglib 2.0 at boot

I removed my systemd autologin and managed to handle things without chrooting (complete crash was due to repeated autologin attempts I suppose). The requested log from the main user (where you'll see the coredump):

sudo systemctl -b

multi-user.target doesn't solve the issue.

Last edited by jfk (2025-10-21 17:45:37)

Offline

#8 2025-10-21 19:21:30

seth
Member
From: Don't DM me only for attention
Registered: 2012-09-03
Posts: 70,052

Re: [SOLVED] Coredump libglib 2.0 at boot

Ah, you're "manually" autostarting gnome - most likely "wrong" (because the wiki suggestion is long-time contested as "doesn't work at all")
=> https://bbs.archlinux.org/viewtopic.php … 3#p2268463

That aside, disable dhcpd if you're gonna use NM.

Neither will explain your keyboard failure, though.
I'll have a close look at the journal but please check and report whether that problem is gone after fixing gnome.

Edit:

oct 21 17:33:45 xps13-fpierreh (udev-worker)[1727]: 3-1.1:1.2: Process '/opt/displaylink/udev.sh /dev ' failed with exit code 2.
oct 21 17:33:45 xps13-fpierreh colord[1839]: Error my backend :        out of memory

But the keyboard is i8042 - not sure whether the usb udev rule or the OOM colord (both likely caused by the failing gnome session) could impact tha.



oct 21 17:31:13 xps13-fpierreh kernel: spi-nor spi0.0: probe with driver spi-nor failed with error -22

nb. also

oct 21 17:31:14 xps13-fpierreh vpnagentd[926]: /opt/cisco/secureclient/bin/vpnagentd: error while loading shared libraries: libxml2.so.2: cannot open shared object file: No such file or directory
oct 21 17:31:14 xps13-fpierreh systemd[1]: vpnagentd.service: Main process exited, code=exited, status=127/n/a
oct 21 17:31:14 xps13-fpierreh systemd[1]: vpnagentd.service: Failed with result 'exit-code'.

=> https://archlinux.org/packages/extra/x8 … l2-legacy/

oct 21 17:31:15 xps13-fpierreh wpa_supplicant[977]: wlp2s0: CTRL-EVENT-SCAN-FAILED ret=-22
oct 21 17:31:18 xps13-fpierreh wpa_supplicant[977]: wlp2s0: CTRL-EVENT-SCAN-FAILED ret=-22
oct 21 17:31:23 xps13-fpierreh wpa_supplicant[977]: wlp2s0: CTRL-EVENT-SCAN-FAILED ret=-22
oct 21 17:31:30 xps13-fpierreh wpa_supplicant[977]: wlp2s0: CTRL-EVENT-SCAN-FAILED ret=-22
oct 21 17:31:40 xps13-fpierreh wpa_supplicant[977]: wlp2s0: CTRL-EVENT-SCAN-FAILED ret=-22
oct 21 17:31:54 xps13-fpierreh wpa_supplicant[977]: wlp2s0: CTRL-EVENT-SCAN-FAILED ret=-22
oct 21 17:32:14 xps13-fpierreh wpa_supplicant[977]: wlp2s0: CTRL-EVENT-SCAN-FAILED ret=-22
oct 21 17:32:43 xps13-fpierreh wpa_supplicant[977]: wlp2s0: CTRL-EVENT-SCAN-FAILED ret=-22
oct 21 17:33:26 xps13-fpierreh wpa_supplicant[977]: wlp2s0: CTRL-EVENT-SCAN-FAILED ret=-22

That's the broadcom wl driver - is this a regression or has that chip never properly worked?
My first instinct would be to

oct 21 17:31:14 xps13-fpierreh NetworkManager[906]: <info>  [1761060674.9674] device (wlp2s0): set-hw-addr: set MAC address to 52:C6:EB:2B:73:43 (scanning)

disable that, https://wiki.archlinux.org/title/Networ … domization

Last edited by seth (2025-10-21 19:32:13)

Offline

#9 2025-10-21 20:57:47

jfk
Member
Registered: 2017-12-11
Posts: 130

Re: [SOLVED] Coredump libglib 2.0 at boot

Ah, you're "manually" autostarting gnome

No: I autolog with systemd and then autostart X in bashrc and gnome in xinitrc.

I followed your suggestion but to no avail.

I commented the autostart of X. Starting it manually shows the server shutting down immediately with a failure in enabling I/O ports (permission errors).

Last edited by jfk (2025-10-21 21:04:45)

Offline

#10 2025-10-21 21:12:57

seth
Member
From: Don't DM me only for attention
Registered: 2012-09-03
Posts: 70,052

Re: [SOLVED] Coredump libglib 2.0 at boot

That will under no circumstances work because gnome v49 no longer supports X11.

If you want to start gnome (on wayland) w/o a DM see the approach in the other thread.

Offline

#11 2025-10-22 12:58:13

jfk
Member
Registered: 2017-12-11
Posts: 130

Re: [SOLVED] Coredump libglib 2.0 at boot

Thank you I totally missed that.

My solution: I kept autologin through systemd, enabled GDM and set autologin to True in GDM conf.

Regarding the wpa_supplicant error, I ordered a new network card to bypass Broadcom proprietary drivers which are probably the reason of those failures. I indeed can't get wifi networks anymore.

Last edited by jfk (2025-10-22 12:59:46)

Offline

Board footer

Powered by FluxBB