Why does it not exist in the repositories?
Are you sure you’re not looking for plasma-discover-flatpak?
Name : plasma-discover-flatpak
Epoch : 0
Version : 6.2.5
Release : 1.fc41
Architecture : x86_64
Download size : 221.0 KiB
Installed size : 614.5 KiB
Source : plasma-discover-6.2.5-1.fc41.src.rpm
Repository : updates
Summary : Plasma Discover flatpak support
URL : https://invent.kde.org/plasma/discover
License : BSD-3-Clause AND CC0-1.0 AND GPL-2.0-only AND GPL-2.0-or-later AND GPL-3.0-only AND LGPL-2.0-or-later AND LGPL-2.1-only AND LGPL-3.0-only AND (GPL-2.0-
: only OR GPL-3.0-only) AND (LGPL-2.1-only OR LGPL-3.0-only)
Description : Plasma Discover flatpak support.
Vendor : Fedora Project
plasma-discover-flatpak is so that flatpak can be installed and searched for in discover.
but plasma-discover-backend-flatpak is so that discover updates flatpak automatically without asking, and it is not in the fedora repositories.
As I do understand it is pakagekit which is integrating flatpak , right ?
You can search for flatpak in discover and see the backend.
If you remove plasma-discover-flatpak it shows the backend removed in discover.
Yes for discover and for gnome-software.
It doesn’t work, it doesn’t update
Please check the settings as shown below. On the live ISO the automatic update is not activated. You have to do this by hand. Please check how it is after installation:
The application for flatpaks is plasma-discover-packagekit.x86_64
: Plasma Discover PackageKit support
Which is interface the for the dnf and flatpak transactions. In the settings of Discover app you can activate or deactivate, as Flathub and or Testing as an example.
PackageKit has no support for Flatpak. GNOME Software and KDE Discover use libflatpak directly.
Where are you getting this information? As far as I know, these are just different names for the same package. Comparing plasma-discover-backend-flatpak from Debian to plasma-discover-flatpak in Fedora, I see basically the same contents.
It looks like this functionality was broken recently, but Discover 6.2.4+ should have the fix, so I don’t know why it’s not working.
I think we should give this topic a solution, and create a new one, to debug the issue which still exists.
The topic asks the question of an in-existent package on RHEL distributions. While the Package name comes from Debian based systems.
A topic with the title “How to debug Flatpak issues while using Discover or Gnome Software?”
Would be much more usable for the whole community, to understand the interactions, in between “Discover/Gnome Software” and Flatpak.
I guess when it is with lib-flatpak there are API calls which do make changes direct in Flatpak? So we would have to Debug direct in Flatpak to see if there are wrong configurations/settings?
@sakunix if you updated your system to the latest versions and you still get Flatpak update issues, think about a new topic with the mentioned title.
To check on flatpak side, if there are some miss-configurations you could use commands like:
# please use each command separately, line by line, otherwise the additional information -vv will not be shown.
flatpak mask -vv
flatpak config -vv
flatpak list -vv
flatpak repair --dry-run -vv
Discover is responsible for setting and implementing any auto-update policy for Flatpak. It’s conceptually the same as a timer that runs flatpak update
periodically (but using the API instead).
I think the only thing worth checking on the Flatpak side is to see if a manual flatpak update
succeeds.
Perhaps the problem persists due to good old 447245 – Auto updates do not work, which I think is only fixed (well, partially anyway) in plasma 6.3.
on openSUSE it works fine