After updating to the latest git version, Kmail started with a totally empty folders list. Adding a new IMAP account didn't change anything. The account got synced but there was still no folder. After a restart, Kmail even crashed with the following error message: "The Email program encountered a fatal error and will terminate now. The error was: Protocol version 28 found, expected at least 29" After another restart, Kmail didn't crash, but there were still no folders. Starting the Akonadi console lead to the following error message: "Akonadi can't connect to database: Can't connect to local MySQL server through socket: '/home/pancho/.project-neon-kde//local/share/akonadi/socket-anna/mysql-socket' (2) QMYSQL: Unable to connect" Still it started. Adding another IMAP account via Akonadi Console worked well and made it sync the account, but still: no folders in Kmail... In the Akonadi console, the debugger keeps running (but without errors), while the browser stays completely empty. I need to purge and reinstall, but might wait a while in order to give more information for fixing at least some aspects of this obviously complex set of bugs. Reproducible: Didn't try
Created attachment 75735 [details] Kmail screenshot when it crashed
Created attachment 75736 [details] Akonadi can't connect
Created attachment 75737 [details] ... but does sync...
Created attachment 75738 [details] ... however with an empty browser.
Yet another time restarting Kmail lead to a different crash: "Application: KMail (kmail), signal: Segmentation fault". This is simply not reproduceable because there's everytime another problem.
you have a problem between akonadi version and kdepim don't know why you didn't have good version. Verify your package
This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present? If noone confirms this bug for a Framework-based version of kmail2 (version 5.0 or later, as part of KDE Applications 15.12 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.