abrt 1.0.9 detected a crash. architecture: x86_64 Attached file: backtrace cmdline: /usr/libexec/gnome-settings-daemon comment: Restarting the deamon on the command line gives the same crash. component: gnome-settings-daemon crash_function: raise executable: /usr/libexec/gnome-settings-daemon global_uuid: c79fa295daa49cef58185485b4bd41098a58683c kernel: 2.6.32.11-99.fc12.x86_64 package: gnome-settings-daemon-2.28.2-1.fc12 rating: 4 reason: Process /usr/libexec/gnome-settings-daemon was killed by signal 6 (SIGABRT) release: Fedora release 12 (Constantine) How to reproduce ----- 1. Start a gnome session through NX server (GPL) (it works just fine with a normal X session)
Created attachment 427009 [details] File: backtrace
Seems similar to https://bugzilla.redhat.com/show_bug.cgi?id=480867 in F10. Users reported it to be fixed in F11 though. I'm seeing it in F12.
There is also some extra output that I missed in the original report: ** (gnome-settings-daemon:25294): WARNING **: Unable to start xrandr manager: RANDR extension is too old (< 1.2) Gdk-ERROR **: The program 'gnome-settings-daemon' received an X Window System error. This probably reflects a bug in the program. The error was 'XI_BadClass (invalid Class parameter)'. (Details: serial 152 error_code 133 request_code 131 minor_code 6) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) aborting...
This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '12'. 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 prior to Fedora 12's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 12 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 please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. 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. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 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. Thank you for reporting this bug and we are sorry it could not be fixed.