Bug 1128060 - No option to retry report submission if it fails due to network problems
Summary: No option to retry report submission if it fails due to network problems
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: libreport
Version: 21
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
Assignee: abrt
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-08-08 07:58 UTC by Adam Williamson
Modified: 2014-08-25 10:16 UTC (History)
5 users (show)

Fixed In Version: libreport-2.2.3-4.fc21
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-08-25 10:16:36 UTC


Attachments (Terms of Use)


Links
System ID Priority Status Summary Last Updated
Red Hat Bugzilla 1069917 None None None Never

Internal Links: 1069917

Description Adam Williamson 2014-08-08 07:58:08 UTC
I just hit a crash in anaconda, went to report it, and ran into https://bugzilla.redhat.com/show_bug.cgi?id=811967 - the consequence being that the network is unavailable. Report submission fails with an error "--- Running report_Bugzilla ---
fatal: libcurl failed to execute the HTTP POST transaction, explaining:  Could not resolve host: bugzilla.redhat.com
('report_Bugzilla' exited with 1)" . Obviously it failed due to the lack of network, but there doesn't seem to be a way to retry after fixing the network issue.

I can retry by leaving the submission process entirely and restarting - anaconda leaves the 'i have crashed, submit a report?' dialog up - but I have to go through the whole process again, including entering the description and my Bugzilla credentials, which is obviously inefficient.

Comment 1 Jakub Filak 2014-08-08 08:50:21 UTC
Hi Adam, thank you for the report! I have a good news, I fixed this annoying lack of user friendliness few days ago in upstream git via commit: https://github.com/abrt/libreport/commit/8db880a2c6add7137aac9f8562ae73aef3e1e436

I will update the packages ASAP!


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