Bug 400389 - Discover shows no progress during flatpak transactions
Summary: Discover shows no progress during flatpak transactions
Status: RESOLVED UPSTREAM
Alias: None
Product: Discover
Classification: Applications
Component: Flatpak Backend (show other bugs)
Version: 5.14.2
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Aleix Pol
URL:
Keywords:
: 401785 (view as bug list)
Depends on:
Blocks:
 
Reported: 2018-10-28 01:11 UTC by Patrick Silva
Modified: 2018-12-14 18:38 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Patrick Silva 2018-10-28 01:11:25 UTC 
STEPS TO REPRODUCE
1. open Discover
2. click "Installed" in the side bar
3. choose some app installed via flatpak and uninstall it by clicking "Remove" buton

OBSERVED RESULT
Progress bar does not work and the side bar shows "Task 0%" while the flatpak
is uninstalled.

EXPECTED RESULT
progress bar works, side bar indicates the progress correctly.

SOFTWARE VERSIONS
Arch Linux
KDE Plasma Version: 5.14.2
KDE Frameworks Version: 5.51
Qt Version: 5.12 beta3

ADDITIONAL INFORMATION
Also reproducible on neon dev unstable.
Comment 1 Patrick Silva 2018-10-28 02:10:26 UTC 
Also there is no progress during installation.
Comment 2 Aleix Pol 2018-10-29 13:30:50 UTC 
This is fixed in master which will be in 5.15.

Sorry for the inconvenience.
Comment 3 Patrick Silva 2018-11-27 16:29:05 UTC 
(In reply to Aleix Pol from comment #2)
> This is fixed in master which will be in 5.15.
Are you sure?
Bug persists on neon dev unstable.
Is a newer flatpak required?
Neon uses flatpak 1.0.1.
Comment 4 Patrick Silva 2018-12-06 17:08:05 UTC 
*** Bug 401785 has been marked as a duplicate of this bug. ***
Comment 5 Aleix Pol 2018-12-13 04:06:33 UTC 
Yes, I'm pretty sure it's a bug on Flatpak. It keeps reporting 100 as percentage. Will have to report properly.
Comment 6 Aleix Pol 2018-12-13 14:34:18 UTC 
https://github.com/flatpak/flatpak/issues/2428
Comment 7 Aleix Pol 2018-12-14 18:38:16 UTC 
Just landed a patch in libflatpak that will enter on their next release that should fix this issue.