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 742507 - random crash (SIGSEGV) while reading mail
random crash (SIGSEGV) while reading mail
Status: RESOLVED DUPLICATE of bug 741434
Product: evolution
Classification: Applications
Component: Mailer
3.12.x (obsolete)
Other Linux
: Normal normal
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2015-01-07 05:37 UTC by Paul Wise
Modified: 2015-01-07 15:00 UTC
See Also:
GNOME target: ---
GNOME version: 3.13/3.14


Description Paul Wise 2015-01-07 05:37:47 UTC 
I got a random crash while reading mail. If the backtrace below isn't useful, please close this bug.

I'm using evolution 3.12.9~git20141130.241663-1 and evolution-data-server 3.12.9~git20141128.5242b0-2 on Debian jessie, architecture amd64.

$ gdb -batch -n -ex bt -ex 'thread apply all bt full' --core /var/crash/1000/31065-1000-1000-11-1420606532-chianamo--usr-bin-evolution.core /usr/bin/evolution
[New LWP 21981]
[New LWP 31070]
[New LWP 31073]
[New LWP 31068]
[New LWP 31091]
[New LWP 31093]
[New LWP 31072]
[New LWP 31069]
[New LWP 31090]
[New LWP 31092]
[New LWP 31142]
[New LWP 32069]
[New LWP 31071]
[New LWP 31065]
[New LWP 358]
[New LWP 21974]
[New LWP 32257]
[New LWP 15531]
[New LWP 15533]
[New LWP 21979]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `evolution'.
Program terminated with signal SIGSEGV, Segmentation fault.

+ Trace 234517

Thread 16 (Thread 0x7f29537fe700 (LWP 21974))

  • #0 syscall
    at ../sysdeps/unix/sysv/linux/x86_64/syscall.S line 38
  • #1 g_cond_wait_until
    at /tmp/buildd/glib2.0-2.42.1/./glib/gthread-posix.c line 1443
  • #2 g_async_queue_pop_intern_unlocked
    at /tmp/buildd/glib2.0-2.42.1/./glib/gasyncqueue.c line 422
  • #3 g_async_queue_timeout_pop
    at /tmp/buildd/glib2.0-2.42.1/./glib/gasyncqueue.c line 543
  • #4 g_thread_pool_wait_for_new_pool
    at /tmp/buildd/glib2.0-2.42.1/./glib/gthreadpool.c line 167
  • #5 g_thread_pool_thread_proxy
    at /tmp/buildd/glib2.0-2.42.1/./glib/gthreadpool.c line 364
  • #6 g_thread_proxy
    at /tmp/buildd/glib2.0-2.42.1/./glib/gthread.c line 764
  • #7 start_thread
    at pthread_create.c line 309
  • #8 clone
    at ../sysdeps/unix/sysv/linux/x86_64/clone.S line 111

Thread 1 (Thread 0x7f2972ffd700 (LWP 21981))

  • #0 g_type_check_instance_is_fundamentally_a
    at /tmp/buildd/glib2.0-2.42.1/./gobject/gtype.c line 3982
  • #1 g_object_unref
    at /tmp/buildd/glib2.0-2.42.1/./gobject/gobject.c line 3067
  • #2 gpg_verify_sync
    at camel-gpg-context.c line 1958
  • #3 camel_cipher_context_verify_sync
    at camel-cipher-context.c line 493
  • #4 empe_mp_signed_parse
    at e-mail-parser-multipart-signed.c line 129
  • #5 e_mail_parser_parse_part_as
    at e-mail-parser.c line 563
  • #6 empe_message_parse
    at e-mail-parser-message.c line 91
  • #7 mail_parser_run
    at e-mail-parser.c line 127
  • #8 e_mail_parser_parse_sync
    at e-mail-parser.c line 349
  • #9 mail_reader_parse_message_run
    at e-mail-reader-utils.c line 2374
  • #10 run_in_thread
    at /tmp/buildd/glib2.0-2.42.1/./gio/gsimpleasyncresult.c line 858
  • #11 io_job_thread
    at /tmp/buildd/glib2.0-2.42.1/./gio/gioscheduler.c line 85
  • #12 g_task_thread_pool_thread
    at /tmp/buildd/glib2.0-2.42.1/./gio/gtask.c line 1215
  • #13 g_thread_pool_thread_proxy
    at /tmp/buildd/glib2.0-2.42.1/./glib/gthreadpool.c line 307
  • #14 g_thread_proxy
    at /tmp/buildd/glib2.0-2.42.1/./glib/gthread.c line 764
  • #15 start_thread
    at pthread_create.c line 309
  • #16 clone
    at ../sysdeps/unix/sysv/linux/x86_64/clone.S line 111 






Comment 1


Milan Crha





          2015-01-07 15:00:35 UTC
        



Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.

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