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 627358 - SEGV on replying to message
SEGV on replying to message
Status: RESOLVED FIXED
Product: evolution-data-server
Classification: Platform
Component: Mailer
2.32.x (obsolete)
Other Linux
: Normal normal
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2010-08-19 13:20 UTC by David Woodhouse
Modified: 2013-09-14 16:54 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description David Woodhouse 2010-08-19 13:20:15 UTC 
Program received signal SIGSEGV, Segmentation fault.

+ Trace 223305

Thread 140734017521424 (LWP 31762)

  • #0 g_slist_reverse
    from /lib64/libglib-2.0.so.0
  • #1 gconf_value_copy
    from /usr/lib64/libgconf-2.so.4
  • #2 gconf_entry_new
    from /usr/lib64/libgconf-2.so.4
  • #3 gconf_entry_copy
    from /usr/lib64/libgconf-2.so.4
  • #4 ??
    from /usr/lib64/libgconf-2.so.4
  • #5 ??
    from /usr/lib64/libgconf-2.so.4
  • #6 gconf_client_get_list
    from /usr/lib64/libgconf-2.so.4
  • #7 load_from_gconf
    at e-source-list.c line 73
  • #8 e_source_list_new_for_gconf
    at e-source-list.c line 368
  • #9 e_book_get_addressbooks
    at e-book.c line 2990
  • #10 load_books_thread
    at e-name-selector.c line 81
  • #11 ??
    from /lib64/libglib-2.0.so.0
  • #12 start_thread
    at pthread_create.c line 301
  • #13 clone
    at ../sysdeps/unix/sysv/linux/x86_64/clone.S line 115 






Comment 1


Matthew Barnes





          2010-08-19 14:49:06 UTC
        



Looks like another case of accessing GConf from a non-mainloop thread even though GConf is known to not be thread-safe.  I killed off load_books_thread() in ENameSelector yesterday (it's all asynchronous now), which should prevent this crash.

Closing as (presumed) FIXED, but please do reopen this if you encounter it again.