Bug 1959969 - Problem reporting tool (gnome-abrt) cannot collect data for reporting system problem
Summary: Problem reporting tool (gnome-abrt) cannot collect data for reporting system ...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-abrt
Version: 34
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Jakub Filak
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 1939467
TreeView+ depends on / blocked
 
Reported: 2021-05-12 18:13 UTC by Magunto
Modified: 2021-06-29 13:51 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-06-29 13:51:54 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Screenshot from the tool's error (66.65 KB, image/png)
2021-05-12 18:13 UTC, Magunto
no flags Details

Description Magunto 2021-05-12 18:13:17 UTC
Created attachment 1782519 [details]
Screenshot from the tool's error

Description of problem:
The problem reporting tool cannot collect information about the problem that occured in the system (eg gnome shell crash) and eventually cannot send it. The problem the tool is analyzing crash data for half an hour and then reports that cannot collect information - user should try again later. Independent how many times or what problem it is related to, result is the same. 

Version-Release number of selected component (if applicable):
Problem Reporting 1.3.6

How reproducible:
After a crash in the system, a pop-up window appears asking if I want to report a problem. After agreeing the problem reporting tools opens and starts it operation. after 30-40 minutes reports that it cannot collect data. 


Steps to Reproduce:
1.As above
2.
3.

Actual results:
Tool not collecting data

Expected results:
Tool collecting respective crash data and sending report to bugzilla. 

Additional info:

Comment 1 Dan T. 2021-05-20 16:47:44 UTC
Just had the exact same issue. I checked journalctl and I don't see any relevant output from abrt or any other processes.

Comment 2 Matej Grabovsky 2021-06-29 13:51:54 UTC
This should be fixed now. Can you please check?


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