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 238394 - Evolution Calendar dos not conform to the iCalendar RFC-2445
Evolution Calendar dos not conform to the iCalendar RFC-2445
Status: RESOLVED DUPLICATE of bug 223606
Product: evolution
Classification: Applications
Component: Calendar
unspecified
Other All
: Normal major
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2003-02-20 13:43 UTC by Troels Blum
Modified: 2003-05-26 07:43 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Troels Blum 2003-02-20 13:43:34 UTC
Package: Evolution
Priority: Major
Version: 1.2.1
Synopsis: Evolution Calendar dos not conform to the iCalendar RFC-2445
Bugzilla-Product: Evolution
Bugzilla-Component: Calendar

Description:
Description of Problem:
Evolution Calendar crashes with a segmentation fault when opening an
event without an end date (DTEND).

Steps to reproduce the problem:
1.
Import an icf file with a VEVENT without a DTEND tag. example:
BEGIN:VCALENDAR
CALSCALE:GREGORIAN
PRODID:BLUM-HOLLYDAY-MARKER
VERSION:2.0
BEGIN:VEVENT
UID:20030220T121747Z-3366-217@www.blum.dk
DTSTAMP:20030220T121747Z
SUMMARY:Juledag
DTSTART;VALUE=DATE:20031225
RRULE:FREQ=YEARLY
END:VEVENT
END:VCALENDAR
2.
Open the event (by double clicking or choose open)
3.
Segmentation fault

Expected Results:
That the event is opend for editing.

How often does this happen?
Every time.

Additional Information:
According RFC-2445 http://www.ietf.org/rfc/rfc2445.txt this is a leagle
VEVENT.
I qoute:
Section 4.8.2.4 Date/Time Start (Page 93)
"   Description: Within the "VEVENT" calendar component, this property
   defines the start date and time for the event. The property is
   REQUIRED in "VEVENT" calendar components. Events can have a start
   date/time but no end date/time. In that case, the event does not
take
   up any time."

Section 6. Recommended Practices (Page 140)
"   2.  A calendar entry with a "DTSTART" property but no "DTEND"
       property does not take up any time. It is intended to represent
       an event that is associated with a given calendar date and time
       of day, such as an anniversary. Since the event does not take up
       any time, it MUST NOT be used to record busy time no matter what
       the value for the "TRANSP" property."



Unknown reporter: troels@blum.dk, changed to bugbuddy-import@ximian.com.
Setting qa contact to the default for this product.
   This bug either had no qa contact or an invalid one.

Comment 1 jack jia 2003-05-26 07:43:36 UTC
Please try the 1.2.2 or later version.

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