Version-Release number of selected component: gnome-calendar-3.16.2-1.fc22 Additional info: reporter: libreport-2.6.0 backtrace_rating: 4 cmdline: /usr/bin/gnome-calendar --gapplication-service crash_function: icaltimezone_compare_change_fn executable: /usr/bin/gnome-calendar global_pid: 5133 kernel: 4.0.6-300.fc22.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 icaltimezone_compare_change_fn at /usr/src/debug/libical-1.0.1/src/libical/icaltimezone.c:756 #1 icaltimezone_find_nearby_change at /usr/src/debug/libical-1.0.1/src/libical/icaltimezone.c:1101 #2 icaltimezone_get_utc_offset at /usr/src/debug/libical-1.0.1/src/libical/icaltimezone.c:868 #3 icaltimezone_convert_time at /usr/src/debug/libical-1.0.1/src/libical/icaltimezone.c:807 #4 icaltime_as_timet_with_zone at /usr/src/debug/libical-1.0.1/src/libical/icaltime.c:323 #5 e_cal_recur_generate_instances_of_rule at e-cal-recur.c:764 #6 e_cal_recur_generate_instances at e-cal-recur.c:639 #7 generate_instances at e-cal-client.c:2659 #8 e_cal_client_generate_instances_for_object_sync at e-cal-client.c:3314 #9 cal_data_model_expand_recurrences_thread at e-cal-data-model.c:1148
Created attachment 1046206 [details] File: backtrace
Created attachment 1046207 [details] File: cgroup
Created attachment 1046208 [details] File: core_backtrace
Created attachment 1046209 [details] File: dso_list
Created attachment 1046210 [details] File: environ
Created attachment 1046211 [details] File: limits
Created attachment 1046212 [details] File: maps
Created attachment 1046213 [details] File: mountinfo
Created attachment 1046214 [details] File: namespaces
Created attachment 1046215 [details] File: open_fds
Created attachment 1046216 [details] File: proc_pid_status
Looks like some memory corrupted in thred (not sure). stm = {tm_sec = 0, tm_min = 0, tm_hour = 0, tm_mday = 1, tm_mon = 0, tm_year = 0, tm_wday = 0, tm_yday = 0, tm_isdst = 36984752, tm_gmtoff = 139899971561937, tm_zone = 0xc000007b6 <error: Cannot access memory at address 0xc000007b6>} Are you able to reproduce this?
(In reply to Igor Gnatenko from comment #12) > Looks like some memory corrupted in thred (not sure). > stm = {tm_sec = 0, tm_min = 0, tm_hour = 0, tm_mday = 1, tm_mon = 0, tm_year > = 0, tm_wday = 0, tm_yday = 0, tm_isdst = 36984752, tm_gmtoff = > 139899971561937, tm_zone = 0xc000007b6 <error: Cannot access memory at > address 0xc000007b6>} > > Are you able to reproduce this? I don't know how to reproduce this error.
Old bug, if still reproducible - please reopen.
Still reproducible. I can't reopen it, but I've reported a new one in bug #1409398. Is it possible that this bug is related to leap seconds? This bug happened after the leap second on 2015-06-31. My crasher (bug #1409398) happened on 2017-01-01, one day after the leap second introduced on 2016-12-31. See also: https://en.wikipedia.org/wiki/Leap_second