Bug 404235

Summary: Flatpak backend doesn't do error reporting or handling
Product: [Applications] Discover Reporter: Bhushan Shah <bshah>
Component: Flatpak BackendAssignee: Dan Leinir Turthra Jensen <leinir>
Status: RESOLVED DUPLICATE    
Severity: normal CC: aleixpol, bugseforuns, jgrulich, kde, nate, phoenix_firebrd
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: Other   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Bhushan Shah 2019-02-12 12:08:04 UTC 
SUMMARY


STEPS TO REPRODUCE
1. Start discover
2. Start installing flatpak
3. Disconnect internet (best way to produce error I found)

OBSERVED RESULT

Discover quietly finishes operation without any kind of notice.

EXPECTED RESULT

Expect that Discover will show some error message

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: git master

ADDITIONAL INFORMATION
Comment 1 Bhushan Shah 2019-02-12 17:44:01 UTC 
Title is changed incorrectly. It doesn't do any error reporting, Internet connection was just example.
Comment 2 Nate Graham 2019-02-12 17:45:37 UTC 
"Doesn't do any error reporting" is a bit too broad since this would require many fixes. Also, I'm not sure that's true since I do see errors from my Flatpak translations from time to time.
Comment 3 Bhushan Shah 2019-02-12 17:55:56 UTC 
It's most generic way to explain bug I have :P

While installing flatpak on phone it had hit 4-5 different problems,

1) bubblewrap being broken
2) space full on disk
3) internet not connected at all
4) flathub timing out in middle of download
5) one other bit I can't remember right now

But in all cases flatpak CLI correctly reported issue but not discover, so oh well.
Comment 4 Nate Graham 2019-02-12 18:09:49 UTC 
Yikes.
Comment 5 Patrick Silva 2019-02-27 20:08:09 UTC 
*** Bug 403377 has been marked as a duplicate of this bug. ***
Comment 6 Nate Graham 2019-04-09 15:24:15 UTC 
*** Bug 406286 has been marked as a duplicate of this bug. ***
Comment 7 Aleix Pol 2019-04-17 16:42:48 UTC 

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