Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
Abrt generated report for /usr/lib64/xulrunner/plugin-container which was killed by SIGSEGV.
When chose to send report, Retrace server didn't support release rhel7 Alpha 3 -> then I generated traceback locally, however after clicking on "Forvard" in GUI, it disappeared without any sign of expected activity.
Version-Release number of selected component (if applicable):
xulrunner-17.0.2-3.el7.x86_64
abrt-2.1.1-3.el7.x86_64
How reproducible:
always for me. I have the item in abrt-gui and can reproduce it
Steps to Reproduce:
1. select xulrunner crash
2. click Report
3. disagree with upload of dump
4. observe successful analysis
5. click Forward
Actual results:
Report window closes
Window: OK Processing finished
Log:
--- Running analyze_CCpp ---
Ok to upload core dump? (It may contain sensitive data). If your answer is 'No', a stack trace will be generated locally. (It may download a huge amount of data). 'NO'
Analyzing coredump 'coredump'
All debuginfo files are available
Generating backtrace
Backtrace is generated and saved, 2503 bytes
--- Running collect_Smolt ---
Smolt package not installed, can't save profile
--- Running collect_xsession_errors ---
No ~/.xsession-errors
===end log===
Expected results:
Report window does not close itself without sending report nor without any error message
Additional info:
Created attachment 708965[details]
/var/tmp/abrt report
xulrunner string found on path /var/tmp/abrt. This is the directory from there with surrounding files