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 499174 - Evolution does not display vEvents with RDATE
Evolution does not display vEvents with RDATE
Status: RESOLVED FIXED
Product: evolution
Classification: Applications
Component: Calendar
3.2.x (obsolete)
Other All
: Normal normal
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
: 542593 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2007-11-23 13:27 UTC by Stefan
Modified: 2017-08-25 09:22 UTC
See Also:
GNOME target: ---
GNOME version: 3.1/3.2



Description Stefan 2007-11-23 13:27:03 UTC
Please describe the problem:
if a remote iCalendar file contains an event which contains and RDATE line, the event is not displayed at all.

Steps to reproduce:
1. create an iCalendar file on a server which contains at least the following event:

BEGIN:VEVENT
UID:789846-4792384-423-abc
SUMMARY:RDATE test event
DTSTART:20071201T140000
DURATION:PT2H
LOCATION: test site
RDATE:20071202T140000
END:VEVENT

2. add the file to the list of calendars

3. wait


Actual results:
Nothing

Expected results:
The event should show up on 01-Dec and 02-Dec

Does this happen every time?
Yes

Other information:
Comment 1 Johnny Jacob 2008-06-19 19:00:32 UTC
CCing Chen here. 
Comment 2 Johnny Jacob 2008-06-19 19:04:18 UTC
Looks like bug 499180 is on the same lines.
Comment 3 Andrew 2008-07-11 22:23:37 UTC
*** Bug 542593 has been marked as a duplicate of this bug. ***
Comment 4 André Klapper 2012-02-10 22:08:00 UTC
Still valid in 3.2.3 with

BEGIN:VCALENDAR
BEGIN:VEVENT
UID:789846-4792384-423-abc
SUMMARY:RDATE test event
DTSTART:20071201T140000
DURATION:PT2H
LOCATION: test site
RDATE:20071202T140000
END:VEVENT
END:VCALENDAR
Comment 5 rhi 2015-10-01 13:38:20 UTC
Still not working with 3.16.5
Comment 6 Milan Crha 2017-08-25 09:22:04 UTC
I tested this with the current development version (3.25.91) and I see the event on the first and on the second of December 2007. Thus it seems to be fixed. I guess a similar experience will be with 3.22 and maybe even 3.20, but I didn't try it with those.