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
Created attachment 664893 [details] File: backtrace
Created attachment 664894 [details] File: cgroup
Created attachment 664895 [details] File: core_backtrace
Created attachment 664896 [details] File: dso_list
Created attachment 664897 [details] File: environ
Created attachment 664898 [details] File: limits
Created attachment 664899 [details] File: maps
Created attachment 664900 [details] File: open_fds
Created attachment 664901 [details] File: proc_pid_status
Created attachment 664902 [details] File: smolt_data
Created attachment 664903 [details] File: var_log_messages
Created attachment 664904 [details] File: xsession_errors
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?
(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. :)
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.
Just saw this exact same crash on F18 Evo 3.6.3...
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