Version-Release number of selected component: vinagre-3.10.2-1.fc20 Additional info: reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: vinagre crash_function: g_settings_set_property executable: /usr/bin/vinagre kernel: 3.14.4-200.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #2 g_settings_set_property at gsettings.c:492 #3 object_set_property at gobject.c:1366 #4 g_object_new_internal at gobject.c:1779 #5 g_object_new_valist at gobject.c:2002 #7 g_settings_new at gsettings.c:864 #8 vinagre_prefs_init at vinagre/vinagre-prefs.c:81 #9 g_type_create_instance at gtype.c:1868 #10 g_object_new_internal at gobject.c:1746 #13 vinagre_prefs_get_default at vinagre/vinagre-prefs.c:58 #14 vinagre_prefs_get_default_gsettings at vinagre/vinagre-prefs.c:71
Created attachment 900145 [details] File: backtrace
Created attachment 900146 [details] File: cgroup
Created attachment 900147 [details] File: core_backtrace
Created attachment 900148 [details] File: dso_list
Created attachment 900149 [details] File: environ
Created attachment 900150 [details] File: limits
Created attachment 900151 [details] File: maps
Created attachment 900152 [details] File: open_fds
Created attachment 900153 [details] File: proc_pid_status
Created attachment 900154 [details] File: var_log_messages
The timestamps on the log messages show that yum had not finished installing the vinagre package (and calling glib-compile-schemas to build the GSettings schema binarcy cache) when it was first launched. The next launch worked without a crash, so please wait for the package installation to finish before running vinagre in future.