On an up-to-date fedora 20, I can no longer search emails with akonadi 1.12.1 while everything works fine with akonadi 1.11.0. The setting is an IMAP mailbox with a local cache (disconnected imap) Relevant programs: kdepim and nepomuk 4.12.5-1.fc20, I have tried akonadi-1.12.1-2, 1.12.1-3 and the brand new 1.12.1-5 With akonadi version 1.12.1, searching mails in kmail returns no answer whatever the request is. I have tried to rejuvenate the imap cache by deleting $HOME/.local/share/akonadi. I have tried also to generate again the nepomuk cache by deleting $HOME/.kde/share/apps/nepomuk/repository. It didn't help. What did help was to downgrade akonadi and akonadi-mysql packages to version 1.11.0-2 and to re-generate the caches (without this, akonadi crashes on start. I imagine that between versions 1.11 and 1.12 the format of the database has changed and that version 1.11 can no longer read the database updated by version 1.12). Then everything works all right. Right now, I have two computers, with the same packages configured on the same imap server, except that one has akonadi-1.12.1-3 (and has no working mail search) and the other has akonadi-1.11.0-2 (and has mail search working). I am ready to run some test and/or send some debugging files, but I don't know where to look. Reproducible: Always
Make sure you have baloo package installed. Baloo provides the search functionality in KDE 4.13.
Well, I am running kde-4.12.5 (the latest kde packaged for fedora 20), and there is no baloo for this version. Are you meaning that akonadi-1.12 is only meant to work with kde-4.13 and should not have been pushed for fedora 20 updates ?
Sorry, I assumed you run 4.13 already Akonadi 1.12 should work with Nepomuk in KDE 4.12 just fine.
I'd love to run 4.13, but I prefer to stick to fedora's packages (and, even though the next fedora is only scheduled for october, there does not seem to be a plan to release kde 4.13 for the current fedora.) Anyway. Is there anything I can do to help debug this ? I have refrained to downgrade akonadi's version and rebuild the database in the hope that I might help. If there's nothing I can do, I'll do the downgrade and get back mail searching...
Sorry, to be completely honest, with Baloo coming in, Nepomuk went to second, maybe even third rail and the not really maintained anymore (not in upstream, not much in Akonadi either). In one of next version of Akonadi we are going to kill Nepomuk support for good. If you really want your search back, you can either downgrade (but you need to wipe your DB), but I would much much more recommend upgrading to 4.13 and getting Baloo. You will be amazed by the speed :-)
(In reply to comment #5) > Sorry, to be completely honest, with Baloo coming in, Nepomuk went to > second, maybe even third rail and the not really maintained anymore (not in > upstream, not much in Akonadi either). In one of next version of Akonadi we > are going to kill Nepomuk support for good. > > If you really want your search back, you can either downgrade (but you need > to wipe your DB), but I would much much more recommend upgrading to 4.13 and > getting Baloo. You will be amazed by the speed :-) Hi Daniel, is there any description/documentation what technology is used for which kind of search in KMAIL? As I understant there are semantic desktop(Nepomuk/Baloo) search and direct search (ALT+Q). I've got a trouble with ALT+Q search on KMAIL 4.13. I'm not sure if that's bug or wrong setting (I've disabled Nepomuk somewhere about 4.10, but Baloo is running now). Thank you in advance.
In KDE 4.13, Baloo is used for all searches in KMail. Nepomuk is not used in 4.13 at all and it's setting does not affect Baloo configuration. If you have problem with KMail search, I recommend opening a bug against KMail.
This bug has only been reported for versions older than KDEPIM 4.14 (at most akonadi-1.3). Can anyone tell if this bug still present? If noone confirms this bug for a recent version of akonadi (part of KDE Applications 15.08 or later), it gets closed in about three months.
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.