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 578703 - Evolution sometimes fails to load some calendar events
Evolution sometimes fails to load some calendar events
Status: RESOLVED DUPLICATE of bug 580724
Product: evolution
Classification: Applications
Component: Calendar
2.24.x (obsolete)
Other All
: Normal normal
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2009-04-11 14:43 UTC by John Haiducek
Modified: 2009-05-25 21:41 UTC
See Also:
GNOME target: ---
GNOME version: 2.23/2.24



Description John Haiducek 2009-04-11 14:43:35 UTC
Please describe the problem:
Evolution sometimes loads all my calendar events (stored on a caldav server), but sometimes it only loads some of them. Which ones it loads or doesn't load seems to vary randomly.

Steps to reproduce:
1. Connect to a caldav calendar
2. Leave the calendar pane
3. Go back to the calendar pane


Actual results:
Sometimes all the events load, sometimes just some of them load. 

Expected results:
All the events should load every time.

Does this happen every time?
No, it happens frequently but not always. Looks like a possible race condition between evolution and evolution-data-server.

Other information:
Recurring events load in their entirety or not at all. In other words, if a recurring event loads, all of its recurrences load.
Comment 1 Milan Crha 2009-04-27 16:56:14 UTC
That's because of "backend busy" error in the time of instances creation of the recurring event. I noticed and mention in bug #353012 though it's quite old and this particular issue is new, since rewrite in bug #347287. This is not CalDAV specific thing, with a bit of luck one is able to reproduce even on a local calendar.

I was told that eds-dbus rewrite should help here. Am I right, Chen?
Comment 2 Chenthill P 2009-04-28 10:20:23 UTC
If its due to 'Backend busy' error, yes eds-dbus port would fix it.
Comment 3 Milan Crha 2009-05-25 21:41:24 UTC
There is a patch for this in bug #580724, thus marking as a duplicate. Please reopen if I'm wrong. Thanks.

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