Version-Release number of selected component: gnome-shell-3.5.91-1.fc18 Additional info: libreport version: 2.0.13 abrt_version: 2.0.12 backtrace_rating: 4 cmdline: /usr/libexec/gnome-shell-calendar-server crash_function: app_load_events kernel: 3.3.4-5.fc17.x86_64 truncated backtrace: :Thread no. 1 (10 frames) : #0 app_load_events at calendar-server/gnome-shell-calendar-server.c : #1 _g_closure_invoke_va at gclosure.c : #4 calendar_sources_registry_source_removed_cb at calendar-server/calendar-sources.c : #5 g_cclosure_marshal_VOID__OBJECTv at gmarshal.c : #6 _g_closure_invoke_va at gclosure.c : #9 source_registry_remove_source at e-source-registry.c : #10 source_registry_object_removed_idle_cb at e-source-registry.c : #14 g_main_context_iteration at gmain.c : #15 e_gdbus_proxy_call_sync at e-gdbus-templates.c : #16 e_gdbus_proxy_call_sync_boolean__void at e-gdbus-templates.c
Created attachment 612754 [details] File: core_backtrace
Created attachment 612755 [details] File: environ
Created attachment 612756 [details] File: backtrace
Created attachment 612757 [details] File: limits
Created attachment 612758 [details] File: cgroup
Created attachment 612760 [details] File: maps
Created attachment 612761 [details] File: dso_list
Created attachment 612762 [details] File: var_log_messages
Created attachment 612763 [details] File: open_fds
Caused by /usr/libexec/evolution-calendar-factory process exiting. backtrace_rating: 4 Package: gnome-shell-3.5.91-1.fc18 OS Release: Fedora release 18 (Spherical Cow)
Evolution was shut down (using IMAP+ and Exchange EWS). I wanted to give it a complete clean restart. Te following happened: [louis@localhost ~]$ /usr/libexec/evolution/3.6/killev Could not find Evolution's process ID [louis@localhost ~]$ ps ax | grep evo 1349 ? Sl 0:02 /usr/libexec/evolution/3.6/evolution-alarm-notify 1458 ? SLl 0:02 /usr/libexec/evolution-source-registry 1473 ? Sl 0:01 /usr/libexec/evolution-calendar-factory 1521 ? Sl 0:00 /usr/libexec/evolution-addressbook-factory 4932 pts/0 S+ 0:00 grep --color=auto evo [louis@localhost ~]$ pkill evolution [louis@localhost ~]$ ps ax | grep evo 4935 ? Sl 0:00 /usr/libexec/evolution-calendar-factory 4941 ? SLl 0:00 /usr/libexec/evolution-source-registry 4950 pts/0 S+ 0:00 grep --color=auto evo [louis@localhost ~]$ pkill evolution [louis@localhost ~]$ ps ax | grep evo 4960 ? Sl 0:00 /usr/libexec/evolution-calendar-factory 4966 ? SLl 0:00 /usr/libexec/evolution-source-registry 4991 pts/0 S+ 0:00 grep --color=auto evo [louis@localhost ~]$ kill 4960 [louis@localhost ~]$ kill 4966 [louis@localhost ~]$ ps ax | grep evo 5012 ? Sl 0:00 /usr/libexec/evolution-calendar-factory 5018 ? SLl 0:00 /usr/libexec/evolution-source-registry 5030 pts/0 S+ 0:00 grep --color=auto evo [louis@localhost ~]$ ps ax | grep evo 5012 ? Sl 0:00 /usr/libexec/evolution-calendar-factory 5018 ? SLl 0:00 /usr/libexec/evolution-source-registry 5047 pts/0 S+ 0:00 grep --color=auto evo [louis@localhost ~]$ After the last 'ps' the ABRT occurred. I did find that the evolution-calendar-factory DID quit after the ABRT crash happened. backtrace_rating: 4 Package: gnome-shell-3.6.1-2.fc18 OS Release: Fedora release 18 (Spherical Cow)
I tried to import a evolution archive in Evolution, but I don't really if it is related to this. The import of evolution archives seems to be broken in Evolution. backtrace_rating: 4 Package: gnome-shell-3.6.2-2.fc18 OS Release: Fedora release 18 (Spherical Cow)
no idea backtrace_rating: 4 Package: gnome-shell-3.6.2-2.fc18 OS Release: Fedora release 18 (Spherical Cow)
I cancelled the Google account authentication dialog. backtrace_rating: 4 Package: gnome-shell-3.6.2-6.fc18 OS Release: Fedora release 18 (Spherical Cow)
Evolution hangs on exit (using the File pulldown menu and selecting Exit). This seesm to occur reliably these days. The crash occurs when I issue 'evolution --force-shutdown' from a terminal.
Same problem as for Matthew Saltzman.
(In reply to Wolfgang Pirker from comment #12) > I tried to import a evolution archive in Evolution, but I don't really if it > is related to this. > The import of evolution archives seems to be broken in Evolution. > > > backtrace_rating: 4 > Package: gnome-shell-3.6.2-2.fc18 > OS Release: Fedora release 18 (Spherical Cow) Happened to me when restoring Evolution data from a backup. gnome-shell-3.6.3.1-1.fc18
I get this regularly whe evolution hangs with a number of unkillable "Unknown background process" in the status bar. I get this crash report when I force-shutdown.
buyg reporter: libreport-2.1.7 backtrace_rating: 4 cmdline: /usr/libexec/gnome-shell-calendar-server crash_function: app_load_events executable: /usr/libexec/gnome-shell-calendar-server kernel: 3.10.14-100.fc18.x86_64 package: gnome-shell-3.6.3.1-2.fc18 reason: Process /usr/libexec/gnome-shell-calendar-server was killed by signal 11 (SIGSEGV) runlevel: N 5 type: CCpp uid: 1000
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '18'. 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 prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 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 to Fedora 18's end of life. 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 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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.