SUMMARY I'm having a lot of crashes in baloo_file_extr ever since the 5.103 Framework update. The crashes aren't noticeable apart from I'm getting Kcrash files appearing in my Home directory, but not for every crash. The Kcrash files are completely garbled though, the only way to view them is using the inode of the file to open it but even the contents are garbled. Example: [KCrash] exe=0�&ɹU appname=p'%ɹU apppath=��"ɹU signal=11 pid=7464 The journal has lots of recorded crashes. Using coredumpctl gdb 7464 bt full on the above one shows the following: https://pastebin.com/s15JJCmh STEPS TO REPRODUCE 1. Use filesystem normally 2. Check the journal or coredumpctl periodically for baloo_file_extr crashes OBSERVED RESULT Sometimes garbled kCrash files appear in home directory but otherwise no visible issue. EXPECTED RESULT No Kcrash files and no recorded baloo_file_extr crashes SOFTWARE/OS VERSIONS Linux: Arch KDE Plasma Version: 5.27.0 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Graphics Platform: Wayland
I'm having the same issue on 5.27.1 on Arch Linux. A workaround at the moment is to disable baloo with `balooctl disable`
Same here. Started after plasma 5.27 update. At the beginning, I had one weird file in my home directory. Second time it was 2. Yesterday I had to remove over 600 files. I decided to disable baloo and wait for an update.
(In reply to 860lacov from comment #2) > Same here. > Started after plasma 5.27 update. Also on Arch? Would be interesting to see if there's a link to the filesystem type. Ext4 or something with more wrinkles (like BTRFS)?
I noticed, many comments regarding this issue concern Wayland. It shouldn't be related but I have another computer running Arch on X11 and there's only report for SIGABRT (in coredumctl) on 2023-02-16 while I've been using this computer everyday since this day. This date could have been a moment where I tried Wayland for some reason. Of course baloo is active on this PC. I could be totally wrong, don't hesitate to tell if it's happening for you on X11.
(In reply to tagwerk19 from comment #3) > (In reply to 860lacov from comment #2) > > Same here. > > Started after plasma 5.27 update. > Also on Arch? > > Would be interesting to see if there's a link to the filesystem type. Ext4 > or something with more wrinkles (like BTRFS)? Personally I'm running similar setups on both computers that's to say : - EXT4 for root partitions - XFS for secondary partitions Additionally, I'm having Windows partitions (dual booting) on the PC where baloo crashes A little note to add to my last comment, the only visible entrys in balooctl that DIDN'T GENERATE KCrash files in my HOME directory were SIGABRT while the PC where baloo constantly generates KCrash files were SIGSEGV
(In reply to Oxygel from comment #4) > I noticed, many comments regarding this issue concern Wayland. Oooo. Bulleye! I'd just set up a clean Arch system (BTRFS and X11 on a KVM guest) and not seen anything. Now just installed plasma-wayland-session, logged back in with wayland, did a "balooctl purge" and get crashes. SIGSEGV in baloo_file_extractor plus Kcrash crashing... crashRecursionCounter = 2 Log back in again with X and repeat, no crashes... Don't get the same behaviour on Neon unstable.
Maybe .. Bug 465801
(In reply to tagwerk19 from comment #3) > (In reply to 860lacov from comment #2) > > Same here. > > Started after plasma 5.27 update. > Also on Arch? > > Would be interesting to see if there's a link to the filesystem type. Ext4 > or something with more wrinkles (like BTRFS)? Arch, btrfs, Wayland
(In reply to tagwerk19 from comment #3) > (In reply to 860lacov from comment #2) > > Same here. > > Started after plasma 5.27 update. > Also on Arch? > > Would be interesting to see if there's a link to the filesystem type. Ext4 > or something with more wrinkles (like BTRFS)? Arch and Wayland, ext4 for all drives but btrfs for some network shares
*** Bug 466266 has been marked as a duplicate of this bug. ***
(In reply to Pawel from comment #10) > *** Bug 466266 has been marked as a duplicate of this bug. *** There is a gdb dump with full debug symbols in this bug report. File system is EXT4 Operating System: Arch Linux KDE Plasma Version: 5.27.1 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.2.0-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 24 × AMD Ryzen 9 5900X 12-Core Processor Memory: 31.3 GiB of RAM Graphics Processor: AMD Radeon RX 6800 XT
*** This bug has been marked as a duplicate of bug 465801 ***
(In reply to 860lacov from comment #8) > Arch, btrfs, Wayland If I understand Bug 465801 right, there's a fix coming in Frameworks 5.104