Bug 1523523

Summary: Reporting disabled because the backtrace is unusable
Product: [Fedora] Fedora Reporter: hacrot3000
Component: abrtAssignee: abrt <abrt-devel-list>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 27CC: abrt-devel-list, bughunt, dvlasenk, extras-qa, iprikryl, jakub, jan.public, jberan, michal.toman, mikhail.v.gavrilov, mkutlak, mmarusak, msuchy
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1291093 Environment:
Last Closed: 2018-10-02 20:45:09 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:
Attachments:
Description Flags
Cannot submit error reporting
none
/usr/share/libreport/events/report_uReport.xml none

Description hacrot3000 2017-12-08 08:37:30 UTC
Created attachment 1364672 [details]
Cannot submit error reporting

While I was browsing with Firefox, the gnome crashed and logout. After login it says Xwayland killed by SIGABRT. I tried to report this problem but some how the problem reporting has bug itself and doesn't allow me to send anything.

I tried to select "No" when being asked "Ok to upload core dump" and but the local app still cannot upload it.


+++ This bug was initially created as a clone of Bug #1291093 +++

Description of problem:
Reporting disabled because the backtrace is unusable. Why? all debug symbols are available for gnome-shell.

--- Additional comment from Mikhail on 2015-12-13 14:10 EST ---



--- Additional comment from Mikhail on 2015-12-13 14:13 EST ---



--- Additional comment from David Tonhofer on 2016-07-30 15:11:37 EDT ---

Hitting similar trouble in Fedora 24

abrt window  shows:

....
"All debuginfo files are available"
"Generating backtrace"
"Backtrace is generated and saved, 26178 bytes"
"Looking for similar problems in bugzilla"

Underneath we see:

"Reporting disabled because the backtrace is unusable"

(I even enabled fedora-debuginfo repository to no avail)

--- Additional comment from Jakub Filak on 2016-08-04 06:51:50 EDT ---

(In reply to David Tonhofer from comment #3)
> Hitting similar trouble in Fedora 24

Which package? Can you please attach the backtrace?

--- Additional comment from David Tonhofer on 2016-08-07 07:42:05 EDT ---

Sorry. It was knsapshot I think. I deleted the backtrace, will post again if error reoccurs.

--- Additional comment from Fedora End Of Life on 2016-11-24 09:12:53 EST ---

This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. 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 '23'.

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 23 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.

--- Additional comment from Fedora End Of Life on 2016-12-20 11:59:03 EST ---

Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 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.

Comment 1 hacrot3000 2017-12-08 08:39:22 UTC
Created attachment 1364673 [details]
/usr/share/libreport/events/report_uReport.xml

I am adding the file /usr/share/libreport/events/report_uReport.xml hope it help

Comment 2 hacrot3000 2017-12-08 09:00:26 UTC
If you want to get the full data, please see this attachment https://bugzilla.redhat.com/attachment.cgi?id=1364691 on bug #1523526

Comment 3 rugk 2017-12-12 23:20:41 UTC
Maybe that is the same/a duplicate of my issue Bug 1513807 ?

Comment 4 hacrot3000 2017-12-13 01:56:46 UTC
(In reply to rugk from comment #3)
> Maybe that is the same/a duplicate of my issue Bug 1513807 ?

No, it not. This bug is cannot submit data for Bug 1513807. It does mean when Bug 1513807 happened, I have no option to report bug to  BZ

Comment 5 Jan Vlug 2018-01-31 08:38:07 UTC
I also experience regularly crashes that cannot be reported to Bugzilla via abrt:
https://retrace.fedoraproject.org/faf/reports/1999013/
https://retrace.fedoraproject.org/faf/dumpdirs/new/oops-2018-01-26-21:28:20-1347-0.tar.gz/

I guess the last one was also not correctly uploaded to FAF.

Comment 6 Jan Vlug 2018-01-31 09:05:44 UTC
See also bug #1532004.

Comment 7 Miroslav Suchý 2018-10-02 20:45:09 UTC

*** This bug has been marked as a duplicate of bug 1515265 ***