Bug 393489

Summary:	Search folders are not updating in 18.04
Product:	[Applications] kmail2	Reporter:	Pieter David <pieter.david>
Component:	search	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED WORKSFORME
Severity:	normal
Priority:	NOR
Version:	5.8.0
Target Milestone:	---
Platform:	Arch Linux
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Pieter David 2018-04-25 07:31:16 UTC

Since I upgraded to the 18.04 applications release, search folders stopped updating automatically (I have one with the unread messages from different IMAP accounts, which contains none of the messages I received since the upgrade, while some of the messages from before are marked as read but still there).
I tried to mark some messages as "unread" and then as "read" again, which has helped in the past, but that did not do the trick this time.
Redoing the search through the dialog gives the same results.
The quick filter for "unread" inside separate folders does seem to work fine.

Please let me know if you need any more information.
Thanks in advance!

Comment 1 Pieter David 2018-05-15 09:54:20 UTC

The problem is also present in 5.8.1. Some more information: if I try to redo the search, I get a dialog asking about re-indexing folders (as in https://bugs.kde.org/show_bug.cgi?id=394071, but without crash).
After `akonadictl restart` and re-opening kmail, I see messages like
"unknown: Xapian error in indexer 0x5628475f8a70 : Attempted to delete or modify an entry in a non-existent posting list for example"
and
"unknown: We asked for UID but the server didn't give it back, resultingFlags not stored."
being printed.

Comment 2 Pieter David 2018-05-26 11:51:57 UTC

After running `akonadictl vacuum` and `akonadictl fsck` a few times, akonadi printed a message that the search database was corrupted (the search was crashing, at that point), so I removed it, triggered a re-indexing, recreated the search folder, and now it is working again.

Comment 3 Justin Zobel 2022-11-26 00:13:47 UTC

Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!

Comment 4 Bug Janitor Service 2022-12-11 05:06:58 UTC

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!

Comment 5 Bug Janitor Service 2022-12-26 05:20:49 UTC

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!