Summary: | (SIGABRT) Baloo crashes on login | ||
---|---|---|---|
Product: | [Frameworks and Libraries] frameworks-baloo | Reporter: | postix <postix> |
Component: | general | Assignee: | baloo-bugs-null |
Status: | RESOLVED WORKSFORME | ||
Severity: | crash | CC: | postix, tagwerk19 |
Priority: | NOR | ||
Version: | 5.94.0 | ||
Target Milestone: | --- | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
postix
2022-06-16 18:37:50 UTC
(In reply to postix from comment #0) > SOFTWARE/OS VERSIONS > Operating System: openSUSE Tumbleweed 20220613 Not related directly to the crash - but are you using Tumbleweed with BTRFS (with multiple subvols)? Have a look at: https://bugs.kde.org/show_bug.cgi?id=402154#c12 and check whether you are seeing the "Device" number changing. This will overload baloo and maybe stress it to the point it fails. (In reply to tagwerk19 from comment #1) > Not related directly to the crash - but are you using Tumbleweed with BTRFS > (with multiple subvols)? Yes and yes. > Have a look at: > https://bugs.kde.org/show_bug.cgi?id=402154#c12 > and check whether you are seeing the "Device" number changing. This will > overload baloo and maybe stress it to the point it fails. I tried it and it says: stat testfile.txt: `Devices: 0/44` balooshow -x testfile.txt: 44 That looks fine to me. (In reply to postix from comment #2) > stat testfile.txt: `Devices: 0/44` > balooshow -x testfile.txt: 44 Next time you reboot, have another look. You can also see what: baloosearch -i filename:testfile.txt gives you, this would be the "DocID" and filename. It would show you if Baloo had seen the file several times (with different device numbers) I found the BTRFS mounts reappearing with different "minor" device numbers ( > I found the BTRFS mounts reappearing with different "minor" device numbers (
Right, after rebooting, the device number has changed from `44` to `43`:
```
$ stat testfile.txt
File: testfile.txt
Devices: 0/43 Inode: 16577140 Links: 1
```
```
$ balooshow -x testfile.txt
fcf2740000002b 43 16577140 testfile.txt: No index information found
```
(In reply to postix from comment #4) > Right, after rebooting, the device number has changed from `44` to `43`... You should see baloosearch -i filename:testfile.txt giving results for the file when it was indexed on the "44" and the "43" Minor Devices... ... I am admittedly being sloppy with the "Minor Device Number" description, it is more properly described here: https://bugs.kde.org/show_bug.cgi?id=402154#c44 Haven't seen this again. |