Description of problem: launch mate-system-monitor by hand Version-Release number of selected component: mate-system-monitor-1.5.0-2.fc17 Additional info: libreport version: 2.0.18 abrt_version: 2.0.18 backtrace_rating: 4 cmdline: mate-system-monitor crash_function: g_logv kernel: 3.3.4-5.fc17.x86_64 truncated backtrace: :Thread no. 1 (6 frames) : #0 g_logv at gmessages.h:101 : #2 g_settings_schema_get_value at gsettingsschema.c:640 : #3 g_settings_schema_key_init at gsettingsschema.c:751 : #4 g_settings_get_value at gsettings.c:1079 : #5 g_settings_get_string at gsettings.c:1559 : #6 procman_data_new at procman.cpp:288
Created attachment 663096 [details] File: core_backtrace
Created attachment 663097 [details] File: environ
Created attachment 663098 [details] File: limits
Created attachment 663099 [details] File: backtrace
Created attachment 663100 [details] File: cgroup
Created attachment 663101 [details] File: smolt_data
Created attachment 663102 [details] File: executable
Created attachment 663103 [details] File: maps
Created attachment 663104 [details] File: dso_list
Created attachment 663105 [details] File: proc_pid_status
Created attachment 663106 [details] File: var_log_messages
Created attachment 663107 [details] File: open_fds
Please run yum update *mate* --enablerepo-updates=testing and reopen this bug if you continue to experience this issue.