https://bugs.kde.org/show_bug.cgi?id=467101
--- Comment #3 from tagwer...@innerjoin.org ---
(In reply to ha51wl8j from comment #2)
> ... more about the corrupted files in my home directory which should not
> appear no matter
> how much baloo crashes ...
There might be a "distribution" component...
I could replicate the crashes, with "left over" files in $HOME, on Arch.
I remember I didn't encounter the issue on Neon Unstable, but I did get a
notification on Fedora 37:
Kcrash: Application '???zU' crashing... (application name varies...)
Kcrash: Attempting to start >:EzU
Warning: socket path is too long
Kcrash failed to exec(), errno = 2
But I did not seem to get a corrupt coredump
I tried Tumbleweed and got crashes, listed by coredumpctl, but no notifications
or strange files.
Best to consider these as recollections (based on scribbled notes) rather than
hard, reproduceable, evidence. In all cases the upgrade to Frameworks 5.104
fixed the baloo_file_extractor crash.
--
You are receiving this mail because:
You are watching all bug changes.
