After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 671639 - Fails to load calendar if there is an event without a DTEND
Fails to load calendar if there is an event without a DTEND
Status: RESOLVED DUPLICATE of bug 678856
Product: evolution
Classification: Applications
Component: Calendar
3.0.x (obsolete)
Other Linux
: Normal normal
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2012-03-08 11:35 UTC by Ed
Modified: 2012-07-26 17:10 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Ed 2012-03-08 11:35:41 UTC
When an event does not come with a DTEND the whole calendar fails to load.

With investigation evolution reports:

$ export CALDAV_DEBUG=all
$ evolution

(evolution:22592): calendar-gui-CRITICAL **: e_day_view_add_event:
assertion `start <= end' failed

To see whether this is a bug or not, I read the iCalendar spec at http://tools.ietf.org/html/rfc5545

which states:

"
For cases where a "VEVENT" calendar component specifies a "DTSTART"
property with a DATE value type but no "DTEND" nor "DURATION" property,
the event's duration is taken to be one day. For cases where a "VEVENT"
calendar component specifies a "DTSTART" property with a DATE-TIME value
type but no "DTEND" property, the event ends on the same calendar date
and time of day specified by the "DTSTART" property.
"

i.e. DTEND and DURATION are not mandatory and a DTSTART of DATE type means all day, and a DTSTART of DATE-TIME means that point in time - which needs to be calculated before it gets to the gui assert (above).
Comment 1 Milan Crha 2012-07-25 17:54:15 UTC
Thanks for a bug report. 3.0.x is quite old, the current stable is 3.4.3. There was similar issue fixed within bug #678856, though certain parts of the fix from that bug report are not relevant for your issue.
Comment 2 Ed 2012-07-26 14:34:21 UTC
Hi Milan. Thanks. Casting my eye over your patch, it "looks" like it should also fix this issue in general. Great.
Comment 3 Milan Crha 2012-07-26 17:10:36 UTC
OK, thanks. I'm marking this as a duplicate of that bug.

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