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 664614 - [abrt] evolution-3.2.1-2.fc16: e_client_utils_open_new: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV
[abrt] evolution-3.2.1-2.fc16: e_client_utils_open_new: Process /usr/bin/evol...
Status: RESOLVED DUPLICATE of bug 663110
Product: evolution
Classification: Applications
Component: Calendar
3.2.x (obsolete)
Other Linux
: Normal critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2011-11-23 07:54 UTC by Milan Crha
Modified: 2014-06-17 14:13 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Milan Crha 2011-11-23 07:54:26 UTC 
Moving this from a downstream bug report:
https://bugzilla.redhat.com/show_bug.cgi?id=755855

libreport version: 2.0.6
abrt_version:   2.0.4.981
backtrace_rating: 4
cmdline:        evolution -c calendar
comment:        unknown, didn't know it did crash
crash_function: e_client_utils_open_new
executable:     /usr/bin/evolution
kernel:         3.1.1-2.fc16.x86_64
reason:         Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
time:           Tue Nov 22 09:24:44 2011

Core was generated by `evolution -c calendar'.
Program terminated with signal 11, Segmentation fault.

+ Trace 229101

Thread 4 (Thread 0x7f9a6ca78700 (LWP 3021))

  • #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 4551
  • #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


Milan Crha





          2014-06-17 14:13:31 UTC
        




*** This bug has been marked as a duplicate of bug 663110 ***