Summary: | Crash when i click "Properites" | ||
---|---|---|---|
Product: | [Frameworks and Libraries] frameworks-baloo | Reporter: | TYMA <TYMA22389> |
Component: | general | Assignee: | baloo-bugs-null |
Status: | RESOLVED WORKSFORME | ||
Severity: | crash | CC: | akselmo, kfm-devel, nate, tagwerk19 |
Priority: | NOR | Keywords: | drkonqi |
Version: | 5.112.0 | ||
Target Milestone: | --- | ||
Platform: | Arch Linux | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
TYMA
2023-12-08 13:07:13 UTC
Seems to be Baloo issue so moved there. (In reply to TYMA from comment #0) > ... > #5 0x00007fd3d5a98b56 in mdb_env_open () at /usr/lib/liblmdb.so > #6 0x00007fd3d7db30e9 in Baloo::Database::open(Baloo::Database::OpenMode) () at /usr/lib/libKF5BalooEngine.so.5 > #7 0x00007fd3da205d81 in Baloo::File::load() () at /usr/lib/libKF5Baloo.so.5 > ... It's trying to find/open the database - something that should be under ~/.local/share/baloo I think if the file's simply not there, you simply don't get any results. Maybe the file has been truncated/corrupted. Close down the baloo_file indexer, go to the folder and rename the "index" file. Something like: $ pkill baloo_file $ cd ~/.local/share/baloo $ mv index index.suspect I assume your Arch runs with systemd, so you can restart the indexing with: $ systemd --user start kde-baloo (In reply to tagwerk19 from comment #2) > $ systemd --user start kde-baloo Sorry... $ systemctl --user start kde-baloo If the file is there, maybe it's been corrupted. If so can you run `mv ~/.local/share/baloo/index ~/.local/share/baloo/index.old` in a terminal window to move it aside, then reboot, and try again? Does that fix it? 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! This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now 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 Thank you for helping us make KDE software even better for everyone! |