Bug 350840

Summary:	kontact fully functional at work. When I start it a home, get following error: Could not create collection inbox resourceId: 20
Product:	[Applications] kontact	Reporter:	mjweeder <ron_collins>
Component:	mail	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED UNMAINTAINED
Severity:	grave	CC:	Sascha.Manns
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description mjweeder 2015-07-31 23:14:45 UTC

I was working on kontact at work with three different email accounts.  I set up identities to use for the sending email. I was able to send and receive test emails.  when I got home I started kontact and got the following error message: Could not create collection inbox resourceId: 20.  After pressing ok kontact is terminated.  This occurs every time kontact is started

Reproducible: Always

Steps to Reproduce:
1. start kontact
2.
3.

Actual Results:  
kontact starts and immediately the following error message is printed: Could not create collection inbox resourceId: 20

Expected Results:  
Begin working without error

Comment 1 Sascha Manns 2015-11-23 07:23:19 UTC

I have the same error but with the outbox (Could not create collection outbox, resourceId: 2). It crashes totally.
Kontact & KMail version: 4:15.08.2
Kubuntu Wily

Comment 2 Denis Kurz 2017-06-23 20:17:17 UTC

This bug has never been confirmed for a Kontact version that is based on KDE Frameworks, except possibly a Technology Preview version 5.0.x. Those versions differ significantly from the old 4.x series. Therefore, I plan to close it in around two or three months. In the meantime, it is set to WAITINGFORINFO to give reporters the opportunity to check if it is still valid. As soon as someone confirms it for a recent version (at least 5.1, ideally even more recent), I'll gladly reopen it.

Please understand that we lack the manpower to triage bugs reported for versions almost two years beyond their end of life.

Comment 3 Denis Kurz 2018-02-01 09:50:09 UTC

Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.1 aka 15.12; preferably much more recent), please open a new one unless it already exists. Thank you for all your input.