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 674181 - [abrt] Crash in connect_to_server, e_cal_backend_ews_open
[abrt] Crash in connect_to_server, e_cal_backend_ews_open
Status: RESOLVED FIXED
Product: evolution-ews
Classification: Other
Component: Calendar
3.4.x
Other Linux
: Normal critical
: ---
Assigned To: Evolution EWS maintainer(s)
Evolution EWS maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2012-04-16 07:20 UTC by Milan Crha
Modified: 2012-10-30 18:11 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Milan Crha 2012-04-16 07:20:16 UTC
Moving this from a downstream bug report:
https://bugzilla.redhat.com/show_bug.cgi?id=812536

[abrt] evolution-data-server-3.2.3-3.fc16: __GI_raise: Process /usr/libexec/e-calendar-factory was killed by signal 6 (SIGABRT)

libreport version: 2.0.8
abrt_version:   2.0.7
backtrace_rating: 4
cmdline:        /usr/libexec/e-calendar-factory
comment:        Went offline. Chose to synchronise. Went online.
crash_function: __GI_raise
executable:     /usr/libexec/e-calendar-factory
kernel:         3.3.1-5.fc16.x86_64
reason:         Process /usr/libexec/e-calendar-factory was killed by signal 6
(SIGABRT)
time:           2012-04-14T16:52:54 CEST

Core was generated by `/usr/libexec/e-calendar-factory'.
Program terminated with signal 6, Aborted.

Thread 2 (Thread 0x7f3162ee6700 (LWP 4199))

  • #0 read
    at ../sysdeps/unix/syscall-template.S line 82
  • #1 read
    at /usr/include/bits/unistd.h line 45
  • #2 unix_signal_helper_thread
    at gmain.c line 4567
  • #3 g_thread_create_proxy
    at gthread.c line 1962
  • #4 start_thread
    at pthread_create.c line 309
  • #5 clone
    at ../sysdeps/unix/sysv/linux/x86_64/clone.S line 115

Comment 1 Brian J. Murrell 2012-10-27 20:37:24 UTC
I've seen this also.
Comment 2 Milan Crha 2012-10-30 18:11:00 UTC
This might be fixed in 3.6.0+, the code, together with the opening routines, changed significantly.