Bug 701327

Summary:	Reloading remote ics calendars fails
Product:	[Fedora] Fedora	Reporter:	Bruno Wolff III <bruno>
Component:	thunderbird-lightning	Assignee:	Orion Poplawski <orion>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	15	CC:	mcepl, orion
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-05-28 16:07:20 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Bruno Wolff III 2011-05-02 15:30:44 UTC

Description of problem:
When reloading remote calendars, ics calendars are dropped.
For example I have http://rbergero.fedorapeople.org/schedules/f-15/f-15-all-milestones.ics and when it gets reloaded by either the automatic reloads or manual reloads of remote calendars, all of the events for the calendar are dropped. Sunbird (installed with --nodeps) doesn't have this problem. Restarting thunderbird results in the events showing up again.
I have a remote caldav calendar that doesn't have this problem.

Version-Release number of selected component (if applicable):
thunderbird-lightning-1.0-0.41.b3pre.fc15.x86_64

How reproducible:
100% (at least with that remote calendar)

Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Orion Poplawski 2011-05-03 19:18:39 UTC

Upstream is the place to file bugs.  Also, as per: http://weblogs.mozillazine.org/calendar/2011/03/lightning_trunk_version_change.html upstream is basically focusing on a TB 3.3 compatible release.  So, my instinct is to close this WONTFIX.  If you do file an issue upstream, feel free to link it to this and perhaps I'll leave it open as a tracker.

Comment 2 Matěj Cepl 2011-05-28 16:07:20 UTC


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