Bug 471548 - Auto-Update for flatpaks, via Discover appears to be non-functional
Summary: Auto-Update for flatpaks, via Discover appears to be non-functional
Status: CONFIRMED
Alias: None
Product: Discover
Classification: Applications
Component: Flatpak Backend (show other bugs)
Version: 5.27.6
Platform: openSUSE Linux
: NOR major
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
: 472908 (view as bug list)
Depends on:
Blocks:
 
Reported: 2023-06-28 21:04 UTC by Shawn W Dunn
Modified: 2023-08-17 06:36 UTC (History)
7 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
logs of manual run of plasma-discover-update via journalctl (2.37 KB, text/plain)
2023-06-28 21:04 UTC, Shawn W Dunn
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Shawn W Dunn 2023-06-28 21:04:45 UTC
Created attachment 159962 [details]
logs of manual run of plasma-discover-update via journalctl

SUMMARY
On openSUSE Kalpa, we only use Discover to handle the installation and management of flatpaks and fwupd, setting Updates to run Automatically in the "Software Update" kcm appears to work fine for fwupd, but is non-functional for flatpak/flathub

STEPS TO REPRODUCE
1. Enable flathub repository
2. Install some flatpaks
3. Set to automatically update software daily in the "Software Update" kcm

OBSERVED RESULT
Flatpaks do not get updated automatically.   The Notification that updates are available works just fine, but there is no automatic download and installation of them.

EXPECTED RESULT
Discover checks for updates of flatpaks from enabled repositories, downloads, and installs them, on a daily schedule

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: openSUSE Kalpa 20230625 (Linux 6.3.9-1-default)
KDE Plasma Version: 5.27.6
KDE Frameworks Version: 5.107.0
Qt Version: 5.15.10

ADDITIONAL INFORMATION
Running `plasma-discover-update` manually in a terminal produces the expected output.  Please see attached logs.
Comment 1 Nate Graham 2023-08-02 20:49:31 UTC
*** Bug 472908 has been marked as a duplicate of this bug. ***