Baloo File Extractor Crashing Constanly

I am using KDE Neon user edition.

Right after update now and there is constant message popping up with “Baloo File Extractor Closed Unexpectedly”

Not sure what is the reason.

I have already rebooted twice but it still crashes constantly.

Any suggestion on why this is happening?

Thanks!

Screenshot_20260318_194448

This appears to be a crash caused by a recent (today) update to libexiv2. See this post for a potential work-around while the issue gets fixed.

1 Like

issue the command

sudo apt install libexiv2-27=0.27.6-1build1

to downgrade that update and wait for it to get fixed before allowing it update again.

1 Like

I downgraded it but it start craching after reboot for a while and stopped for now.

Do I need to hold this package like it is suggested in this thread?
If so, how should I enable the update back again later?

Thanks!

my discover is set to manual updates without the offline updates feature turned on

so that i’m in control of when the update gets reapplied.

if you issue the hold, you will not have visibility to when it’s available to fix and you might forget about it

i’ve got the little red badge in my system tray to remind me.

1 Like

Thanks for explaining

That’s a regression in ubuntu also affecting kubuntu.

See workaround in Kioslave 5 closed unexpectedly - #5 by Yaulande

you want to switch the apply system updates to Immediately.

the wording in plasma 5 was more clear.

the point is you want to see the updates listed in discover instead of having them rolled up in a single System Update check box.

that way you will see the package listed as i have shown in the screen shot and you will see when other packages come down.

i would recommend unchecking this particular package until we get the all clear from kubuntu

if that starts to drag out, then i would consider putting a hold on it.

1 Like

Okay, Got it Thanks!

currently on my kubuntu 24.04 apt list --upgradable is showing this list of packages being held back

so perhaps the dreaded package was supposed to be held back as well to await these others, but somehow slipped thru the gates


binutils-common/noble-updates 2.42-4ubuntu2.10 amd64 [upgradable from: 2.42-4ubuntu2.8]
binutils-x86-64-linux-gnu/noble-updates 2.42-4ubuntu2.10 amd64 [upgradable from: 2.42-4ubuntu2.8]
binutils/noble-updates 2.42-4ubuntu2.10 amd64 [upgradable from: 2.42-4ubuntu2.8]
coreutils/noble-updates 9.4-3ubuntu6.2 amd64 [upgradable from: 9.4-3ubuntu6.1]
libbinutils/noble-updates 2.42-4ubuntu2.10 amd64 [upgradable from: 2.42-4ubuntu2.8]
libctf-nobfd0/noble-updates 2.42-4ubuntu2.10 amd64 [upgradable from: 2.42-4ubuntu2.8]
libctf0/noble-updates 2.42-4ubuntu2.10 amd64 [upgradable from: 2.42-4ubuntu2.8]
libexiv2-27/noble-security 0.27.6-1ubuntu0.1 amd64 [upgradable from: 0.27.6-1build1]
libgprofng0/noble-updates 2.42-4ubuntu2.10 amd64 [upgradable from: 2.42-4ubuntu2.8]
libsframe1/noble-updates 2.42-4ubuntu2.10 amd64 [upgradable from: 2.42-4ubuntu2.8]


Hmmm… my Neon has the same list being held (except the new libexiv2 which is installed). I wonder why? I may make a Timeshift restore point an manually upgrade them with the “–only-upgrade” switch.

seems unrelated, the new patch 0.27.6-1ubuntu0.3 is now available in my kubuntu discover and it seems to be working

those other packages will get release when their time comes.

Just update the system including livexiv2-27=0.27.6-1ubuntu0.3 It crashed a few time after reboot but it seems table now.

Its not solved yet. It crashes on every reboot as of now

do you still have some 100 pending updates, or did you let those go thru?

i would update everything and the down grade that one package as mentioned above and seel how things behave after a reboot then.

if it still has issues, perhaps try creating a new user to see if it happens with that user acct as well or if it just happens with yours.