Open
Bug 947138
Opened 12 years ago
Updated 2 years ago
Events randomly not showing when offline mode support selected
Categories
(Calendar :: Provider: CalDAV, defect)
Tracking
(Not tracked)
UNCONFIRMED
People
(Reporter: eric, Unassigned)
Details
User Agent: Mozilla/5.0 (X11; Ubuntu; Linux i686; rv:25.0) Gecko/20100101 Firefox/25.0 (Beta/Release)
Build ID: 20131115110315
Steps to reproduce:
When "offline mode support" is checked on a DAV calendar properties dialog, events randomly disappear. Sometimes they even never show up after their creation. Any kind of event can be affected (single events, periodic events , ...)
When offline mode support is unchecked, everything works fine.
Firefox version 25.0.1 (canonical build for ubuntu system)
| Reporter | ||
Comment 1•12 years ago
|
||
Sorry, I mentionned my firefox version instead of my thunderbird version ... hum ... :
thunderbird 24.1.1
Severity: normal → major
OS: All → Linux
Hardware: All → x86
Comment 2•12 years ago
|
||
I can report a similar (same?) bug with
User agent: Mozilla/5.0 (Windows NT 5.1; rv:26.0) Gecko/20100101 Firefox/26.0 SeaMonkey/2.23
Build identifier: 20131210201652
using
Lightning 2.8b1
I use several CalDAV sources on an OwnCloud server. For months this used to be a very nicely stable setup. But in recent weeks, strange communication problems occurred. I had initially created the calendars with offline support ON. So I thought it a good idea to test whether this offline feature might have to do with it.
Turn offline support off: calendars keep working (as long as connected to the web)
Turn offline support on: all events and tasks are "gone" -- meaning they do not show in lightning anymore
Turn offline support back off: calendars are working again.
This is reproducible.
An annoying quirk that makes offline work that much more difficult.
Updated•5 years ago
|
Component: Lightning Only → Provider: CalDAV
Comment 3•3 years ago
|
||
In the process of migrating remaining bugs to the new severity system, the severity for this bug cannot be automatically determined. Please retriage this bug using the new severity system.
Severity: major → --
You need to log in
before you can comment on or make changes to this bug.
Description
•