Bug 1005274 - [abrt] mate-control-center-1.6.1-2.fc19: g_settings_set_property: Process /usr/bin/mate-display-properties was killed by signal 5 (SIGTRAP)
Summary: [abrt] mate-control-center-1.6.1-2.fc19: g_settings_set_property: Process /us...
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: mate-control-center
Version: 19
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Dan Mashal
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:f9e732fd2193b0e5c73ff4d198d...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-09-06 14:45 UTC by Steve Carl
Modified: 2013-10-03 14:02 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-10-03 14:02:09 UTC
Type: ---


Attachments (Terms of Use)
File: backtrace (24.48 KB, text/plain)
2013-09-06 14:45 UTC, Steve Carl
no flags Details
File: cgroup (141 bytes, text/plain)
2013-09-06 14:45 UTC, Steve Carl
no flags Details
File: core_backtrace (3.10 KB, text/plain)
2013-09-06 14:46 UTC, Steve Carl
no flags Details
File: dso_list (7.86 KB, text/plain)
2013-09-06 14:46 UTC, Steve Carl
no flags Details
File: environ (1.19 KB, text/plain)
2013-09-06 14:46 UTC, Steve Carl
no flags Details
File: limits (1.29 KB, text/plain)
2013-09-06 14:46 UTC, Steve Carl
no flags Details
File: maps (41.61 KB, text/plain)
2013-09-06 14:46 UTC, Steve Carl
no flags Details
File: open_fds (226 bytes, text/plain)
2013-09-06 14:46 UTC, Steve Carl
no flags Details
File: proc_pid_status (947 bytes, text/plain)
2013-09-06 14:46 UTC, Steve Carl
no flags Details
File: var_log_messages (345 bytes, text/plain)
2013-09-06 14:46 UTC, Steve Carl
no flags Details

Description Steve Carl 2013-09-06 14:45:46 UTC
Description of problem:
- Installed MATE with YUM
- logged into MATE desktop
- CLick on 'Display' to re-setup the multi-monitor config
-Crash

Version-Release number of selected component:
mate-control-center-1.6.1-2.fc19

Additional info:
reporter:       libreport-2.1.6
backtrace_rating: 4
cmdline:        mate-display-properties
crash_function: g_settings_set_property
executable:     /usr/bin/mate-display-properties
kernel:         3.10.10-200.fc19.x86_64
runlevel:       N 5
uid:            1000

Truncated backtrace:
Thread no. 1 (6 frames)
 #2 g_settings_set_property at gsettings.c:492
 #3 object_set_property at gobject.c:1358
 #4 g_object_constructor at gobject.c:1869
 #6 g_object_new_valist at gobject.c:1836
 #8 g_settings_new at gsettings.c:869
 #9 run_application at xrandr-capplet.c:2429

Potential duplicate: bug 896678

Comment 1 Steve Carl 2013-09-06 14:45:53 UTC
Created attachment 794786 [details]
File: backtrace

Comment 2 Steve Carl 2013-09-06 14:45:56 UTC
Created attachment 794787 [details]
File: cgroup

Comment 3 Steve Carl 2013-09-06 14:46:01 UTC
Created attachment 794788 [details]
File: core_backtrace

Comment 4 Steve Carl 2013-09-06 14:46:05 UTC
Created attachment 794789 [details]
File: dso_list

Comment 5 Steve Carl 2013-09-06 14:46:09 UTC
Created attachment 794790 [details]
File: environ

Comment 6 Steve Carl 2013-09-06 14:46:12 UTC
Created attachment 794791 [details]
File: limits

Comment 7 Steve Carl 2013-09-06 14:46:23 UTC
Created attachment 794792 [details]
File: maps

Comment 8 Steve Carl 2013-09-06 14:46:27 UTC
Created attachment 794793 [details]
File: open_fds

Comment 9 Steve Carl 2013-09-06 14:46:30 UTC
Created attachment 794794 [details]
File: proc_pid_status

Comment 10 Steve Carl 2013-09-06 14:46:33 UTC
Created attachment 794795 [details]
File: var_log_messages

Comment 11 Wolfgang Ulbrich 2013-09-06 18:29:13 UTC
Thanks for reporting this issue.

msg = 0x225cd00 "Settings schema 'org.mate.SettingsDaemon.plugins.xrandr' is not installed\n"
        msg_alloc = 0x225cd00 "Settings schema 'org.mate.SettingsDaemon.plugins.xrandr' is not installed\n"
        i = 2

Is mate-settings-daemon installed which provide org.mate.SettingsDaemon.plugins.xrandr?
Can you explain more detailed how do you installed MATE?


Note You need to log in before you can comment on or make changes to this bug.