Summary: | List entry for home folder is can be deleted, but always returns upon re-opening the KCM | ||
---|---|---|---|
Product: | [Applications] systemsettings | Reporter: | Yurii Kolesnykov <yurii.kolesnykov> |
Component: | kcm_baloo | Assignee: | baloo-bugs-null |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | nate, plasma-bugs, yurii.kolesnykov, zrenfire |
Priority: | NOR | ||
Version: | 5.19.4 | ||
Target Milestone: | --- | ||
Platform: | Other | ||
OS: | Linux | ||
Latest Commit: | https://invent.kde.org/plasma/plasma-desktop/commit/07dcff19b05ed63311fc42665d559f11c7281870 | Version Fixed In: | 5.22 |
Sentry Crash Report: |
Description
Yurii Kolesnykov
2020-08-14 23:25:40 UTC
Yeah, we should probably not let the user remove this entry, only change its indexing status. A possibly relevant merge request was started @ https://invent.kde.org/plasma/plasma-desktop/-/merge_requests/439 Possibly related: https://www.reddit.com/r/ManjaroLinux/comments/my55oc/weird_file_indexing_glitch_in_manjarokde/ The user changed their home directory to "Not Indexed", selected another KCM, then opened up "File Search" again to see: /home/user "Indexed" /home/user "Not Indexed" He repeated it to get /home/user "Indexed" /home/user "Not Indexed" /home/user "Not Indexed" Git commit 07dcff19b05ed63311fc42665d559f11c7281870 by Nate Graham. Committed on 26/04/2021 at 10:39. Pushed by ngraham into branch 'master'. [kcms/baloo] Don't allow removing the home path Baloo doesn't actually support not indexing the home path at all, but the UI allows it, sort of: you can do it, but it doesn't actually have any effect, and and the removed entry comes back when you leave and return to the KCM. So let's remove the possibility of doing it at all by marking the home path in the model as not deletable. FIXED-IN: 5.22 M +1 -1 kcms/baloo/filteredfoldermodel.cpp https://invent.kde.org/plasma/plasma-desktop/commit/07dcff19b05ed63311fc42665d559f11c7281870 |