Bug 426729 - Discover refuses to update packages from Gnome Nightly flatpak remote
Summary: Discover refuses to update packages from Gnome Nightly flatpak remote
Status: RESOLVED DUPLICATE of bug 417078
Alias: None
Product: Discover
Classification: Applications
Component: Flatpak Backend (show other bugs)
Version: unspecified
Platform: Neon Linux
: NOR normal
Target Milestone: ---
Assignee: Dan Leinir Turthra Jensen
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-09-19 14:02 UTC by Patrick Silva
Modified: 2020-12-10 14:42 UTC (History)
3 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Patrick Silva 2020-09-19 14:02:41 UTC
STEPS TO REPRODUCE
1. add Gnome Nightly flatpak remote
https://wiki.gnome.org/Apps/Nightly
2. install some app from this remote (I installed Sound Recorder)
3. wait for a update to a runtime from Gnome Nightly flatpak remote
and try to install it via Discover

OBSERVED RESULT
Discover does not update the runtime and shows unhelpful "Aborted due to failure"
error message. However, the same remote can be updated via Konsole with "flatpak update". Furthermore, Discover updates runtimes from flathub remote as expected.

EXPECTED RESULT
Discover should update runtimes from any flatpak remote

SOFTWARE/OS VERSIONS
Operating System: KDE neon Unstable Edition
KDE Plasma Version: 5.19.90
KDE Frameworks Version: 5.75.0
Qt Version: 5.15.0
Comment 1 Patrick Silva 2020-11-09 10:13:54 UTC
Sound Recorder app is also not updated.

Operating System: KDE neon Unstable Edition
KDE Plasma Version: 5.20.80
KDE Frameworks Version: 5.76.0
Qt Version: 5.15.0
Comment 2 Patrick Silva 2020-12-10 13:47:12 UTC
Currently I also can not install packages from Gnome Nightly flatpak remote.
Discover just says "Aborted due to failure".

Operating System: KDE neon Unstable Edition
KDE Plasma Version: 5.20.80
KDE Frameworks Version: 5.77.0
Qt Version: 5.15.2
Comment 3 Nate Graham 2020-12-10 14:42:35 UTC
*** This bug has been marked as a duplicate of bug 417078 ***