Bug 887873

Summary: [abrt] evolution-3.6.2-3.fc18: g_settings_backend_dispatch_signal: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Zeeshan Ali <zeenix>
Component: evolutionAssignee: Matthew Barnes <mbarnes>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 18CC: fedora, lucilanga, mbarnes, mclasen, mcrha, murray.alex
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:5955bce19a775b741ecae27e54552968f9bbaf29
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-01-08 13:37:43 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: smolt_data
none
File: var_log_messages
none
File: xsession_errors none

Description Zeeshan Ali 2012-12-17 14:11:25 UTC 
Version-Release number of selected component:
evolution-3.6.2-3.fc18

Additional info:
backtrace_rating: 4
cmdline:        evolution
crash_function: g_settings_backend_dispatch_signal
executable:     /usr/bin/evolution
kernel:         3.6.10-5.fc18.x86_64
remote_result:  NOTFOUND
uid:            500

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 g_settings_backend_dispatch_signal at gsettingsbackend.c:340
 #1 g_settings_backend_path_changed at gsettingsbackend.c:496
 #2 dconf_engine_change_notify at dconfsettingsbackend.c:246
 #3 dconf_engine_watch_established at dconf-engine.c:735
 #5 dconf_gdbus_method_call_done at dconf-gdbus-thread.c:230
 #6 g_simple_async_result_complete at gsimpleasyncresult.c:775
 #7 g_dbus_connection_call_done at gdbusconnection.c:5339
 #8 g_simple_async_result_complete at gsimpleasyncresult.c:775
 #9 complete_in_idle_cb at gsimpleasyncresult.c:787
 #13 g_main_context_iteration at gmain.c:3351
Comment 1 Zeeshan Ali 2012-12-17 14:11:29 UTC 
Created attachment 664893 [details]
File: backtrace
Comment 2 Zeeshan Ali 2012-12-17 14:11:33 UTC 
Created attachment 664894 [details]
File: cgroup
Comment 3 Zeeshan Ali 2012-12-17 14:11:37 UTC 
Created attachment 664895 [details]
File: core_backtrace
Comment 4 Zeeshan Ali 2012-12-17 14:11:40 UTC 
Created attachment 664896 [details]
File: dso_list
Comment 5 Zeeshan Ali 2012-12-17 14:11:42 UTC 
Created attachment 664897 [details]
File: environ
Comment 6 Zeeshan Ali 2012-12-17 14:11:45 UTC 
Created attachment 664898 [details]
File: limits
Comment 7 Zeeshan Ali 2012-12-17 14:11:48 UTC 
Created attachment 664899 [details]
File: maps
Comment 8 Zeeshan Ali 2012-12-17 14:11:50 UTC 
Created attachment 664900 [details]
File: open_fds
Comment 9 Zeeshan Ali 2012-12-17 14:11:52 UTC 
Created attachment 664901 [details]
File: proc_pid_status
Comment 10 Zeeshan Ali 2012-12-17 14:11:55 UTC 
Created attachment 664902 [details]
File: smolt_data
Comment 11 Zeeshan Ali 2012-12-17 14:11:57 UTC 
Created attachment 664903 [details]
File: var_log_messages
Comment 12 Zeeshan Ali 2012-12-17 14:12:02 UTC 
Created attachment 664904 [details]
File: xsession_errors
Comment 13 Milan Crha 2013-01-07 11:12:58 UTC 
Thanks for a bug report. I see this crashed on evolution start, but it crashed in GSettings code, which may or may not be related to evolution itself. Is this reproducible on your machine? Can it be related to tracker's evolution plugin, which you seem to have installed?
Comment 14 Zeeshan Ali 2013-01-07 14:06:26 UTC 
(In reply to comment #13)
> Thanks for a bug report. I see this crashed on evolution start, but it
> crashed in GSettings code, which may or may not be related to evolution
> itself. Is this reproducible on your machine?

I haven't seen any evolution crashes lately so I'd guess not.

> Can it be related to tracker's
> evolution plugin, which you seem to have installed?

You tell me. :)
Comment 15 Milan Crha 2013-01-08 13:37:43 UTC 
Good it works for you again, bad we didn't find what caused it. I'm closing this for now, but please feel free to reopen, or file a new bug, in case you'd face this again. My idea behind tracker was to remove 3rd party components/plugins, and then check whether evolution on its own can work properly.
Comment 16 Alex Murray 2013-02-10 12:42:34 UTC 
Just saw this exact same crash on F18 Evo 3.6.3...
Comment 17 Christian Stadelmann 2013-03-17 20:51:10 UTC 
Me too, but I can not reproduce it. Evolution crashed one time at startup, then I started gdb and tried to start Evolution and it just started fine.
Using evolution-3.6.3-2.fc18.x86_64