Bug 1532004

Summary: Crashes sometimes cannot be reported using ABRT
Product: [Fedora] Fedora Reporter: Jan Vlug <jan.public>
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, forummail, jakub, jorti, michal.toman, mkutlak, mmarusak, msuchy, sc1.bugzilla.redhat
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-10-02 20:45:50 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:
Bug Depends On: 1540500, 1547787    
Bug Blocks:    

Description Jan Vlug 2018-01-07 10:39:38 UTC
It happens quite often that I cannot report crashes with ABRT.
I have the impression that these crashes are often related to Wayland or nouveau.

I will report these crashes as comments to this bug.

The first one is:
https://retrace.fedoraproject.org/faf/reports/1851071/
also reported as bug 1532002.

Comment 1 Jan Vlug 2018-01-07 11:04:53 UTC
I also tried reporting the crash via the CLI:

(I also manually did: debuginfo-install deja-dup-37.0-1.fc27)

report-cli -v /var/spool/abrt/ccpp-2018-01-07-11:22:13.301422-9167
uReport has been already sent: '/var/spool/abrt/ccpp-2018-01-07-11:22:13.301422-9167'
Bug for '/var/spool/abrt/ccpp-2018-01-07-11:22:13.301422-9167' not yet filed. Continuing.
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). [y/N/f/e] y  
Querying server settings
Preparing an archive to upload
Waiting for tar...
Waiting for xz...
Done...
Uploading 2.0 MiB
Upload successful
Retrace job started
Preparing environment for backtrace generation
...
Preparing environment for backtrace generation
Generating backtrace
Cleaning environment after backtrace generation
Retrace job finished successfully
No exploitable data available
Using product "Fedora".
Using product version 27.
Loading settings from '/etc/libreport/plugins/bugzilla.conf'
create private bz ticket: 'NO'
groups: '0x55680efc8440'
Initializing XML-RPC library
Looking for similar problems in bugzilla
There is no bugzilla bug with 'abrt_hash:2e41039cf8e7b351bfab1397e83233702b800fc7'
Reporting disabled because the backtrace is unusable.
Please try to install debuginfo manually using the command: "debuginfo-install deja-dup-37.0-1.fc27" and try again.

Comment 2 Jan Vlug 2018-02-23 17:42:34 UTC
See also: https://bugzilla.redhat.com/show_bug.cgi?id=1531472#c2

Comment 3 Lorenzo Calabrese 2018-05-20 13:17:50 UTC
The same bug happen in several of my machines.
(Just as Jan Vlug in https://bugzilla.redhat.com/show_bug.cgi?id=1531472#c2)

It appears with several software, from the graphical invocation as well from the cli.

The result is invariably : [...] no backtrace usable [...]

Here is a sample when I tried to launched supertux-kart

Note of some interest : it as started to happen only with the last updates of FC27

I do not know what is implied there, and i feel sorry to miss time to dig in it myself

So here is going a *bog* thank you to whom is going to do it.

IMHO it is not a simple bug.

I would hate to see *normal* users stepping back from O.S. if the problem persist and start to happen with LibreOffice and some more day by day essentials 

Having a **working** return of information about bug is, again, IMHO, crucial.

Since "bug return" is not working, I do think very probable we are missing a lot of others feed back.

Hom much ?

-----------------
[root@node0 abrt]# report-cli -v /var/spool/abrt/ccpp-2018-05-20-10\:16\:48.222538-3218
uReport has been already sent: '/var/spool/abrt/ccpp-2018-05-20-10:16:48.222538-3218'
Bug for '/var/spool/abrt/ccpp-2018-05-20-10:16:48.222538-3218' not yet filed. Continuing.
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). [y/N/f/e] y
Querying server settings
Preparing an archive to upload
Waiting for tar...
Waiting for xz...
Done...
You are going to upload 28.3 MiB. Continue? [y/N] y
Uploading 28.3 MiB
Uploading 25%
Uploading 48%
Uploading 74%
Uploading 99%
Upload successful
Retrace job started
Preparing environment for backtrace generation
Preparing environment for backtrace generation
Preparing environment for backtrace generation
Preparing environment for backtrace generation
Preparing environment for backtrace generation
Preparing environment for backtrace generation
Preparing environment for backtrace generation
Preparing environment for backtrace generation
Preparing environment for backtrace generation
Generating backtrace
Cleaning environment after backtrace generation
Retrace job finished successfully
No exploitable data available
Using product "Fedora".
Using product version 28.
Loading settings from '/etc/libreport/plugins/bugzilla.conf'
Loading settings from '/root/.config/libreport/bugzilla.conf'
create private bz ticket: 'NO'
groups: '0x564d39f11460'
Initializing XML-RPC library
Looking for similar problems in bugzilla
There is no bugzilla bug with 'abrt_hash:c2940ba68517c08d92720756b00c75824212ec59'
Reporting disabled because the backtrace is unusable.
Please try to install debuginfo manually using the command: "debuginfo-install supertuxkart-0.9.3-2.fc28.3" and try again.

---------------

Cheers
and thank you again
Enzo.

Comment 4 James Caldwell 2018-08-21 22:39:28 UTC
I slowly got the debuginfos installed. abrt failed the same as other reports. I tried report-cli which failed due to debuginfo files failing to install.  So with a little goggling I found that debuginfo-install was not installed but that was not the issue with report-cli. I then find there is a tool called coredumputil which will help process a coredump and get all the debuginfo files. Oh goodie.

Fedora Magazine https://fedoramagazine.org/file-better-bugs-coredumpctl/ has instructions. 

These types of instructions HELP us HELP developers. :)

Once I'd gotten this done then report-cli worked.

Comment 5 Miroslav Suchý 2018-10-02 20:45:50 UTC

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