Launchpad has imported 9 comments from the remote bug at https://bugs.kde.org/show_bug.cgi?id=380171.
If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. ------------------------------------------------------------------------ On 2017-05-25T08:14:25+00:00 Gerdfleischer wrote: Created attachment 105703 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 Reply at: https://bugs.launchpad.net/ubuntu/+source/kmail/+bug/1821868/comments/0 ------------------------------------------------------------------------ On 2017-05-25T16:35:45+00:00 Gerdfleischer wrote: 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. Reply at: https://bugs.launchpad.net/ubuntu/+source/kmail/+bug/1821868/comments/1 ------------------------------------------------------------------------ On 2019-03-15T08:34:02+00:00 Rik Mills wrote: Also occurring on Debian Buster with 18.08 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861960 Reply at: https://bugs.launchpad.net/ubuntu/+source/kmail/+bug/1821868/comments/2 ------------------------------------------------------------------------ On 2019-03-15T08:34:31+00:00 Rik Mills wrote: Can also see this on 18.12.3 packages staged for Kubuntu Reply at: https://bugs.launchpad.net/ubuntu/+source/kmail/+bug/1821868/comments/3 ------------------------------------------------------------------------ On 2019-03-16T02:06:31+00:00 Rik Mills wrote: 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. Reply at: https://bugs.launchpad.net/ubuntu/+source/kmail/+bug/1821868/comments/4 ------------------------------------------------------------------------ On 2019-03-16T10:06:19+00:00 Rik Mills wrote: Also confirmed on KDE Neon user edition with PIM 18.12.3 Reply at: https://bugs.launchpad.net/ubuntu/+source/kmail/+bug/1821868/comments/5 ------------------------------------------------------------------------ On 2019-03-27T08:55:07+00:00 Rik Mills wrote: Ubuntu Bug: https://bugs.launchpad.net/kmail/+bug/1821868 Debian bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861960 Reply at: https://bugs.launchpad.net/ubuntu/+source/kmail/+bug/1821868/comments/7 ------------------------------------------------------------------------ On 2019-03-27T10:02:48+00:00 Rik Mills wrote: 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. Reply at: https://bugs.launchpad.net/ubuntu/+source/kmail/+bug/1821868/comments/8 ------------------------------------------------------------------------ On 2019-03-27T10:08:08+00:00 Dvratil-7 wrote: 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. Reply at: https://bugs.launchpad.net/ubuntu/+source/kmail/+bug/1821868/comments/9 ** Changed in: kmail Importance: Unknown => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821868 Title: Kmail (or Kontact) crashes on 1st run on a fresh system: Failed SpecialCollectionsRequestJob::slotResult "Invalid parent" To manage notifications about this bug go to: https://bugs.launchpad.net/kmail/+bug/1821868/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
