Bug 1036463

Summary: [abrt] gnome-settings-daemon-3.8.5-1.fc19: gnome_rr_config_load_current: Process /usr/libexec/gnome-settings-daemon was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: M. Edward (Ed) Borasky <znmeb>
Component: gnome-settings-daemonAssignee: Bastien Nocera <bnocera>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 19CC: bnocera, fmuellner, mkasik, ofourdan, rstrode, tiagomatos
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/32622fa50b2a4bf75c21bdd7b3024dcbe5e213f2
Whiteboard: abrt_hash:40678515058ce9e0f9a3f4d72eef685df8d5c047
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-02-17 19:29:23 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

Description M. Edward (Ed) Borasky 2013-12-02 04:01:58 UTC 
Description of problem:
I have a new system. So ... installed Fedora 19 on it, updated all the packages, installed some more stuff on it, configured the monitor / Radeon driver and tried to log into GNOME 3. This crash is the result. *After* this crash, I tried to log in to the MATE desktop. That login succeeded but generated another ABRT - https://bugzilla.redhat.com/show_bug.cgi?id=1036460

I think this is the same problem - something to do with the Radeon driver and mode lines. I'm going to attach the Xorg.0.log to the *other* bug (https://bugzilla.redhat.com/show_bug.cgi?id=1036460).

Version-Release number of selected component:
gnome-settings-daemon-3.8.5-1.fc19

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

Truncated backtrace:
Thread no. 1 (10 frames)
 #4 gnome_rr_config_load_current at gnome-rr-config.c:659
 #5 gnome_rr_config_new_current at gnome-rr-config.c:735
 #6 gnome_rr_config_load_filename at gnome-rr-config.c:675
 #7 apply_configuration_from_filename at gsd-xrandr-manager.c:453
 #8 apply_stored_configuration_at_startup at gsd-xrandr-manager.c:1936
 #9 gsd_xrandr_manager_start at gsd-xrandr-manager.c:2077
 #10 impl_activate at gsd-xrandr-plugin.c:29
 #11 _activate_plugin at gnome-settings-plugin-info.c:408
 #12 gnome_settings_plugin_info_activate at gnome-settings-plugin-info.c:431
 #13 maybe_activate_plugin at gnome-settings-manager.c:95

Potential duplicate: bug 1021155
Comment 1 M. Edward (Ed) Borasky 2013-12-02 04:02:06 UTC 
Created attachment 831418 [details]
File: backtrace
Comment 2 M. Edward (Ed) Borasky 2013-12-02 04:02:10 UTC 
Created attachment 831419 [details]
File: cgroup
Comment 3 M. Edward (Ed) Borasky 2013-12-02 04:02:13 UTC 
Created attachment 831420 [details]
File: core_backtrace
Comment 4 M. Edward (Ed) Borasky 2013-12-02 04:02:18 UTC 
Created attachment 831421 [details]
File: dso_list
Comment 5 M. Edward (Ed) Borasky 2013-12-02 04:02:21 UTC 
Created attachment 831422 [details]
File: environ
Comment 6 M. Edward (Ed) Borasky 2013-12-02 04:02:25 UTC 
Created attachment 831423 [details]
File: limits
Comment 7 M. Edward (Ed) Borasky 2013-12-02 04:02:29 UTC 
Created attachment 831424 [details]
File: maps
Comment 8 M. Edward (Ed) Borasky 2013-12-02 04:02:32 UTC 
Created attachment 831425 [details]
File: open_fds
Comment 9 M. Edward (Ed) Borasky 2013-12-02 04:02:36 UTC 
Created attachment 831426 [details]
File: proc_pid_status
Comment 10 M. Edward (Ed) Borasky 2013-12-02 04:02:39 UTC 
Created attachment 831427 [details]
File: var_log_messages
Comment 11 Fedora End Of Life 2015-01-09 20:45:15 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 12 Fedora End Of Life 2015-02-17 19:29:23 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.