Hi all,
After running the latest updates, I have something of an issue with logging into KDE - I don’t think this is the same issue as the other thread currently floating about, but will to admit I’m wrong on this.
So, attempt to log in → black screen → back to SDDM login prompt.
The reason is that it looks like systemd is having a bad day - journalctl shows this :
Oct 13 16:46:36 <host> systemd[1]: Started Process Core Dump (PID 52183/UID 0).
Oct 13 16:46:36 <host> systemd[1]: Started Pass systemd-coredump journal entries to relevant user for potential DrKonqi handling.
Oct 13 16:46:36 <host> systemd-coredump[52188]: [🡕] Process 52174 (baloo_file_extr) of user 1000 dumped core.
Stack trace of thread 52174:
#0 0x00007f53f52a53f4 n/a (libc.so.6 + 0x963f4)
#1 0x00007f53f524c120 raise (libc.so.6 + 0x3d120)
#2 0x00007f53f52334c3 abort (libc.so.6 + 0x244c3)
#3 0x00007f53f4c8c663 n/a (libQt6Core.so.6 + 0x8c663)
#4 0x00007f53f4c8ce07 _ZNK14QMessageLogger5fatalEPKcz (libQt6Core.so.6 + 0x8ce07)
#5 0x00007f53f54daa65 n/a (libQt6Gui.so.6 + 0xdaa65)
#6 0x00007f53f557c3a8 _ZN22QGuiApplicationPrivate21createEventDispatcherEv (libQt6Gui.so.6 + 0x17c3a8)
#7 0x00007f53f4d49a2d _ZN23QCoreApplicationPrivate4initEv (libQt6Core.so.6 + 0x149a2d)
#8 0x00007f53f557c43e _ZN22QGuiApplicationPrivate4initEv (libQt6Gui.so.6 + 0x17c43e)
#9 0x00007f53f5574fad _ZN15QGuiApplicationC2ERiPPci (libQt6Gui.so.6 + 0x174fad)
#10 0x0000607b167d3247 n/a (baloo_file_extractor + 0x8247)
#11 0x00007f53f5234e08 n/a (libc.so.6 + 0x25e08)
#12 0x00007f53f5234ecc __libc_start_main (libc.so.6 + 0x25ecc)
#13 0x0000607b167d3595 n/a (baloo_file_extractor + 0x8595)
Stack trace of thread 52182:
#0 0x00007f53f531a63d __poll (libc.so.6 + 0x10b63d)
#1 0x00007f53f451de0d n/a (libglib-2.0.so.0 + 0xbfe0d)
#2 0x00007f53f44ba795 g_main_context_iteration (libglib-2.0.so.0 + 0x5c795)
#3 0x00007f53f4fa82bd _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt6Core.so.6 + 0x3a82bd)
#4 0x00007f53f4d4ff66 _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt6Core.so.6 + 0x14ff66)
#5 0x00007f53f4e3d650 _ZN7QThread4execEv (libQt6Core.so.6 + 0x23d650)
#6 0x00007f53f5cc0f0e n/a (libQt6DBus.so.6 + 0x2df0e)
#7 0x00007f53f4ecd237 n/a (libQt6Core.so.6 + 0x2cd237)
#8 0x00007f53f52a339d n/a (libc.so.6 + 0x9439d)
#9 0x00007f53f532849c n/a (libc.so.6 + 0x11949c)
ELF object binary architecture: AMD x86-64
Oct 13 16:46:36 <host> systemd[1]: systemd-coredump@2321-52183-0.service: Deactivated successfully.
Oct 13 16:46:36 <host> baloo_file[2924]: kf.baloo: Extractor crashed
Oct 13 16:46:36 <host> baloo_file_extractor[52195]: Failed to create wl_display (No such file or directory)
Oct 13 16:46:36 <host> baloo_file_extractor[52195]: qt.qpa.plugin: Could not load the Qt platform plugin "wayland" in "" even though it was found.
Oct 13 16:46:36 <host> baloo_file_extractor[52195]: qt.qpa.xcb: could not connect to display :1
Oct 13 16:46:36 <host> baloo_file_extractor[52195]: qt.qpa.plugin: From 6.5.0, xcb-cursor0 or libxcb-cursor0 is needed to load the Qt xcb platform plugin.
Oct 13 16:46:36 <host> baloo_file_extractor[52195]: qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
Oct 13 16:46:36 <host> baloo_file_extractor[52195]: This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.
Available platform plugins are: vkkhrdisplay, xcb, wayland, wayland-egl, eglfs, minimal, linuxfb, offscreen, vnc, minimalegl.
Oct 13 16:46:36 <host> systemd-coredump[52200]: Process 52195 (baloo_file_extr) of user 1000 terminated abnormally with signal 6/ABRT, processing...
Oct 13 16:46:36 <host> systemd[1]: Started Process Core Dump (PID 52200/UID 0).
Oct 13 16:46:36 <host> systemd[1]: Started Pass systemd-coredump journal entries to relevant user for potential DrKonqi handling.
Oct 13 16:46:36 <host> drkonqi-coredump-processor[52189]: "/usr/lib/kf6/baloo_file_extractor" 52174 "/var/lib/systemd/coredump/core.baloo_file_extr.1000.aeb306d182b24fb4bb74251b558e0d9f.52174.1728834396000000.zst"
Oct 13 16:46:36 <host> drkonqi-coredump-processor[52170]: "/usr/lib/kf6/baloo_file_extractor" 52161 "/var/lib/systemd/coredump/core.baloo_file_extr.1000.aeb306d182b24fb4bb74251b558e0d9f.52161.1728834396000000.zst"
Oct 13 16:46:36 <host> systemd[1]: drkonqi-coredump-processor@2320-52166-0.service: Deactivated successfully.
Oct 13 16:46:36 <host> systemd[2526]: Started Launch DrKonqi for a systemd-coredump crash (PID 52189/UID 0).
Oct 13 16:46:36 <host> systemd[1]: drkonqi-coredump-processor@2321-52183-0.service: Deactivated successfully.
Oct 13 16:46:36 <host> systemd[2526]: Started Launch DrKonqi for a systemd-coredump crash (PID 52170/UID 0).
Oct 13 16:46:36 <host> drkonqi-coredump-launcher[52206]: Unable to find file for pid 52174 expected at "kcrash-metadata/baloo_file_extractor.aeb306d182b24fb4bb74251b558e0d9f.52174.ini"
Oct 13 16:46:36 <host> drkonqi-coredump-launcher[52206]: Nothing handled the dump :O
Oct 13 16:46:36 <host> drkonqi-coredump-launcher[52209]: Unable to find file for pid 52161 expected at "kcrash-metadata/baloo_file_extractor.aeb306d182b24fb4bb74251b558e0d9f.52161.ini"
Oct 13 16:46:36 <host> drkonqi-coredump-launcher[52209]: Nothing handled the dump :O
Using balooctl I have disabled baloo, and purged it a swell, but it looks as if this is pointless as systemd attempts to load it anyway, resulting in this crash. Tried reinstalling baloo and xcb-utils, no avail.
Anyone got any clues?