Bug 307779 - Receive "Items Requested for an Unknown Collection" error when Kmail checks mail
Summary: Receive "Items Requested for an Unknown Collection" error when Kmail checks mail
Status: RESOLVED DUPLICATE of bug 307746
Alias: None
Product: kmail2
Classification: Applications
Component: general (show other bugs)
Version: 4.9.2
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-10-03 16:10 UTC by Edward Reiss
Modified: 2012-10-15 11:01 UTC (History)
6 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Edward Reiss 2012-10-03 16:10:36 UTC 
Periodically I receive a popup stating "items requested for an unknown collection". This is repeatable as I only have to have Kmail open and checking mail.

Reproducible: Always

Steps to Reproduce:
1. Open Kmail
2. Kmail downloads emails
3. Receive popup message
Actual Results:  
Popup message

Expected Results:  
The software should have seamlessly downloaded email

This is an upgrade 40 4.9.2 from 4.9.1 for Kubuntu 12.04.1
Comment 1 Jonathan D. 2012-10-04 07:57:52 UTC 
I have the same error message. On my computer, it appears when syncing a CalDAV calendar.
Deleting and creating the resource again doesn't solve the issue.
Comment 2 Edward Reiss 2012-10-04 12:04:11 UTC 
I removed the CalDAV calendar and replaced it with the Google calendar connector and the error went away.
Comment 3 Thomas Tanghus 2012-10-09 20:43:15 UTC 
(In reply to comment #1)
> I have the same error message. On my computer, it appears when syncing a
> CalDAV calendar.
> Deleting and creating the resource again doesn't solve the issue.

Same here with my ownCloud DAV resource also on 4.9.2.
Comment 4 Thomas Tanghus 2012-10-10 07:48:25 UTC 
btw, the product in this issue should be changed from kmail2 to DAV Groupware resource.
Comment 5 Christoph Feck 2012-10-15 11:01:30 UTC 

*** This bug has been marked as a duplicate of bug 307746 ***