https://bugs.kde.org/show_bug.cgi?id=223034
--- Comment #43 from Neil Darlow <n...@darlow.co.uk> --- Created attachment 82326 --> https://bugs.kde.org/attachment.cgi?id=82326&action=edit Workaround for akonadi/nepomuk startup ordering I have found that this problem is caused by a startup ordering problem relating to akonadi and nepomuk. Specifically, for akonadi address resource indexing to work correctly, nepomukfilewatch and nepomukfileindexer must start before akonadi_nepomuk_feeder. If this does not happen then addresses are not indexed and address expansion fails. This script detects the condition that akonadi_nepomuk_feeder is started before nepomukfilewatch/nepomukfileindexer and, in that case, it sends a HUP signal to akonadi_nepomuk_feeder which causes it to respawn. Indexing will then commence correctly. Copy the script to .e.g. /usr/local/bin and make it executable then add it to your KDE autostart as a script. It will execute at the next login. I have been running this script on fedora-based netbook and desktop systems for months now and my akonadi address resource expansion works flawlessly. Regards, Neil Darlow -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs