Created attachment 105703 [details] screenshot or error dialog window KMail crashes on first start xsession errors: org.kde.pim.maildirresource: the resource is not properly configured: there is no config file for the resource. We create a new one. org.kde.akonadi.ETM: GEN true false false org.kde.akonadi.ETM: collection: QVector() org.kde.akonadi.ETM: QObject::killTimer: Timers cannot be stopped from another thread org.kde.akonadi.ETM: Subtree: 5 QSet(5) org.kde.akonadi.ETM: Fetch job took 37 msec org.kde.akonadi.ETM: was collection fetch job: collections: 1 org.kde.akonadi.ETM: first fetched collection: "Local Folders" org.kde.akonadi.ETM: collection: QVector() org.kde.akonadi.ETM: Fetch job took 39 msec org.kde.akonadi.ETM: was collection fetch job: collections: 4 org.kde.akonadi.ETM: first fetched collection: "Search" org.kde.pim.akonadicore: Failed SpecialCollectionsRequestJob::slotResult "Invalid parent" org.kde.akonadi.ETM: Fetch job took 1 msec org.kde.akonadi.ETM: was collection fetch job: collections: 0 org.kde.pim.mailcommon: "The Email program encountered a fatal error and will terminate now.\nThe error was:\nInvalid parent" "No file selected." org.kde.pim.akonadicore: not referenced 4 org.kde.pim.maildirresource: the resource is not properly configured: there is no config file for the resource. We create a new one. QObject::killTimer: Timers cannot be stopped from another thread org.kde.pim.akonadicore: not referenced 12
with debug packages org.kde.akonadi.ETM: was collection fetch job: collections: 0 org.kde.pim.akonadicore: Failed SpecialCollectionsRequestJob::slotResult "Invalid parent" org.kde.pim.mailcommon: "The Email program encountered a fatal error and will terminate now.\nThe error was:\nInvalid parent" org.kde.pim.akonadiserver: DATABASE ERROR: org.kde.pim.akonadiserver: Error code: 1062 org.kde.pim.akonadiserver: DB error: "Duplicate entry '4-outbox' for key 'CollectionTable_parentAndNameIndex'" org.kde.pim.akonadiserver: Error text: "Duplicate entry '4-outbox' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement" org.kde.pim.akonadiserver: Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, cachePolicyCheckInterval, cachePolicyCacheTimeout, cachePolicySyncOnDemand, cachePolicyLocalParts, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10, :11, :12, :13, :14)" org.kde.pim.akonadiserver: Error during insertion into table "CollectionTable" "Duplicate entry '4-outbox' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement" org.kde.pim.akonadicore: Failed SpecialCollectionsRequestJob::slotResult "Could not create collection outbox, resourceId: 3" org.kde.pim.maildispatcher: Failed to get outbox folder. Retrying in: 5000 org.kde.pim.akonadicore: Failed CollectionCreateJob. "Could not create collection outbox, resourceId: 3" "No file selected." org.kde.pim.akonadicore: not referenced 3 org.kde.pim.maildirresource: the resource is not properly configured: there is no config file for the resource. We create a new one. QObject::killTimer: Timers cannot be stopped from another thread org.kde.pim.akonadicore: not referenced 14 Also, if akonadiserver is started manually before everything is ok.
Also occurring on Debian Buster with 18.08 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861960
Can also see this on 18.12.3 packages staged for Kubuntu
Reproducible here on debian sid/buster. Requires a pristine install with NO config files or db created yet OR after stopping akonadi and doing rm -fr ~/.local/share/akonadi* ~/.cache/akonadi* ~/.config/akonadi* ~/.config/specialmailcollectionsrc then trying. removing ~/.config/specialmailcollectionsrc (which would not exist in pristine install) seems crucial.
Also confirmed on KDE Neon user edition with PIM 18.12.3
Ubuntu Bug: https://bugs.launchpad.net/kmail/+bug/1821868 Debian bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861960
Creating the ~/.config/specialmailcollectionsrc file with its default content of: [SpecialCollections] DefaultResourceId=akonadi_maildir_resource_0 prior to 1st launch prevents the crash, but I don't know if that would adversely affect the running of Kmail after that.
I think this is a race condition in the initial setup: the race could be that on first start the Maildir resource (that backs the "Local folders") starts discovering what folders exist in ~/.local/share/mail and starts creating them in Akonadi and at the same time KMail realizes there's no Inbox, Outbox etc. in Local Folders and starts creating them. At some point they clash as they both attempt to create the same collection - one of them wins and one of them fails with the SQL error - if KMail is the one who loses, it aborts the initial job and triggers the "fatal error" dialog.
Still occurs in 19.08.1 in Neon, and Kubuntu staging builds.
Thank you for reporting this crash in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the crash with a recent software version? If you can reproduce the issue, please change the status to "CONFIRMED" when replying. Thank you!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!