Bug 431664 - Schedule a re-index for people upgrading to 5.78 or later
Summary: Schedule a re-index for people upgrading to 5.78 or later
Status: RESOLVED INTENTIONAL
Alias: None
Product: frameworks-baloo
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: 5.78.0
Platform: Other Linux
: HI normal
Target Milestone: ---
Assignee: Stefan Brüns
URL:
Keywords:
: 405317 405320 431985 434000 438850 439277 (view as bug list)
Depends on:
Blocks:
 
Reported: 2021-01-15 22:06 UTC by Nate Graham
Modified: 2025-01-22 13:26 UTC (History)
8 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Nate Graham 2021-01-15 22:06:14 UTC 
Bug 430891, Bug 430273, and Bug 430435 are all fixed in Frameworks 5.68--provided that you do a full re-index.

However there is no mechanism to do that automatically, so people with Frameworks 5.78 are still experiencing these bugs. Then they file bug reports, and we tell them to do a `balooctl purge`, which helps. This should probably be done automatically.
Comment 1 Justin Zobel 2021-01-17 06:22:17 UTC 
(In reply to Nate Graham from comment #0)
> Bug 430891, Bug 430273, and Bug 430435 are all fixed in Frameworks
> 5.68--provided that you do a full re-index.
> 
> However there is no mechanism to do that automatically, so people with
> Frameworks 5.78 are still experiencing these bugs. Then they file bug
> reports, and we tell them to do a `balooctl purge`, which helps. This should
> probably be done automatically.

Perhaps on every version change that might affect baloo search. Though it would be best to prompt the user somehow as some may have large indexes that are already working and don't want a full re-index done which could take hours if they have a large collection of files.
Comment 2 Nate Graham 2021-01-27 17:00:52 UTC 
*** Bug 431985 has been marked as a duplicate of this bug. ***
Comment 3 Nate Graham 2021-03-08 16:03:22 UTC 
*** Bug 434000 has been marked as a duplicate of this bug. ***
Comment 4 dagobertram 2021-07-03 08:21:10 UTC 
*** Bug 438850 has been marked as a duplicate of this bug. ***
Comment 5 dagobertram 2021-07-03 08:26:57 UTC 
*** Bug 405317 has been marked as a duplicate of this bug. ***
Comment 6 dagobertram 2021-07-03 08:27:53 UTC 
*** Bug 405320 has been marked as a duplicate of this bug. ***
Comment 7 tagwerk19 2021-07-06 09:58:30 UTC 
Still run into this issue, cf:
     https://bugs.kde.org/show_bug.cgi?id=438850#c12
Think it's worth flagging "Confirmed"

Could perhaps make use of the "dbVersion" and bump it on a significant change.
Comment 8 tagwerk19 2021-10-30 12:04:29 UTC 
Seemingly would catch people upgrading from Debian 10 to Debian 11
... Frameworks 5.54 to 5.78
Comment 9 Nate Graham 2022-11-30 17:09:54 UTC 
At this point everyone should be using 5.78 or later, and unfortunately it's pretty clear we're not going to action this. Closing.
Comment 10 tagwerk19 2024-07-07 21:59:56 UTC 
(In reply to tagwerk19 from comment #7)
> ... Could perhaps make use of the "dbVersion" and bump it on a significant change ...
Cross reference: Bug 477068
Comment 11 postix 2025-01-22 13:21:20 UTC 
*** Bug 439277 has been marked as a duplicate of this bug. ***
Comment 12 postix 2025-01-22 13:26:51 UTC 
I've directly referenced all bugs, which where referenced by "see also" via a marked duplicate of this bug.