[frameworks-baloo] [Bug 462909] baloo_file crashed at mdb_assert_fail.constprop.0 on GNOME after login
https://bugs.kde.org/show_bug.cgi?id=462909 Fushan Wen changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |WORKSFORME --- Comment #5 from Fushan Wen --- Seems fixed -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 462909] baloo_file crashed at mdb_assert_fail.constprop.0 on GNOME after login
https://bugs.kde.org/show_bug.cgi?id=462909 postix changed: What|Removed |Added CC||pos...@posteo.eu -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 462909] baloo_file crashed at mdb_assert_fail.constprop.0 on GNOME after login
https://bugs.kde.org/show_bug.cgi?id=462909 tagwer...@innerjoin.org changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #4 from tagwer...@innerjoin.org --- (In reply to Fushan Wen from comment #3) > I am using btrfs. It is strange is that baloo is still running when you have switched to Gnome, I'd expect it to close down when you log out of KDE. However, there are times when closing down baloo doesn't work, that is if you do a "balooctl disable", you still have the baloo_file process running. My gut feeling, as you are using OpenSUSE and BTRFS, it's likely that your home drive has been (re)mounted with a new/different device number and baloo sees a completely new set of files to index (and a large set of files that it had indexed, which have vanished). When baloo sorts through this, it can get stuck and not to respond to signals. Maybe it could still be running after you have logged out and back in under Gnome. You can see if your database has has grown unexpectedly large with "balooctl indexSize", if it is very large that would be a warning sign, and you can check whether baloo is seeing device numbers changing by comparing "stat" and "balooshow -x" as described here: https://bugs.kde.org/show_bug.cgi?id=402154#c12 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 462909] baloo_file crashed at mdb_assert_fail.constprop.0 on GNOME after login
https://bugs.kde.org/show_bug.cgi?id=462909 --- Comment #3 from Fushan Wen --- (In reply to tagwerk19 from comment #1) > Baloo running under Gnome? Strange. > Do you have anything unusual configured? > What sort of filesystem, Ext4? BTRFS? I installed two desktop environments, and can't remember any unusual configured. I am using btrfs. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 462909] baloo_file crashed at mdb_assert_fail.constprop.0 on GNOME after login
https://bugs.kde.org/show_bug.cgi?id=462909 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 462909] baloo_file crashed at mdb_assert_fail.constprop.0 on GNOME after login
https://bugs.kde.org/show_bug.cgi?id=462909 tagwer...@innerjoin.org changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO CC||tagwer...@innerjoin.org --- Comment #1 from tagwer...@innerjoin.org --- Baloo running under Gnome? Strange. Do you have anything unusual configured? What sort of filesystem, Ext4? BTRFS? -- You are receiving this mail because: You are watching all bug changes.
