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 661355 - [abrt] evolution-3.2.0-1.fc16: strncpy: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
[abrt] evolution-3.2.0-1.fc16: strncpy: Process /usr/bin/evolution was killed...
Status: RESOLVED DUPLICATE of bug 662643
Product: evolution-data-server
Classification: Platform
Component: Mailer
3.2.x (obsolete)
Other Linux
: Normal critical
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2011-10-10 07:05 UTC by Milan Crha
Modified: 2011-11-08 15:56 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Milan Crha 2011-10-10 07:05:05 UTC 
Moving this from a downstream bug report:
https://bugzilla.redhat.com/show_bug.cgi?id=744626

libreport version: 2.0.6
abrt_version:   2.0.4.981
backtrace_rating: 4
cmdline:        evolution -c calendar
comment:        Evolution crash when I access the mailer component
crash_function: strncpy
executable:     /usr/bin/evolution
kernel:         3.1.0-0.rc8.git0.1.fc16.x86_64
reason:         Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
time:           Sun Oct  9 19:59:43 2011

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

+ Trace 228737

Thread 9 (Thread 0x7fd06a025700 (LWP 13009))

  • #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 305
  • #5 clone
    at ../sysdeps/unix/sysv/linux/x86_64/clone.S line 115 






Comment 1


Matthew Barnes





          2011-11-08 15:56:21 UTC
        




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