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 673519 - [abrt] evolution-3.4.0.1-1.fc17: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
[abrt] evolution-3.4.0.1-1.fc17: Process /usr/bin/evolution was killed by sig...
Status: RESOLVED OBSOLETE
Product: dconf
Classification: Core
Component: gsettings backend
0.12.x
Other Linux
: Normal critical
: ---
Assigned To: dconf-maint
dconf-maint
Depends on:
Blocks:
 
 
Reported: 2012-04-04 16:32 UTC by Milan Crha
Modified: 2013-01-24 17:09 UTC
See Also:
GNOME target: ---
GNOME version: ---


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

libreport version: 2.0.10
abrt_version:   2.0.9
backtrace_rating: 4
cmdline:        evolution
comment:        Started evolution 3.4.0 after an upgrade from Fedora 16 / 3.2.x
to Fedora 17. Two accounts configured: evw connecting to Exchange and google
for calendar (via gnome-online-accounts).
crash_function: g_settings_backend_dispatch_signal
executable:     /usr/bin/evolution
kernel:         3.3.0-8.fc17.x86_64
time:           Mon 02 Apr 2012 15:40:18 BST

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

+ Trace 230010

Thread 1 (Thread 0x7f95b1bc2700 (LWP 1923))

  • #0 g_settings_backend_dispatch_signal
    at gsettingsbackend.c line 340
  • #1 g_settings_backend_path_changed
    at gsettingsbackend.c line 496
  • #2 add_match_done
    at dconfsettingsbackend.c line 597
  • #3 g_simple_async_result_complete
    at gsimpleasyncresult.c line 767
  • #4 g_dbus_connection_call_done
    at gdbusconnection.c line 5289
  • #5 g_simple_async_result_complete
    at gsimpleasyncresult.c line 767
  • #6 complete_in_idle_cb
    at gsimpleasyncresult.c line 779
  • #7 g_main_dispatch
    at gmain.c line 2515
  • #8 g_main_context_dispatch
    at gmain.c line 3052
  • #9 g_main_context_iterate
    at gmain.c line 3123
  • #10 g_main_loop_run
    at gmain.c line 3317
  • #11 dconf_context_thread
    at dconfcontext.c line 11
  • #12 g_thread_proxy
    at gthread.c line 801
  • #13 start_thread
    at pthread_create.c line 309
  • #14 clone
    at ../sysdeps/unix/sysv/linux/x86_64/clone.S line 115 






Comment 1


Allison Karlitskaya (desrt)





          2013-01-24 17:09:24 UTC
        



This codepath through dconf was recently rewritten.  I doubt the original bug remains.  If so, it's probably not a dconf bug.