Description of problem: I updated kontact today and now its asking me to set up my accounts. It was working fine until this update. I have 12 years of data in an account. Did this update lose all my information? Should it have migrated settings or something? Is it incompatible with previous kontact? Version-Release number of selected component (if applicable): kontact-16.08.3-2.fc24.x86_64 kmail-16.08.3-2.fc24.x86_64 Steps to Reproduce: 1. dny -y update 2. open kontact Actual results: My email Expected results: Being asked to setup an account.
kdepim-16.12.2-3.fc24 has been submitted as an update to Fedora 24. https://bodhi.fedoraproject.org/updates/FEDORA-2017-81bed9e1d4
OK. With the update mentioned, kontact does have my data again. However, its very unstable and still unusable. It segfaults starting up, akonadi segfaults when fetching mail, and then it loses connection with the imap server. Mar 8 18:46:15 x2 akonadi_imap_resource: org.kde.pim.akonadicore: The item sync is being rolled-back. Mar 8 18:46:15 x2 akonadi_imap_resource: org.kde.pim.imapresource: Fetch job failed "Connection to server lost." Mar 8 18:46:15 x2 akonadi_imap_resource: org.kde.pim.imapresource: "" Mar 8 18:46:47 x2 akonadi_imap_resource: org.kde.pim.kimap: Connection to server lost 0 Mar 8 18:46:47 x2 akonadi_imap_resource: org.kde.pim.imapresource: Session login cancelled Kontact is so complex the only solution is to reboot the system. I can usually access 1 or 2 emails before it loses the session.
*** Bug 1430590 has been marked as a duplicate of this bug. ***
You can probably consider some variant of the following to avoid having to reboot or restart session: (command line): akonadictl restart or even akonadictl stop (and it should restart itself on demand the next time you launch an akonadi client, like kmail or kontact) Of course, the more pressing issue here is: akonadi_imap_resource: org.kde.pim.kimap: Connection to server lost 0
I filed several bz upstream about how unstable this new release is: https://bugs.kde.org/show_bug.cgi?id=377399 kontact loses imap connections constantly https://bugs.kde.org/show_bug.cgi?id=377393 /usr/bin/akonadiserver crashes https://bugs.kde.org/show_bug.cgi?id=377395 Kontact is crashing during start up I also see the retrace server starting to count up crashes.
Still getting the following (Times are AEST): Last metadata expiration check: 0:13:11 ago on Sat Mar 11 09:45:57 2017. Dependencies resolved. ========================================================================= Package Arch Version Repository Size ========================================================================= Skipping packages with broken dependencies: akregator x86_64 16.12.2-1.fc24 updates 677 k akregator-libs x86_64 16.12.2-1.fc24 updates 560 k gpgme x86_64 1.8.0-10.fc24 updates 196 k kaddressbook x86_64 16.12.2-1.fc24 updates 80 k kaddressbook-libs x86_64 16.12.2-1.fc24 updates 151 k kdepim-addons x86_64 16.12.2-1.fc24 updates 1.0 M kdepim-apps-libs x86_64 16.12.2-1.fc24 updates 159 k kf5-libkleo x86_64 16.12.2-1.fc24 updates 364 k kf5-mailcommon x86_64 16.12.2-1.fc24 updates 518 k kf5-messagelib x86_64 16.12.2-1.fc24 updates 5.2 M kleopatra x86_64 16.12.2-1.fc24 updates 1.4 M kleopatra-libs x86_64 16.12.2-1.fc24 updates 93 k kmail x86_64 16.12.2-1.fc24 updates 1.5 M kmail-libs x86_64 16.12.2-1.fc24 updates 940 k knotes-libs x86_64 16.12.2-1.fc24 updates 243 k kontact x86_64 16.12.2-1.fc24 updates 766 k kontact-libs x86_64 16.12.2-1.fc24 updates 92 k korganizer x86_64 16.12.2-1.fc24 updates 732 k korganizer-libs x86_64 16.12.2-1.fc24 updates 795 k Transaction Summary ========================================================================= Skip 19 Packages Nothing to do. Complete!
kdepim-16.12.2-3.fc24 has been pushed to the Fedora 24 stable repository. If problems still persist, please make note of it in this bug report.
KMail will not start because Akonadi will not start $ akonadictl start /usr/bin/mysqladmin: connect to server at 'localhost' failed error: 'Can't connect to local MySQL server through socket '/tmp/akonadi-kmg.pbmcxO/mysql.socket' (111 "Connection refused")' Check that mysqld is running and that the socket: '/tmp/akonadi-kmg.pbmcxO/mysql.socket' exists!