Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.

Bug 1149477

Summary:	abrt fails to report crashes in native code for java: reporter-ureport failed with exit code 1
Product:	[Fedora] Fedora	Reporter:	Christian Stadelmann <fedora>
Component:	abrt	Assignee:	Marek Bryša <mbrysa>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	21	CC:	abrt-devel-list, dvlasenk, iprikryl, jberan, jfilak, mhabrnal, mikhail.v.gavrilov, mmilata, mtoman
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	gnome-abrt-1.0.0-1.fc21	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-10-16 21:56:55 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Christian Stadelmann 2014-10-05 11:47:49 UTC

Description of problem:
I've seen 2 native code crashes in java recently and both could not be reported using ABRT:
https://bugzilla.redhat.com/show_bug.cgi?id=1149463
https://bugzilla.redhat.com/show_bug.cgi?id=1149473

Version-Release number of selected component (if applicable):
abrt 2.2.2-9.fc21

How reproducible:
Don't know. java crashes don't happen that much.

Actual results:
abrt was unable to report the bugs.

Expected results:
abrt should be able to report the bugs.

Additional info:
the event_log file has the full error message. It is the same for both bugs (ignoring the timestamp):

2014-10-04-18:06:36> Der Server hat mit einer Fehlermeldung geantwortet: »Validation failed: Element 'stacktrace' is invalid: List element is invalid: Element 'frames' is invalid: List element is invalid: Element 'file_name' is missing«
2014-10-04-18:06:36  reporter-ureport failed with exit code 1
2014-10-04-18:06:36* (»report_uReport« abgebrochen durch 1)
2014-10-04-18:06:48> Der Server hat mit einer Fehlermeldung geantwortet: »Validation failed: Element 'stacktrace' is invalid: List element is invalid: Element 'frames' is invalid: List element is invalid: Element 'file_name' is missing«
2014-10-04-18:06:48  reporter-ureport failed with exit code 1
2014-10-04-18:06:48* (»report_uReport« abgebrochen durch 1)

Comment 1 Jakub Filak 2014-10-06 07:57:19 UTC

Hello, thank you for taking the time report this issue. This bug report should be filed against ABRT Server (http://retrace.fedoraproject.org/) but there is no such a component in Bugzilla yet.

At first glance, it appears that we can safely ignore the last invalid frame in a core backtrace.

Comment 2 Christian Stadelmann 2014-10-06 08:56:43 UTC

Could it be possible that this bug is a result of https://bugzilla.redhat.com/show_bug.cgi?id=1148207 ? If yes this bug could be closed.

Comment 3 Jakub Filak 2014-10-06 09:00:48 UTC

(In reply to Christian Stadelmann from comment #2)
> Could it be possible that this bug is a result of
> https://bugzilla.redhat.com/show_bug.cgi?id=1148207 ? If yes this bug could
> be closed.

Thanks! Good point, but no, this bug is caused by something else. Our algorithm based on elfutils produced a backtrace where some of the function frames misses source file name and function name.

Comment 4 Marek Bryša 2014-10-06 09:09:37 UTC

https://github.com/abrt/faf/pull/288 fixes this bug. It should get through the deployment process to our production server within a week.
Thank you for reporting this issue.

Comment 5 Fedora Update System 2014-10-14 12:22:01 UTC

gnome-abrt-1.0.0-1.fc21,abrt-2.3.0-2.fc21,libreport-2.3.0-2.fc21,satyr-0.15-1.fc21 has been submitted as an update for Fedora 21.
https://admin.fedoraproject.org/updates/gnome-abrt-1.0.0-1.fc21,abrt-2.3.0-2.fc21,libreport-2.3.0-2.fc21,satyr-0.15-1.fc21

Comment 6 Jakub Filak 2014-10-15 08:41:58 UTC

*** Bug 1152663 has been marked as a duplicate of this bug. ***

Comment 7 Fedora Update System 2014-10-16 01:59:36 UTC

Package gnome-abrt-1.0.0-1.fc21, abrt-2.3.0-2.fc21, libreport-2.3.0-2.fc21, satyr-0.15-1.fc21:
* should fix your issue,
* was pushed to the Fedora 21 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing gnome-abrt-1.0.0-1.fc21 abrt-2.3.0-2.fc21 libreport-2.3.0-2.fc21 satyr-0.15-1.fc21'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2014-12856/gnome-abrt-1.0.0-1.fc21,abrt-2.3.0-2.fc21,libreport-2.3.0-2.fc21,satyr-0.15-1.fc21
then log in and leave karma (feedback).

Comment 8 Christian Stadelmann 2014-10-16 21:56:55 UTC

I can configm the fix. Thanks!

Comment 9 Fedora Update System 2014-10-20 16:39:09 UTC

gnome-abrt-1.0.0-1.fc21, abrt-2.3.0-2.fc21, libreport-2.3.0-2.fc21, satyr-0.15-1.fc21 has been pushed to the Fedora 21 stable repository.  If problems still persist, please make note of it in this bug report.