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 763047 - libecal criticals on startup
libecal criticals on startup
Status: RESOLVED FIXED
Product: gnome-calendar
Classification: Applications
Component: General
3.19.x
Other Linux
: Normal normal
: 3.26
Assigned To: GNOME Calendar maintainers
GNOME Calendar maintainers
: 763660 769828 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2016-03-03 16:00 UTC by Marinus Schraal
Modified: 2017-04-17 18:20 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
gdb output (15.53 KB, text/plain)
2016-03-03 16:00 UTC, Marinus Schraal 		  Details
e-cal-data-model: fix critical due invalid time range (921 bytes, patch)
2016-10-03 22:24 UTC, Georges Basile Stavracas Neto 		committed Details | Review

Description Marinus Schraal 2016-03-03 16:00:31 UTC 
Created attachment 323003 [details]
gdb output

I get a lot of these on startup:

libecal-CRITICAL **: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed

Attached some gdb output. The printed variables are interval_start & _end. Which is odd, since they should return 0 reading icaltime_compare.

Should the interval_{start,end} be 0 to 0 to begin with anyways?
Comment 1 Matthias Clasen 2016-03-15 17:06:26 UTC 
*** Bug 763660 has been marked as a duplicate of this bug. ***
Comment 2 Erick Perez Castellanos 2016-04-07 05:20:23 UTC 
Is this still happening? I can't reproduce it on my jhbuild running on F23.
Comment 3 Christian Stadelmann 2016-04-07 07:33:50 UTC 
Still happening on gnome-calendar-3.20.0-1.fc24.x86_64. Haven't tested jhbuild.
Comment 4 Marinus Schraal 2016-08-13 11:54:53 UTC 
*** Bug 769828 has been marked as a duplicate of this bug. ***
Comment 5 Georges Basile Stavracas Neto 2016-10-03 22:24:13 UTC 
Created attachment 336844 [details] [review]
e-cal-data-model: fix critical due invalid time range

libecal-CRITICAL **: e_cal_recur_generate_instances_sync: assertion
'icaltime_compare (interval_start, interval_end) < 0' failed
Comment 6 Georges Basile Stavracas Neto 2016-10-03 22:27:09 UTC 
Attachment 336844 [details] pushed as c0ed70f - e-cal-data-model: fix critical due invalid time range