Baloo File Extractor Constantly Crashes

Hello there!

Since approximately last week, I’ve been encountering an issue when booting up my KDE Neon install where my taskbar will get spammed with “Baloo File Extractor has crashed” notifications, as seen in the attached image.

Based on previous reporting of similar issues in other Linux distros, I attempted the following commands:
balooctl6 disable && balooctl6 purge && balooctl6 enable

The first two executed as expected - the third resulted in some odd behaviour which I’m not able to figure out.

First, it gives me:

KCrash: Application 'baloo_file_extractor' crashing... crashRecursionCounter = 2  
kf.baloo: Extractor crashed  
kf.idletime: Could not find any system poller plugin  
qt.core.qobject.connect: QObject::connect(KAbstractIdleTimePoller, KIdleTime): invalid nullptr parameter  
qt.core.qobject.connect: QObject::connect(KAbstractIdleTimePoller, KIdleTime): invalid nullptr parameter  
qt.core.qobject.connect: QObject::connect: No such signal Solid::Backends::Fstab::FstabStorageAccess::repairRequested(QString) in ./src/solid/devices/frontend/storageaccess.cpp:23  
qt.core.qobject.connect: QObject::connect: No such signal Solid::Backends::Fstab::FstabStorageAccess::repairDone(Solid::ErrorType, QVariant, QString) in ./src/solid/devices/frontend/storageaccess.cpp:24

This is followed by twenty or thirty (inconsistent) repetitions of:
QFont::setPixelSize: Pixel size <= 0 (-1),
and then that first code block a few times in a row.

It alternates between these two for while, and then gives me a new error:

kf.filemetadata: Could not create Extractor: "/usr/lib/x86_64-linux-gnu/qt6/plugins/kf6/kfilemetadata/kfilemetadata_appimageextractor.so"
kf.filemetadata: "Cannot load library /usr/lib/x86_64-linux-gnu/qt6/plugins/kf6/kfilemetadata/kfilemetadata_appimageextractor.so: /lib/x86_64-linux-gnu/libappimage.so.1.0: undefined symbol: _ZNKSt7__cxx1115basic_stringbufIcSt11char_traitsIcESaIcEE12_M_high_markEv"
qt.gui.imageio: libpng warning: iCCP: known incorrect sRGB profile
"Error: Invalid least number of objects reading page offset hints table"

Now, while all this is going on, I’ve been watching balooctl6 monitor in a separate tab, and it seems like everything is fine from that end - it is processing files, those files are returning Ok, it’s running - but it’s still spamming out my taskbar.

The easy answer would be to just disable the notifications for crashing, since it seems like it’s still operating despite crashing, but I’d like to figure out why exactly it’s giving these errors, in case it’s a sign of some other bad stuff going on.

Thanks in advance for any help, and please let me know if there’s any other information I can provide!

There was a cleanup change Merge request 192 that was a bit enthusiastic.

The discovery is here Bug 487628 and “moment of realisation”, here Note 959092.

It ha just been reverted in Merge Request 200. You don’t say what disto you are using, it sounds like a bit cutting edge :slight_smile:

As per my original post, I am using KDE Neon, and for more context I am using the Stable Edition.

Thanks for the links, that does explain this whole thing!

… for more context I am using the Stable Edition …

Looks like we didn’t catch the bug quickly enough then!

Hello,

I’m having the same issue, I’m using the KDE Neon User Edition latest updates.

It happened few days ago but after a reboot it was fine but now it just doesn’t stop. I disabled it for now.

I’m having the same issue, I’m using the KDE Neon User Edition latest updates.

I am doubtful, this is the case, the bug 487628 was fixed.
But we can check:

Something that could be helpful :

coredumpctl debug baloo_file_extractor -A "-ex bt -ex quit" |& tee backtrace.txt

or

coredumpctl debug baloo_file -A "-ex bt -ex quit" |& tee backtrace.txt

Reference:

Probably not the same bug but the same thing is happening, exactly the same, I get multiple crash messages filling my panel and when I close one it spawns another, I have already send a few of them from the Auto report feature.

Both commands say “No match found.”, I did try to reset it, I also added only basic indexing=true to ~/.config/baloofilerc, purged it and enabled it again, it’s not crashing at the moment, I think it maybe related to a protected file that it’s trying to scan the contents of.

Few notes:

  • First time it happened was when I was setting up few flatpak apps, I left it download and when I came back it was a sleep so when I unlocked it I saw the crash messages
  • The second time (today) it happened when I tried to run few old games from Heroic, I was trying to edit some .ini files

Symptoms are different from bugs, you have similar symptoms indeed.

Good that means we have the stack trace reported.
I looked at the sentry reports, it lacks some debug symbols for baloo_file_extractor unfortunately in Neon.

I am not sure but perhaps the automatic reporting removing your traces locally.

You should be able to see the process concerned by the crash in the crash notification, and use it n the command.

coredumpctl debug <process_name>  -A "-ex bt -ex quit" |& tee backtrace.txt

Hi,

After the latest update it started crashing again but this time I can’t send a report

Starting debugger gdb --nw --nx --batch --init-eval-command=set debuginfod enabled on --command=/tmp/drkonqi.sJNRwL --command=/tmp/drkonqi.IkwnFv --core=/tmp/drkonqi-core.PTFnTw/core /usr/lib/x86_64-linux-gnu/libexec/kf6/baloo_file_extractor

warning: could not find '.gnu_debugaltlink' file for /usr/lib/x86_64-linux-gnu/libexec/kf6/baloo_file_extractor

warning: Can't open file /usr/lib/x86_64-linux-gnu/libQt6WaylandClient.so.6.9.0 during file-backed mapping note processing

warning: Can't open file /usr/lib/x86_64-linux-gnu/libKF6Codecs.so.6.15.0 during file-backed mapping note processing

warning: Can't open file /usr/lib/x86_64-linux-gnu/libQt6DBus.so.6.9.0 during file-backed mapping note processing

warning: Can't open file /usr/lib/x86_64-linux-gnu/libQt6Core.so.6.9.0 during file-backed mapping note processing

warning: Can't open file /usr/lib/x86_64-linux-gnu/libQt6Gui.so.6.9.0 during file-backed mapping note processing

warning: Can't open file /usr/lib/x86_64-linux-gnu/libQt6Xml.so.6.9.0 during file-backed mapping note processing

warning: Can't open file /usr/lib/x86_64-linux-gnu/libKF6CoreAddons.so.6.15.0 during file-backed mapping note processing

warning: Can't open file /usr/lib/x86_64-linux-gnu/libKF6I18n.so.6.15.0 during file-backed mapping note processing

warning: Can't open file /usr/lib/x86_64-linux-gnu/libKF6IdleTime.so.6.15.0 during file-backed mapping note processing

warning: Can't open file /usr/lib/x86_64-linux-gnu/libKF6Crash.so.6.15.0 during file-backed mapping note processing

warning: Can't open file /usr/lib/x86_64-linux-gnu/libKF6BalooEngine.so.6.15.0 during file-backed mapping note processing

warning: Can't open file /usr/lib/x86_64-linux-gnu/libKF6Solid.so.6.15.0 during file-backed mapping note processing

warning: Can't open file /usr/lib/x86_64-linux-gnu/libKF6ConfigCore.so.6.15.0 during file-backed mapping note processing

warning: Can't open file /usr/lib/x86_64-linux-gnu/libKF6FileMetaData.so.6.15.0 during file-backed mapping note processing

warning: core file may not match specified executable file.
[New LWP 15639]
[New LWP 15642]
[New LWP 15644]
[New LWP 15643]
Core was generated by `/usr/lib/x86_64-linux-gnu/libexec/kf6/baloo_file_extractor'.
Program terminated with signal SIGABRT, Aborted.
#0  0x00007c2a8149eb2c in ?? ()
[Current thread is 1 (LWP 15639)]
Traceback (most recent call last):
  File "/usr/share/drkonqi/gdb/python/gdb_preamble/preamble.py", line 812, in print_preamble
    print_preamble_internal()
  File "/usr/share/drkonqi/gdb/python/gdb_preamble/preamble.py", line 783, in print_preamble_internal
    resolve_modules()
  File "/usr/share/drkonqi/gdb/python/gdb_preamble/preamble.py", line 778, in resolve_modules
    image = CoreImage(line)
            ^^^^^^^^^^^^^^^
  File "/usr/share/drkonqi/gdb/python/gdb_preamble/preamble.py", line 746, in __init__
    raise NoBuildIdException(f'No build id found in core image: {eu_unstrip_line}')
NoBuildIdException: No build id found in core image: 0x7c2a7d4f5000+0x10b000 - . - /usr/lib/x86_64-linux-gnu/libQt6WaylandClient.so.6.9.0
No build id found in core image: 0x7c2a7d4f5000+0x10b000 - . - /usr/lib/x86_64-linux-gnu/libQt6WaylandClient.so.6.9.0
Sentry is attempting to send 2 pending events
Waiting up to 30 seconds
Press Ctrl-C to quit
Debugging ended with exit code '1' and exit status 'NormalExit'
Debugging ended with exit code '1' and exit status 'NormalExit'