Bug 1514980 - fedora 27 - reporting is disabled because backtrace is unusable
Summary: fedora 27 - reporting is disabled because backtrace is unusable
Keywords:
Status: CLOSED DUPLICATE of bug 1515265
Alias: None
Product: Fedora
Classification: Fedora
Component: abrt
Version: 27
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: abrt
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-11-19 20:44 UTC by Aleksandar Kostadinov
Modified: 2018-10-02 20:43 UTC (History)
7 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2018-10-02 20:43:57 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1515265 0 unspecified CLOSED Reporting disabled because the backtrace is unusable 2021-02-22 00:41:40 UTC

Description Aleksandar Kostadinov 2017-11-19 20:44:07 UTC
Description of problem:
like bug 750616 I see this error message:

> --- Running report_uReport ---
> ('report_uReport' completed successfully)
> 
> --- 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, 49099 bytes
> 
> --- Running analyze_BodhiUpdates ---
> Looking for similar problems in bugzilla

And in the status bar "Reporting is disabled because backtrace is unusable"

Version-Release number of selected component (if applicable):
abrt-2.10.5-1.fc27.x86_64

How reproducible:
two times out of two I get the same error. xfce4-notifyd-0.4.0-2.fc27.x86_64 crashes when I try to do things with the new dnfdragora applet. Maybe can reproduce trying to update using it.

/var/tmp/abrt/ is empty so I can't tell what is going on. I think `abrt` itself should provide some more information when things go wrong and this is actually a bigger bug IMO.

Comment 1 Miroslav Suchý 2018-10-02 20:43:57 UTC

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


Note You need to log in before you can comment on or make changes to this bug.