Okay … I tried with a fresh user account: Same problem there. akonadi was running, but kontact reported it as “not working properly”. Since there were no email accounts the mail account assisted started, indicating: “Akonadi Server is being started” (while it was already running) which was obviously fruitless, so I shut down the assistant after 5 or 6 minutes. That test was important for me too, because the email, carddav and caldav accounts I had defined in Akonadi are not displayed in the config windows - but thats not because they are gone, and have caused the troubel, but its obviously akonadi thats not displaying them.
So looks very much like a communication problem between Kontact and akonadi.
Just for the record: Akregator is running fine within Kontact (on both, my current and the fresh account).
Output of akonadictl staus:
akonadictl status
Akonadi Control: running
Akonadi Server: running
search paths: ("lib64", "lib64/qt5/plugins/", "lib64/kf5/", "lib64/kf5/plugins/", "/usr/lib/qt5/plugins/", "/usr
/lib64/qt5/plugins", "/usr/bin")
Akonadi Server Search Support: available (Remote Search)
Available Agent Types: akonadi_akonotes_resource, akonadi_archivemail_agent, akonadi_birthdays_resource, akonadi_
contacts_resource, akonadi_davgroupware_resource, akonadi_followupreminder_agent, akonadi_googlecalendar_resource
, akonadi_googlecontacts_resource, akonadi_ical_resource, akonadi_icaldir_resource, akonadi_imap_resource, akonad
i_indexing_agent, akonadi_invitations_agent, akonadi_kalarm_dir_resource, akonadi_kalarm_resource, akonadi_knut_r
esource, akonadi_kolab_resource, akonadi_maildir_resource, akonadi_maildispatcher_agent, akonadi_mailfilter_agent
, akonadi_mbox_resource, akonadi_migration_agent, akonadi_mixedmaildir_resource, akonadi_newmailnotifier_agent, a
konadi_notes_agent, akonadi_notes_resource, akonadi_openxchange_resource, akonadi_pop3_resource, akonadi_sendlate
r_agent, akonadi_vcard_resource, akonadi_vcarddir_resource
Akonadiconsole needs long for a reaction and the brings up the same message as Kontact: "The Akonadi-Service for personal Information-Management isn’t working properly/correctly " (in german!)
Restarting the Server from Akonadi Console brings up a message “Akonadi-Server is being started” and thats running now for 5 Minutes without anything happening that could be seen in ksysguard.
And this is the output in konsole from starting Akonadi Console and restarting AkonadiServer from within:
akonadiconsole
""
connectToServer "/tmp/akonadi-jmbarkei.8CV1R5/akonadiserver.socket"
"AkonadiConsole Browser Widget"
connectToServer "/tmp/akonadi-jmbarkei.8CV1R5/akonadiserver.socket"
Connected to "Akonadi" , using protocol version 52
Server says: "Not Really IMAP server"
Connected to "Akonadi" , using protocol version 52
Server says: "Not Really IMAP server"
org.kde.akonadi.ETM: GEN true true true
org.kde.akonadi.ETM: collection: QVector()
org.kde.akonadi.ETM: GEN true false true
org.kde.akonadi.ETM: collection: QVector()
org.kde.akonadi.ETM: GEN true false true
org.kde.akonadi.ETM: collection: QVector()
org.kde.akonadi.ETM: GEN true false true
org.kde.akonadi.ETM: collection: QVector()
org.kde.akonadi.ETM: Subtree: 279 QSet(279, 320, 318, 319, 316, 317, 315)
org.kde.akonadi.ETM: Subtree: 7 QSet(7)
org.kde.akonadi.ETM: Subtree: 1 QSet(306, 307, 1)
org.kde.akonadi.ETM: Fetch job took 254 msec
org.kde.akonadi.ETM: was collection fetch job: collections: 11
org.kde.akonadi.ETM: first fetched collection: "Search"
org.kde.akonadi.ETM: Subtree: 9 QSet(9)
org.kde.akonadi.ETM: Subtree: 102 QSet(102)
org.kde.akonadi.ETM: Subtree: 103 QSet(103)
org.kde.akonadi.ETM: Subtree: 258 QSet(258)
org.kde.akonadi.ETM: Subtree: 256 QSet(256)
org.kde.akonadi.ETM: Fetch job took 258 msec
org.kde.akonadi.ETM: was collection fetch job: collections: 5
org.kde.akonadi.ETM: first fetched collection: "Notizen"
org.kde.akonadi.ETM: Subtree: 279 QSet(279, 320, 321, 318, 319, 316, 317, 315)
org.kde.akonadi.ETM: Subtree: 7 QSet(7)
org.kde.akonadi.ETM: Subtree: 1 QSet(306, 307, 1)
org.kde.akonadi.ETM: Subtree: 298 QSet(298)
org.kde.akonadi.ETM: Fetch job took 263 msec
org.kde.akonadi.ETM: was collection fetch job: collections: 13
org.kde.akonadi.ETM: first fetched collection: "Search"
org.kde.akonadi.ETM: Subtree: 9 QSet(9)
org.kde.akonadi.ETM: Subtree: 102 QSet(102)
org.kde.akonadi.ETM: Subtree: 279 QSet(296, 279, 297, 320, 321, 318, 319, 316, 317, 315)
org.kde.akonadi.ETM: Subtree: 103 QSet(103)
org.kde.akonadi.ETM: Subtree: 7 QSet(7)
org.kde.akonadi.ETM: Subtree: 175 QSet(176, 177, 253, 190, 175, 188, 189, 186, 187, 184, 185, 182, 183, 180, 181, 178, 179)
org.kde.akonadi.ETM: Subtree: 4 QSet(254, 252, 250, 251, 70, 248, 71, 249, 69, 66, 64, 65, 78, 79, 192, 76, 77, 75, 72, 80, 37, 34, 35, 32, 33, 46, 47, 44, 42, 43, 172
, 40, 173, 41, 171, 55, 52, 53, 51, 48, 49, 62, 63, 60, 61, 58, 191, 59, 56, 57, 6, 4, 5, 12, 13, 10, 11, 22, 23, 20, 21, 18, 19, 16, 278, 17, 30, 31, 277, 28, 29, 26,
27, 24, 25, 247)
org.kde.akonadi.ETM: Subtree: 258 QSet(258)
org.kde.akonadi.ETM: Subtree: 256 QSet(256)
org.kde.akonadi.ETM: Subtree: 1 QSet(259, 306, 307, 1)
org.kde.akonadi.ETM: Subtree: 15 QSet(15)
org.kde.akonadi.ETM: Subtree: 298 QSet(298)
org.kde.akonadi.ETM: Fetch job took 278 msec
org.kde.akonadi.ETM: was collection fetch job: collections: 115
org.kde.akonadi.ETM: first fetched collection: "Search"
Starting/Stopping Akonadi (using an event loop).
… and nothing more. A after akonadi restart in the Konsole, there is nothing happening.
And the single applications just display the same message as kontact. … if they come up …
So, what do we know now:
- it’s not a problem of configuration (otherwise it would have worked from within the fresh account.
- It looks like a problem of communication between Kontact and akonadi but can’t see where it might come from …
Thanks for your time!!
Jay