Version: (using KDE 4.1.3) OS: Linux Installed from: Ubuntu Packages I have a bunch of address books; krunner seems to be looking in one of them, but not any of the others. I have tried changing which address books are active in kontact, but that doesn't seem to have any effect in krunner. krunner itself doesn't seem to have any way to control which address books are in use. Either krunner should look in all address books, or it should provide some way to control which address books are searched. Right now, there seems to be no indication of where it's looking, or any way to control which address books it uses. Its current behaviour makes it more or less useless as a tool for using contact information.
it uses the kde addressbook, whatever that is according to the KABC library. i suppose your request is to port this runner to akonadi.
I don't really understand what you're saying :-( Sorry. From a user standpoint, it seems to me that the normal interaction that one has with address books is via kontact (that's the only place I know of where one generally edits and otherwise manipulates them). krunner seems to be using ONE of the many address books accessible to kontact. But I have no idea how it selects which one to use, nor how to change the one that it is using. In particular, the one that it is using seems to be completely independent of the ones that are currently active in kontact. I'm sorry if I'm not using the right terms. This report is simply a reflection of behaviour that seems incorrect to me as a user. I don't know the technical details behind how krunner decides which address book to use. I just know that right now my system is using one particular address book out of the several that are available, and I don't see any any to change which address book is being used.
Just a note to say that this is still a wish in 4.2. That is, in 4.2 there still doesn't seem to be any way to control or even to know which address books are being used by krunner. Basically, there's no way to know whether krunner will find a match for a contact.
With Plasma 5, the Akonadi integration isn't ready, and given that Akonadi is being re-written the runners will also need significant work. Resolving this bug as LATER.