|Summary:||[abrt] crash in gnome-settings-daemon-2.28.2-1.fc12: raise: Process /usr/libexec/gnome-settings-daemon was killed by signal 6 (SIGABRT)|
|Product:||[Fedora] Fedora||Reporter:||saulo <sauloal>|
|Component:||gnome-settings-daemon||Assignee:||Bastien Nocera <bnocera>|
|Status:||CLOSED WONTFIX||QA Contact:||Fedora Extras Quality Assurance <extras-qa>|
|Version:||12||CC:||bnocera, dbonline, derstef, jlowry, rstrode, sharon|
|Fixed In Version:||Doc Type:||Bug Fix|
|Doc Text:||Story Points:||---|
|Last Closed:||2010-12-03 15:05:20 UTC||Type:||---|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
|Cloudforms Team:||---||Target Upstream Version:|
Description saulo 2010-05-04 22:19:11 UTC
abrt 1.0.9 detected a crash. architecture: x86_64 Attached file: backtrace cmdline: /usr/libexec/gnome-settings-daemon component: gnome-settings-daemon crash_function: raise executable: /usr/libexec/gnome-settings-daemon global_uuid: ffc2387c1b11f222e4c39eb0c8275fe5f77275f9 kernel: 22.214.171.124-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)
Comment 2 Stefan Lehmann 2010-05-10 07:35:25 UTC
Package: gnome-settings-daemon-2.28.2-1.fc12 Architecture: x86_64 OS Release: Fedora release 12 (Constantine) Comment ----- started session via freenx
Comment 3 Demetrios Belis 2010-05-13 10:05:56 UTC
Package: gnome-settings-daemon-2.28.2-1.fc12 Architecture: x86_64 OS Release: Fedora release 12 (Constantine) How to reproduce ----- 1. This happens every time I connect with freenx client 2. Sometimes, after updating packages and it reboots, it becomes extremely slow. After a reboot, everything is back to normal Comment ----- This happens every time I connect with freenx client. The system is usable though...
Comment 4 Jerry Lowry 2010-05-21 16:40:12 UTC
Package: gnome-settings-daemon-2.28.2-1.fc12 Architecture: x86_64 OS Release: Fedora release 12 (Constantine) How to reproduce ----- 1.logged into the system and it crashed as the system logged me on. 2. 3. Comment ----- updated to the latest versions of software yesterday. system set idle since the reboot. logged in to restart the backup software and the gnome-settings-daemon crashed on login.
Comment 5 Bug Zapper 2010-11-03 15:38:33 UTC
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
Comment 6 Jerry Lowry 2010-11-03 16:58:51 UTC
planning to upgrade to FC 13 before then. Hopefully this will not be a problem after the upgrade. Close at end of life.
Comment 7 Bug Zapper 2010-12-03 15:05:20 UTC
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.