Bug 1145697

Summary: reporter-bugzilla killed by SIGABRT
Product: [Fedora] Fedora Reporter: Enygma <Enygma2002_ro>
Component: satyrAssignee: Jakub Filak <jfilak>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: abrt-devel-list, dvlasenk, Enygma2002_ro, jberan, jfilak, mhabrnal, mmilata, rvokal
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/0e874e7f8cfa660ef758142cdf91e33e1cef8887
Whiteboard: abrt_hash:ec93dd99c7d4df71fbf30123ab042e08ff958f51
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 1147952 (view as bug list) Environment:
Last Closed: 2015-06-29 22:39:42 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1147952    
Attachments:
Description Flags
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Enygma 2014-09-23 14:24:27 UTC 
Description of problem:
Tried to report a crash on the JVM (openjdk), but at the final step, after logging into bugzilla and before trying to create the new bug, I got an assertion error and abrt crashed. I could not copy the assertion message in time.

Version-Release number of selected component:
libreport-plugin-bugzilla-2.2.3-2.fc20

Additional info:
reporter:       libreport-2.2.3
backtrace_rating: 4
cmdline:        reporter-bugzilla -b -c /etc/libreport/plugins/bugzilla.conf -F /etc/libreport/plugins/bugzilla_format.conf -A /etc/libreport/plugins/bugzilla_formatdup.conf
crash_function: sr_stacktrace_free
executable:     /usr/bin/reporter-bugzilla
kernel:         3.16.2-200.fc20.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (4 frames)
 #4 sr_stacktrace_free at generic_stacktrace.c:166
 #5 append_short_backtrace at reporter-bugzilla.c:362
 #6 append_item at reporter-bugzilla.c:406
 #7 generate_bz_comment at reporter-bugzilla.c:494
Comment 1 Enygma 2014-09-23 14:24:30 UTC 
Created attachment 940463 [details]
File: backtrace
Comment 2 Enygma 2014-09-23 14:24:31 UTC 
Created attachment 940464 [details]
File: cgroup
Comment 3 Enygma 2014-09-23 14:24:33 UTC 
Created attachment 940465 [details]
File: core_backtrace
Comment 4 Enygma 2014-09-23 14:24:34 UTC 
Created attachment 940466 [details]
File: dso_list
Comment 5 Enygma 2014-09-23 14:24:36 UTC 
Created attachment 940467 [details]
File: environ
Comment 6 Enygma 2014-09-23 14:24:37 UTC 
Created attachment 940468 [details]
File: limits
Comment 7 Enygma 2014-09-23 14:24:39 UTC 
Created attachment 940469 [details]
File: maps
Comment 8 Enygma 2014-09-23 14:24:40 UTC 
Created attachment 940470 [details]
File: open_fds
Comment 9 Enygma 2014-09-23 14:24:42 UTC 
Created attachment 940471 [details]
File: proc_pid_status
Comment 10 Enygma 2014-09-23 14:24:43 UTC 
Created attachment 940472 [details]
File: var_log_messages
Comment 11 Jakub Filak 2014-09-23 15:01:13 UTC 
Thank you for taking the time to report this crash. The assertion message is included in the attached backtrace and denotes an impossible code execution path. Could you please try to report the JVM crash again and report the results here?  If the crash is reproducible, please attach the data of the JVM crash that are stored in one of "/var/tmp/abrt/ccpp*" directories.
Comment 12 Enygma 2014-09-23 19:01:17 UTC 
Hi and thanks for your replay.

Unfortunately, I no longer have the JVM crash. I have tried to re-report the issue, but this time ABRT kept telling me that the crash is invalid, something about "invalid stacktrace", or along that line. After that, I have deleted the crash data. I hope the attached that of my report is enough to get you going in the good direction.

Will try to report anything new that pops up in the meanwhile.
Comment 13 Fedora End Of Life 2015-05-29 12:56:57 UTC 
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. 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 EOL if it remains open with a Fedora  'version'
of '20'.

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 20 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 14 Fedora End Of Life 2015-06-29 22:39:42 UTC 
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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.