Bug 403377 - Display error message when flatpak app fails to install
Summary: Display error message when flatpak app fails to install
Status: RESOLVED DUPLICATE of bug 404235
Alias: None
Product: Discover
Classification: Applications
Component: discover (show other bugs)
Version: 5.14.90
Platform: Neon Linux
: NOR normal
Target Milestone: ---
Assignee: Aleix Pol
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-01-18 21:03 UTC by Prasad Murthy
Modified: 2019-02-27 20:08 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Prasad Murthy 2019-01-18 21:03:39 UTC 
SUMMARY
When I tried to install vlc flatpak from flathub via discover on a live kde neon session, package installation fails without notification. Upon trying install directly via konsole, I was able to see the error message

STEPS TO REPRODUCE
1. start a live session of kde 15.15 beta using kde neon git stable iso
2. open discover
3. add flathub as flatpak source
4. search for vlc flatpak package and Install


OBSERVED RESULT
flatpak package fetched but install does not succeed and the user is not alerted by any means.


EXPECTED RESULT
Discover has to alert the user that it was not able to install the package and also if possible the error string from flatpak backend.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: KDE neon Developer Edition
Release: 18.04
Neon Version: kde neon git stable(ISO filename: neon-devedition-gitstable-20190117-1716-amd64.iso)

Kernel Version: 4.15.0-43-generic
OS Type: 64-bit

(available in About System)
KDE Plasma Version: 5.14.90
KDE Frameworks Version: 5.54.0
Qt Version: 5.11.2
Comment 1 Nate Graham 2019-01-18 21:24:35 UTC 
In this case, the problem was insufficient disk space. the Flatpak CLI said:

error: Failed to install org.kde.Platform/x86_64/5.12: min-free-space-size 500MB would be exceeded

But Discover did not display any error message.
Comment 2 Patrick Silva 2019-02-27 20:08:09 UTC 
*** This bug has been marked as a duplicate of bug 404235 ***