abrt version: 1.1.13 architecture: i686 Attached file: backtrace cmdline: rss-glx-busyspheres -r component: rss-glx crash_function: raise executable: /usr/bin/rss-glx-busyspheres kernel: 2.6.32.19-163.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) time: 1283897019 uid: 500
Created an attachment (id=445855) File: backtrace
This is really the same as bug #629404 and I wonder why abrt didn't recognize it's a duplicate -- it has the same abrt hash after all. The only difference I see is that I changed the component to mesa in the original bug and added a comment, but that shouldn't be a reason for abrt to open duplicate bugs. Maybe abrt doesn't cope well with the new Bugzilla version? I'll change the component to abrt for investigation of this problem.
ABRT currently checks if the component is the same. We should probably remove this check. A negative consequence of the removal is that (for example) if a GTK bug is reported to Evince, users of all applications using GTK get their crash reported to the Evince bug too. So we need to add a comment with the reporter's component if it's different from the existing bug's component.
Abrt should probably compare the component name to the current one and those already recorded in the first and subsequent comments. If it's any of these, adding another comment would just clutter up the report.
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
We should detect library crashes on Bugzilla level (using a tool which operates on Bugzilla). Client reporting problems to Bugzilla cannot have enough information to recognize whether a bug belongs to an application or some library.
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
Backtrace analysis found this bug to be similar to some already closed bugs from other components. You might want to check those bugs for additional information. Bugs which were found to be similar to this bug: abrt: bug #626294 mesa: bug #629404 This comment is automatically generated.
I believe this bug is fixed. ABRT deduplicator found rhbz#629404 as a duplicate which according the comment#1 is really a duplicate.