Description of problem: Installed a fresh F19 VM (GNOME install from netinst ISO), updated with updates-testing enabled, configured my Owncloud and IMAP accounts *via GOA*, launched Evolution (not sure if that matters or if it would've happened anyway as soon as I set up the Owncloud account and it just took a while to trigger). Version-Release number of selected component: gnome-shell-3.8.4-3.fc19 Additional info: reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: /usr/libexec/gnome-shell-calendar-server crash_function: icaltimezone_load_builtin_timezone executable: /usr/libexec/gnome-shell-calendar-server kernel: 3.14.5-100.fc19.x86_64 runlevel: N 5 type: CCpp uid: 1000 var_log_messages: Jun 5 14:33:51 localhost abrt-hook-ccpp[2649]: Saved core dump of pid 1535 (/usr/libexec/gnome-shell-calendar-server) to /var/tmp/abrt/ccpp-2014-06-05-14:33:51-1535 (49668096 bytes) Truncated backtrace: Thread no. 1 (10 frames) #0 icaltimezone_load_builtin_timezone at icaltimezone.c:1766 #1 icaltimezone_get_tzid at icaltimezone.c:1156 #2 copy_timezone at e-cal-client.c:1795 #3 e_cal_client_set_default_timezone at e-cal-client.c:1841 #4 app_load_events at calendar-server/gnome-shell-calendar-server.c:642 #5 on_appointment_sources_changed at calendar-server/gnome-shell-calendar-server.c:743 #6 _g_closure_invoke_va at gclosure.c:840 #9 calendar_sources_registry_source_changed_cb at calendar-server/calendar-sources.c:440 #10 g_cclosure_marshal_VOID__OBJECTv at gmarshal.c:1312 #11 _g_closure_invoke_va at gclosure.c:840 Potential duplicate: bug 842223
Created attachment 902680 [details] File: backtrace
Created attachment 902681 [details] File: cgroup
Created attachment 902682 [details] File: core_backtrace
Created attachment 902683 [details] File: dso_list
Created attachment 902684 [details] File: environ
Created attachment 902685 [details] File: exploitable
Created attachment 902686 [details] File: limits
Created attachment 902687 [details] File: maps
Created attachment 902688 [details] File: open_fds
Created attachment 902689 [details] File: proc_pid_status
Another user experienced a similar problem: Fresh F19 VM, update with updates-testing, set up OwnCloud account (with calendar) via GOA, run Evolution (not sure if that part matters). reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: /usr/libexec/gnome-shell-calendar-server crash_function: icaltimezone_load_builtin_timezone executable: /usr/libexec/gnome-shell-calendar-server kernel: 3.14.5-100.fc19.x86_64 package: gnome-shell-3.8.4-3.fc19 reason: gnome-shell-calendar-server killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
This crash seems to be happening quite regularly in the test VM - up to 7 occurrences now, with it just sitting there for an hour or so.
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.