You are not logged in.
baloo_file_extr process is crashing several times every second on my machine. My current workaround is to pause the indexer in Settings.
Crash log:
PID: 30358 (baloo_file_extr)
TID: 30358 (baloo_file_extr)
UID: 1000 (ljmcc)
GID: 1000 (ljmcc)
Signal: 6 (ABRT) si_code: SI_TKILL
Timestamp: Thu 2026-10-15 22:21:59 BST (1s ago)
Command Line: /usr/lib/kf6/baloo_file_extractor
Executable: /usr/lib/kf6/baloo_file_extractor
Control Group: /user.slice/user-1000.slice/user@1000.service/background.slice/kde-baloo.service
Unit: user@1000.service
User Unit: kde-baloo.service
Slice: user-1000.slice
Owner UID: 1000 (ljmcc)
Boot ID: 6ae1ab781de14a7c814ba82569fc7e0a
Machine ID: 60a1dae040234189a529ecc0c8c25596
Hostname: archimedes
Storage: /var/lib/systemd/coredump/core.baloo_file_extr.1000.6ae1ab781de14a7c814ba82569fc7e0a.30358.1792099319000000.zst (present)
Size on Disk: 716.9K
Message: Process 30358 (baloo_file_extr) of user 1000 dumped core.
Stack trace of thread 30358:
#0 0x00007f77d029a11c n/a (libc.so.6 + 0x9a11c)
#1 0x00007f77d023e5d0 raise (libc.so.6 + 0x3e5d0)
#2 0x00007f77d0225685 abort (libc.so.6 + 0x25685)
#3 0x00007f77d0a99bfe n/a (libQt6Core.so.6 + 0x99bfe)
#4 0x00007f77d0a9a369 _ZNK14QMessageLogger5fatalEPKcz (libQt6Core.so.6 + 0x9a369)
#5 0x00007f77d13b228b _ZN22QGuiApplicationPrivate25createPlatformIntegrationEv (libQt6Gui.so.6 + 0x1b228b)
#6 0x00007f77d13b38c8 _ZN22QGuiApplicationPrivate21createEventDispatcherEv (libQt6Gui.so.6 + 0x1b38c8)
#7 0x00007f77d0b8ee15 _ZN23QCoreApplicationPrivate4initEv (libQt6Core.so.6 + 0x18ee15)
#8 0x00007f77d13b39cb _ZN22QGuiApplicationPrivate4initEv (libQt6Gui.so.6 + 0x1b39cb)
#9 0x00007f77d13a92ae _ZN15QGuiApplicationC2ERiPPci (libQt6Gui.so.6 + 0x1a92ae)
#10 0x000055e18c504388 n/a (baloo_file_extractor + 0x8388)
#11 0x00007f77d0227781 n/a (libc.so.6 + 0x27781)
#12 0x00007f77d02278b9 __libc_start_main (libc.so.6 + 0x278b9)
#13 0x000055e18c504625 n/a (baloo_file_extractor + 0x8625)
Stack trace of thread 30362:
#0 0x00007f77d02a08f2 n/a (libc.so.6 + 0xa08f2)
#1 0x00007f77d0311ac2 read (libc.so.6 + 0x111ac2)
#2 0x00007f77d0004551 n/a (libglib-2.0.so.0 + 0xbb551)
#3 0x00007f77cffae43e n/a (libglib-2.0.so.0 + 0x6543e)
#4 0x00007f77cffb3ae3 n/a (libglib-2.0.so.0 + 0x6aae3)
#5 0x00007f77cffb3db5 g_main_context_iteration (libglib-2.0.so.0 + 0x6adb5)
#6 0x00007f77d0ec4d22 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt6Core.so.6 + 0x4c4d22)
#7 0x00007f77d0b96a74 _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt6Core.so.6 + 0x196a74)
#8 0x00007f77d0cc4a02 _ZN7QThread4execEv (libQt6Core.so.6 + 0x2c4a02)
#9 0x00007f77d0969781 n/a (libQt6DBus.so.6 + 0x38781)
#10 0x00007f77d0d78fdb n/a (libQt6Core.so.6 + 0x378fdb)
#11 0x00007f77d0298042 n/a (libc.so.6 + 0x98042)
#12 0x00007f77d032072c n/a (libc.so.6 + 0x12072c)
ELF object binary architecture: AMD x86-64
-- Notice: 1 systemd-coredump@.service unit is running, output may be incomplete.Offline
Installed package for baloo is 6.31.0-1
Offline
https://wiki.archlinux.org/title/Debuginfod
Also
Signal: 6 (ABRT) si_code: SI_TKILLAny abort messages in the journal?
#5 0x00007f77d13b228b _ZN22QGuiApplicationPrivate25createPlatformIntegrationEv (libQt6Gui.so.6 + 0x1b228b)Are you by any chance exporting QT_QPA_PLATFORM?
printenvOffline
Oct 15 22:51:12 archimedes baloo_file[1347]: Extractor crashed
Oct 15 22:51:12 archimedes baloo_file_extractor[45206]: Failed to create wl_display (No such file or directory)
Oct 15 22:51:12 archimedes baloo_file_extractor[45206]: Could not load the Qt platform plugin "wayland" in "" even though it was found.
Oct 15 22:51:12 archimedes baloo_file_extractor[45206]: could not connect to display
Oct 15 22:51:12 archimedes baloo_file_extractor[45206]: From 6.5.0, xcb-cursor0 or libxcb-cursor0 is needed to load the Qt xcb platform plugin.
Oct 15 22:51:12 archimedes baloo_file_extractor[45206]: Could not load the Qt platform plugin "xcb" in "" even though it was found.
Oct 15 22:51:12 archimedes baloo_file_extractor[45206]: This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.
Available platform plugins are: minimal, vkkhrdisplay, wayland-brcm, wayland-egl, wayland, offscreen, linuxfb, vnc, minimalegl, xcb, eglfs.
Oct 15 22:51:12 archimedes systemd-coredump[45212]: [?] Process 45206 (baloo_file_extr) of user 1000 dumped core.I checked my environment, I don't appear to be setting QT_QPA_PLATFORM.
Offline
printenv | grep -iE 'display|xdg'plasma ditched X11 support, if you're trying to run baloo on a different kind of (X11) session that might be a problem.
Offline
XDG_RUNTIME_DIR=/run/user/1000
XDG_SESSION_CLASS=user
XDG_DATA_DIRS=/home/ljmcc/.local/share/flatpak/exports/share:/var/lib/flatpak/exports/share:/usr/local/share:/usr/share
XDG_SEAT=seat0
WAYLAND_DISPLAY=wayland-1
XDG_CURRENT_DESKTOP=KDE
XDG_SEAT_PATH=/org/freedesktop/DisplayManager/Seat0
XDG_SESSION_DESKTOP=KDE
XDG_VTNR=2
DISPLAY=:0
XDG_SESSION_PATH=/org/freedesktop/DisplayManager/Session1
XDG_CONFIG_DIRS=/home/ljmcc/.config/kdedefaults:/etc/xdg
XDG_SESSION_ID=2
XDG_MENU_PREFIX=plasma-
XDG_SESSION_TYPE=waylandOffline
It's this bug: https://bugs.kde.org/show_bug.cgi?id=524392
Current temporary workaround is to do a `systemctl --user restart kde-baloo.service` to stop the crashes. Seems to be due to the fact that the baloo process is missing DISPLAY and WAYLAND_DISPLAY.
There is a merge request to delay the start of kde-baloo until those env vars become available, but currently it is causing a systemd cycle ordering issue and preventing baloo from starting up: https://invent.kde.org/frameworks/baloo … quests/331
Offline
systemctl --user stop kde-baloo.service
systemctl --user edit kde-baloo.servicethen enter:
[Unit]
After=plasma-kwin_wayland.servicesave, close the editor, then restart.
Last edited by genericity (2026-10-16 08:57:53)
Offline
systemctl --user stop kde-baloo.service systemctl --user edit kde-baloo.servicethen enter:
[Unit] After=plasma-kwin_wayland.servicesave, close the editor, then restart.
This worked for me.
Offline
I note that for baloo version that the file after the update contains:
After=plasma-workspace.targetWhich is different to the change suggested above, and does not fix the logout delay for me. Is there an upstream change that might bring in the correct change fx the issue in the next version?
Mike C
Offline
The logout delay? I think that's a separate issue related to plasmashell not properly quitting on sigterm.
Offline
Yes you are right - https://bugs.kde.org/show_bug.cgi?id=527208 is the delay bug upstream
Mike C
Offline
I note that for baloo version that the file after the update contains:
After=plasma-workspace.targetWhich is different to the change suggested above, and does not fix the logout delay for me. Is there an upstream change that might bring in the correct change fx the issue in the next version?
The above delays starting baloo_file further in the session startup. Both approach works, as long as kde-baloo.service is launched after plasma-kwin_wayland.service is running (thus $WAYLAND_DISPLAY and $DISPLAY is set).
The logout problem can probably be worked around by removing the pager widget. (3rd-party pager widgets seem to not trigger the bug.) The fix is in Qt 6.12.1.
Offline
The relevant fix should be backported in the new baloo 6.31.0-2 package
Offline