Version-Release number of selected component: evolution-data-server-3.5.92-1.fc18 Additional info: libreport version: 2.0.14 abrt_version: 2.0.13 backtrace_rating: 4 cmdline: /usr/libexec/evolution-calendar-factory crash_function: initialize_backend kernel: 3.6.0-1.fc18.x86_64 truncated backtrace: :Thread no. 1 (5 frames) : #6 initialize_backend at e-cal-backend-caldav.c:2652 : #7 caldav_do_open at e-cal-backend-caldav.c:2754 : #8 cal_backend_open at e-cal-backend-sync.c:578 : #9 operation_thread at e-data-cal.c:183 : #11 g_thread_proxy at gthread.c:797
Created attachment 621022 [details] File: core_backtrace
Created attachment 621023 [details] File: environ
Created attachment 621024 [details] File: limits
Created attachment 621025 [details] File: backtrace
Created attachment 621026 [details] File: cgroup
Created attachment 621027 [details] File: maps
Created attachment 621028 [details] File: dso_list
Created attachment 621029 [details] File: open_fds
Created attachment 621030 [details] File: var_log_messages
Thanks for a bug report. I do not see from the backtrace why this crashed, it only shows that there was a memory corruption when opening a CalDAV calendar. Do you recall what you did, like just added a new CalDAV calendar, or was otherwise changing the calendar view or anything like that?
Rebooted after update backtrace_rating: 4 Package: evolution-data-server-3.6.2-2.fc18 OS Release: Fedora release 18 (Spherical Cow)
1. start evolution 2. crash notification shows up backtrace_rating: 4 Package: evolution-data-server-3.6.3-2.fc18 OS Release: Fedora release 18 (Spherical Cow)
*** Bug 964405 has been marked as a duplicate of this bug. ***
Newly installed F19 beta reporter: libreport-2.1.4 backtrace_rating: 4 cmdline: /usr/libexec/evolution-calendar-factory crash_function: initialize_backend executable: /usr/libexec/evolution-calendar-factory kernel: 3.9.4-300.fc19.x86_64 package: evolution-data-server-3.8.2-1.fc19 reason: Process /usr/libexec/evolution-calendar-factory was killed by signal 6 (SIGABRT) runlevel: N 5 uid: 1000
I just saw this after starting 3.8.5 for the first time. I haven't touched the configuration of my CalDAV (Google) calendars for a long time.
Have one personal Google account and one work GoogleApps account configured as gnome online accounts. This crash happens at start up, just after I log in. reporter: libreport-2.1.6 backtrace_rating: 4 cmdline: /usr/libexec/evolution-calendar-factory crash_function: initialize_backend executable: /usr/libexec/evolution-calendar-factory kernel: 3.10.5-201.fc19.x86_64 package: evolution-data-server-3.8.4-1.fc19 reason: Process /usr/libexec/evolution-calendar-factory was killed by signal 6 (SIGABRT) runlevel: N 5 uid: 1000
I dom't know, why this package crashed, because I switched the pc on, but I wasn't logged in. After the login I see the warning, that this package crashed. Thank you! reporter: libreport-2.1.6 backtrace_rating: 4 cmdline: /usr/libexec/evolution-calendar-factory crash_function: initialize_backend executable: /usr/libexec/evolution-calendar-factory kernel: 3.10.9-200.fc19.x86_64 package: evolution-data-server-3.8.5-4.fc19 reason: Process /usr/libexec/evolution-calendar-factory was killed by signal 11 (SIGSEGV) reported_to: uReport: BTHASH=fd1b76661c17f79bf047e4a6a5b97f81e05b9cfd runlevel: N 5 uid: 1000
I Unknow what happend the occur when I was to intented to update of Os. reporter: libreport-2.1.6 backtrace_rating: 4 cmdline: /usr/libexec/evolution-calendar-factory crash_function: initialize_backend executable: /usr/libexec/evolution-calendar-factory kernel: 3.10.10-200.fc19.x86_64 package: evolution-data-server-3.8.5-4.fc19 reason: Process /usr/libexec/evolution-calendar-factory was killed by signal 6 (SIGABRT) reported_to: uReport: BTHASH=446968fae00f140927f4e606b706eac21ab5e402 runlevel: N 5 uid: 1000
Created attachment 797681 [details] evolution-calendar-factory was killed "error" after this update So...are there any updates regarding this bug? Any progress on resolving this issue? I just received the same error after doing an update. Here's the history log of that update:
Unfortunately no progress and no update, I get the crash occasionally too, but whenever I try to debug the cause of the crash the factory doesn't crash. A simple code read doesn't show anything obvious, just the opposite, the code seems to do things right. This has been moved upstream within bug #872652, thus I mark this as a duplicate of it. Any further investigation might be done upstream. *** This bug has been marked as a duplicate of bug 872652 ***