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 596860 - [regression] Duplicate event gets shown in calendar view
[regression] Duplicate event gets shown in calendar view
Status: RESOLVED FIXED
Product: evolution
Classification: Applications
Component: Calendar
2.30.x (obsolete)
Other Linux
: Normal normal
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
evolution[kill-bonobo]
: 597778 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2009-09-30 12:02 UTC by Akhil Laddha
Modified: 2013-09-13 01:07 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
proposed evo patch (1.10 KB, patch)
2009-10-09 13:43 UTC, Milan Crha
committed Details | Review

Description Akhil Laddha 2009-09-30 12:02:35 UTC
Evolution 2.29.1 

If i create any appointment, calendar view shows two instances of same event. Duplicate event will go away after evolution restart.
Comment 1 Akhil Laddha 2009-10-08 09:23:04 UTC
*** Bug 597778 has been marked as a duplicate of this bug. ***
Comment 2 Milan Crha 2009-10-08 17:09:54 UTC
I'm looking on this. So far I created only a commit 0fcfd40 in eds master with a full list of possible errors returned from EDataCal/EDataBook and/or backends. And a litle change in e_cal_create_object to allow also NULL and 'uid' parameter.
Comment 3 Milan Crha 2009-10-09 13:43:56 UTC
Created attachment 145130 [details] [review]
proposed evo patch

for evolution;

ej, this was tough, it's there since fix for a bug #594534, which just uncovered this bug.

Matt, did you intentionally change a logic of the default source in a calendar? I know what it should do, but I do not know whether you did there some logic change.
The ideal thing should be to never do query on a default calendar, as it's in ECalModel twice, once as an opened calendar, the second time as a default calendar. Unfortunately as two pointers. I fixed the place where this one was seen and added a runtime warning when something similar happens again, but I've a feeling this patch isn't complete. There are couple other possibilities how to solve this.
Comment 4 Milan Crha 2009-10-16 09:39:07 UTC
Created commit 14c68f8 in evo master (2.29.1+) as an interim solution, because the release is just behind the corner and this might users notice for sure.
Comment 5 Milan Crha 2009-11-13 12:32:05 UTC
(In reply to comment #3)
> I fixed the place where this one was
> seen and added a runtime warning when something similar happens again, but I've
> a feeling this patch isn't complete. There are couple other possibilities how
> to solve this.

Maybe some other bug, if any. I'm closing this one, as no duplicate events so far for me.