Red Hat Bugzilla – Bug 1014239
faf cannot recognize duplicates of crashes on Fedora 19
Last modified: 2015-03-22 20:42:08 EDT
Description of problem:
It was dealing with a firefox-plugin (flash) crash.
Version-Release number of selected component:
runlevel: N 3
Thread no. 1 (5 frames)
#0 sr_rpm_package_free at rpm.c:61
#1 sr_rpm_package_uniq at rpm.c:260
#2 sr_abrt_rpm_packages_from_dir at abrt.c:268
#3 sr_abrt_report_from_dir at abrt.c:355
#4 libreport_ureport_from_dump_dir at json.c:43
Created attachment 806021 [details]
Created attachment 806022 [details]
Created attachment 806023 [details]
Created attachment 806024 [details]
Created attachment 806025 [details]
Created attachment 806026 [details]
Created attachment 806027 [details]
Created attachment 806028 [details]
Created attachment 806029 [details]
Created attachment 806030 [details]
Created attachment 806031 [details]
Created attachment 806032 [details]
Created attachment 806033 [details]
Thank you for the bug report. This bug report has been filed by ABRT and it should be recognized as a duplicate of the older bug #1010948 report but reporter-bugzilla could not recognize the older bug reporter as a duplicate because the older report is marked as private. The ABRT server were responsible for the duplicate detection but the crash  does not have any bugzilla URL attached.
Could you please attach an archive with the crash data? You can easily find a file system path to the data by right click on the problem entry in the list of problems in gnome-abrt.
Created attachment 806041 [details]
entire ccpp directory
(I believe almost all of these were already individually attached above.)
Thank you for the quick response.
These two lines from event_log file show us where is the problem:
2013-10-01-10:47:31> This problem does not have an uReport assigned.
2013-10-01-10:47:31* ('post_report' exited with 1)
The ABRT server were not able to process the crash.
But the file also says that report_uReport event was completed successfully:
2013-10-01-10:42:52> ('report_uReport' completed successfully)
Therefore the problem must be on ABRT server's side.
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.
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
Thank you for reporting this bug and we are sorry it could not be fixed.