Bug 1036460

Summary: [abrt] mate-settings-daemon-1.6.2-0.3.gitd2d3aa7.fc19: mate_rr_config_new_current: Process /usr/libexec/mate-settings-daemon was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: M. Edward (Ed) Borasky <znmeb>
Component: mate-settings-daemonAssignee: Dan Mashal <dan.mashal>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 19CC: dan.mashal, fedora, rdieter, stefano, znmeb
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/50e7133c3b690a632437b2a02ac0d9ca927ef7fa
Whiteboard: abrt_hash:009050e4516f6a520b10ded7ded0f73cd61e2028
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-02-17 19:29:21 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
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: var_log_messages
none
Most recent Xorg.0.log before the crash none

Description M. Edward (Ed) Borasky 2013-12-02 03:53:05 UTC
Description of problem:
starting up Mate desktop after reconfiguring a new monitor. I think it has something to do with the Radeon driver and mode lines.

Version-Release number of selected component:
mate-settings-daemon-1.6.2-0.3.gitd2d3aa7.fc19

Additional info:
reporter:       libreport-2.1.9
backtrace_rating: 4
cmdline:        /usr/libexec/mate-settings-daemon
crash_function: mate_rr_config_new_current
executable:     /usr/libexec/mate-settings-daemon
kernel:         3.11.9-200.fc19.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #4 mate_rr_config_new_current at mate-rr-config.c:607
 #5 config_new_stored at mate-rr-config.c:1142
 #6 mate_rr_config_apply_from_filename_with_time at mate-rr-config.c:1346
 #7 apply_configuration_from_filename at msd-xrandr-manager.c:334
 #8 apply_stored_configuration_at_startup at msd-xrandr-manager.c:2229
 #9 msd_xrandr_manager_start at msd-xrandr-manager.c:2341
 #10 impl_activate at msd-xrandr-plugin.c:78
 #11 _activate_plugin at mate-settings-plugin-info.c:476
 #12 mate_settings_plugin_info_activate at mate-settings-plugin-info.c:499
 #13 maybe_activate_plugin at mate-settings-manager.c:87

Comment 1 M. Edward (Ed) Borasky 2013-12-02 03:53:11 UTC
Created attachment 831398 [details]
File: backtrace

Comment 2 M. Edward (Ed) Borasky 2013-12-02 03:53:14 UTC
Created attachment 831399 [details]
File: cgroup

Comment 3 M. Edward (Ed) Borasky 2013-12-02 03:53:16 UTC
Created attachment 831400 [details]
File: core_backtrace

Comment 4 M. Edward (Ed) Borasky 2013-12-02 03:53:20 UTC
Created attachment 831401 [details]
File: dso_list

Comment 5 M. Edward (Ed) Borasky 2013-12-02 03:53:23 UTC
Created attachment 831402 [details]
File: environ

Comment 6 M. Edward (Ed) Borasky 2013-12-02 03:53:26 UTC
Created attachment 831403 [details]
File: limits

Comment 7 M. Edward (Ed) Borasky 2013-12-02 03:53:30 UTC
Created attachment 831404 [details]
File: maps

Comment 8 M. Edward (Ed) Borasky 2013-12-02 03:53:33 UTC
Created attachment 831406 [details]
File: open_fds

Comment 9 M. Edward (Ed) Borasky 2013-12-02 03:53:35 UTC
Created attachment 831408 [details]
File: proc_pid_status

Comment 10 M. Edward (Ed) Borasky 2013-12-02 03:53:38 UTC
Created attachment 831410 [details]
File: var_log_messages

Comment 11 M. Edward (Ed) Borasky 2013-12-02 04:05:58 UTC
Created attachment 831428 [details]
Most recent Xorg.0.log before the crash

I think this bug is something in the 3.11 kernel Radeon driver; I didn't have anything strange happen with 3.9.5. I also think bug https://bugzilla.redhat.com/show_bug.cgi?id=1036463 is the same underlying problem.

Comment 12 Wolfgang Ulbrich 2013-12-02 15:52:32 UTC
I'm not an expert with ATI driver, i'm nvidia user, but..

#7  0x00007f674b504ed5 in apply_configuration_from_filename (manager=manager@entry=0x10b38a0, filename=filename@entry=0x10c9880 "/home/znmeb/.config/monitors.xml.backup", no_matching_config_is_an_error=no_matching_config_is_an_error@entry=0, timestamp=timestamp@entry=0, error=error@entry=0x7fffc8278ec0) at msd-xrandr-manager.c:334

I think m-s-d expect a /home/znmeb/.config/monitors.xml
Here on my system this file is there.
In relation to the other report about m-c-c, can you run'mate-display-properties' from a terminal to create this file?
If m-d-p starts you'll trigger another abrt alarm after clicking on the apply button. This is a well known old issue and reported but monitors.xml should be written.

Comment 13 M. Edward (Ed) Borasky 2013-12-02 21:18:07 UTC
I typed in 'mate-display-properties' and it crashed without writing ~/.config/monitors.xml

Comment 14 Fedora End Of Life 2015-01-09 20:45:12 UTC
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 19 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 15 Fedora End Of Life 2015-02-17 19:29:21 UTC
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.