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 755000 - Deleting this event on recurring events: the first time another timezone as in the second time
Deleting this event on recurring events: the first time another timezone as i...
Status: RESOLVED DUPLICATE of bug 754999
Product: evolution
Classification: Applications
Component: Calendar
3.16.x (obsolete)
Other Linux
: Normal normal
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2015-09-14 15:37 UTC by dbet1
Modified: 2015-09-15 16:43 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description dbet1 2015-09-14 15:37:31 UTC 
1. Make a recurring event; recurring eg. daily 3 times
2. Right click the second event, choose Delete this event only
3. Open the first event and edit the recurring rules. The EXDATE is the same time as the recurrent event time
4. Deleted this EXDATE rule
5. Save the event using All instances
6. The previously deleted second event is back of course
7. Right click the second event again, choose Delete this event only
8. Open the first event and edit the recurring rules. The EXDATE is now two hours before the recurring event
9. As a consequence the second (deleted) event is showed in the calendar, which is wrong

It seems that the first time Evolution uses the timezone of the event in the EXDATE, but the second uses UTC in the EXDATE, which is the right thing in my eyes.

Detected with Fedora 22.
Comment 1 Milan Crha 2015-09-15 09:58:04 UTC 
Thanks for a bug report. This might be just a consequence of yours bug #754999. 

Also Fedora 22 doesn't tell anything to most of the users, the important thing is the version of the Evolution, eventually evolution-data-server. You can still have Fedora 22 installed, but different evolution versions there.
Comment 2 Milan Crha 2015-09-15 16:43:21 UTC 
I tried the steps with changes from bug #754999 and I cannot reproduce it with them, thus I consider this fixed by it and mark this bug as a duplicate of the other.

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