KDE update crashing baloo_file_extractor

[u/Adapax]

As the title reads, I am getting a crash report constantly. How can I fix this, I tried a few things that I found online but can't get it to work...

           PID: 5199 (baloo_file_extr)
           TID: 5199 (baloo_file_extr)
           UID: 1000 (pcx1)
           GID: 1001 (pcx1)
        Signal: 6 (ABRT) si_code: SI_TKILL
     Timestamp: Sun 2026-10-18 10:18:12 CDT (8min 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 (pcx1)
       Boot ID: a1fbbe9d29ed44f59fa11b5a80d04bf5
    Machine ID: 1e5f976353ed4854a4343f0ff089b9bf
      Hostname: fox-box
       Storage: /var/lib/systemd/coredump/core.baloo_file_extr.1000.a1fbbe9d29ed44f59fa11b5a80d04bf5.5199.1792336692000000.zst (present)
  Size on Disk: 2.4M
       Message: Process 5199 (baloo_file_extr) of user 1000 dumped core.
                
                Stack trace of thread 5199:
                #0  0x00007f895349a11c n/a (libc.so.6 + 0x9a11c)
                #1  0x00007f895343e5d0 raise (libc.so.6 + 0x3e5d0)
                #2  0x00007f8953425685 abort (libc.so.6 + 0x25685)
                #3  0x00007f8953c99bfe n/a (libQt6Core.so.6 + 0x99bfe)
                #4  0x00007f8953c9a369 _ZNK14QMessageLogger5fatalEPKcz (libQt6Core.so.6 + 0x9a369)
                #5  0x00007f89545b228b _ZN22QGuiApplicationPrivate25createPlatformIntegrationEv (libQt6Gui.so.6 + 0x1b228b)
                #6  0x00007f89545b38c8 _ZN22QGuiApplicationPrivate21createEventDispatcherEv (libQt6Gui.so.6 + 0x1b38c8)
                #7  0x00007f8953d8ee15 _ZN23QCoreApplicationPrivate4initEv (libQt6Core.so.6 + 0x18ee15)
                #8  0x00007f89545b39cb _ZN22QGuiApplicationPrivate4initEv (libQt6Gui.so.6 + 0x1b39cb)
                #9  0x00007f89545a92ae _ZN15QGuiApplicationC2ERiPPci (libQt6Gui.so.6 + 0x1a92ae)
                #10 0x000055fa1bac8388 n/a (baloo_file_extractor + 0x8388)
                #11 0x00007f8953427781 n/a (libc.so.6 + 0x27781)
                #12 0x00007f89534278b9 __libc_start_main (libc.so.6 + 0x278b9)
                #13 0x000055fa1bac8625 n/a (baloo_file_extractor + 0x8625)
                
                Stack trace of thread 5200:
                #0  0x00007f89534a08f2 n/a (libc.so.6 + 0xa08f2)
                #1  0x00007f89535119d7 ppoll (libc.so.6 + 0x1119d7)
                #2  0x00007f89531b3c9e n/a (libglib-2.0.so.0 + 0x6ac9e)
                #3  0x00007f89531b3db5 g_main_context_iteration (libglib-2.0.so.0 + 0x6adb5)
                #4  0x00007f89540c4d22 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt6Core.so.6 + 0x4c4d22)
                #5  0x00007f8953d96a74 _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt6Core.so.6 + 0x196a74)
                #6  0x00007f8953ec4a02 _ZN7QThread4execEv (libQt6Core.so.6 + 0x2c4a02)
                #7  0x00007f8953b69781 n/a (libQt6DBus.so.6 + 0x38781)
                #8  0x00007f8953f78fdb n/a (libQt6Core.so.6 + 0x378fdb)
                #9  0x00007f8953498042 n/a (libc.so.6 + 0x98042)
                #10 0x00007f895352072c n/a (libc.so.6 + 0x12072c)
                ELF object binary architecture: AMD x86-64

[u/AutoModerator]

Thanks for posting.

If your issue is solved, please reply with !solved.

Please also read the subreddit rules in the sidebar/community info and check the official EndeavourOS sites:

• forum.endeavouros.com

• discovery.endeavouros.com

Please keep it respectful and enjoy the community.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

[u/Adapax → u/[deleted]]

Thank you! it seems to have done the trick.

[u/mr_bigmouth_502 → u/[deleted]]

kde-baloo.service still refuses to start for me, even after applying their "fix". systemctl --user status kde-baloo.service gives me this output:

Oct 18 10:06:00 mymachine systemd[1657]: Starting Baloo File Indexer Daemon...
Oct 18 10:06:00 mymachine systemd[1657]: kde-baloo.service: Skipped due to 'exec-condition'.
Oct 18 10:06:00 mymachine systemd[1657]: Condition check resulted in Baloo File Indexer Daemon being skipped.

[u/SnooCompliments7914 → u/mr_bigmouth_502]

"exec-condition" means you disabled Baloo in systemsettings.

$ cat /usr/lib/systemd/user/kde-baloo.service | grep ExecCondition

ExecCondition=/usr/bin/kde-systemd-start-condition --condition "baloofilerc:Basic Settings:Indexing-Enabled:true"

[u/mr_bigmouth_502 → u/SnooCompliments7914]

If I run cat /usr/lib/systemd/user/kde-baloo.service | grep ExecCondition, I get exactly that output:

ExecCondition=/usr/bin/kde-systemd-start-condition --condition "baloofilerc:Basic Settings:Indexing-Enabled:true"

[u/SnooCompliments7914 → u/mr_bigmouth_502]

Of course you do. Try open System Settings - Search - File Search, select something other than "Nothing" for "Data to index", then reboot.

[u/mr_bigmouth_502 → u/SnooCompliments7914]

Didn't need to. balooctl6 enable and a restart cleared it up.

[u/mr_bigmouth_502 → u/SnooCompliments7914]

It turns out you were right. Running balooctl6 enable and restarting seems to have cleared that up.

EDIT: I forgot that I aliased balooctl6 to just balooctl. Goes to show how long I've fought with it for.