abrt 1.1.1 detected a crash. architecture: i686 Attached file: backtrace cmdline: rss-glx-busyspheres -r component: rss-glx crash_function: raise executable: /usr/bin/rss-glx-busyspheres global_uuid: 10fddf8498b35f6019c15a5286365b816ae0d5be kernel: 2.6.32.16-150.fc12.i686.PAE package: rss-glx-0.9.1.p-2.fc12 rating: 4 reason: Process /usr/bin/rss-glx-busyspheres was killed by signal 6 (SIGABRT) release: Fedora release 12 (Constantine)
Created an attachment (id=440296) File: backtrace
This really should have the same abrt hash as bug #629404. Changing component to abrt for further investigation.
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
One of these bugs is reported by abrt-1.1.1 and the other by abrt-1.1.13 - there was a change in the hash generating logic between those versions and this problem should be fixed now.