Bug 1014239

Summary: faf cannot recognize duplicates of crashes on Fedora 19
Product: [Fedora] Fedora Reporter: Frank Ch. Eigler <fche>
Component: libreportAssignee: Michal Toman <mtoman>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 19CC: abrt-devel-list, amit.shah, andy.blight, dvlasenk, fche, jfilak, mlichvar, mmilata, mtoman, pknirsch, rvokal
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:f8fad5403e7efc9821436774744b2a4ff72b27f1
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-02-17 17:26:39 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: exploitable
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages
none
File: core.3614
none
File: core.3624
none
entire ccpp directory none

Description Frank Ch. Eigler 2013-10-01 14:46:19 UTC
Description of problem:
It was dealing with a firefox-plugin (flash) crash.

Version-Release number of selected component:
libreport-plugin-ureport-2.1.7-1.fc19

Additional info:
reporter:       libreport-2.1.7
backtrace_rating: 4
cmdline:        reporter-ureport
crash_function: sr_rpm_package_free
executable:     /usr/bin/reporter-ureport
kernel:         3.10.10-200.fc19.x86_64
runlevel:       N 3
type:           CCpp
uid:            500

Truncated backtrace:
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

Comment 1 Frank Ch. Eigler 2013-10-01 14:46:23 UTC
Created attachment 806021 [details]
File: backtrace

Comment 2 Frank Ch. Eigler 2013-10-01 14:46:27 UTC
Created attachment 806022 [details]
File: cgroup

Comment 3 Frank Ch. Eigler 2013-10-01 14:46:30 UTC
Created attachment 806023 [details]
File: core_backtrace

Comment 4 Frank Ch. Eigler 2013-10-01 14:46:34 UTC
Created attachment 806024 [details]
File: dso_list

Comment 5 Frank Ch. Eigler 2013-10-01 14:46:37 UTC
Created attachment 806025 [details]
File: environ

Comment 6 Frank Ch. Eigler 2013-10-01 14:46:41 UTC
Created attachment 806026 [details]
File: exploitable

Comment 7 Frank Ch. Eigler 2013-10-01 14:46:45 UTC
Created attachment 806027 [details]
File: limits

Comment 8 Frank Ch. Eigler 2013-10-01 14:46:49 UTC
Created attachment 806028 [details]
File: maps

Comment 9 Frank Ch. Eigler 2013-10-01 14:46:53 UTC
Created attachment 806029 [details]
File: open_fds

Comment 10 Frank Ch. Eigler 2013-10-01 14:46:58 UTC
Created attachment 806030 [details]
File: proc_pid_status

Comment 11 Frank Ch. Eigler 2013-10-01 14:47:01 UTC
Created attachment 806031 [details]
File: var_log_messages

Comment 12 Frank Ch. Eigler 2013-10-01 14:47:16 UTC
Created attachment 806032 [details]
File: core.3614

Comment 13 Frank Ch. Eigler 2013-10-01 14:47:27 UTC
Created attachment 806033 [details]
File: core.3624

Comment 14 Jakub Filak 2013-10-01 15:12:08 UTC
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 [1] 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.


1: https://retrace.fedoraproject.org/faf/problems/1161922/

Comment 15 Frank Ch. Eigler 2013-10-01 15:20:09 UTC
Created attachment 806041 [details]
entire ccpp directory

(I believe almost all of these were already individually attached above.)

Comment 16 Jakub Filak 2013-10-01 15:50:01 UTC
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.

Comment 17 Fedora End Of Life 2015-01-09 20:03:49 UTC
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.

Comment 18 Fedora End Of Life 2015-02-17 17:26:39 UTC
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
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.