Discover fails to fetch updates due to Fedora OCI Flatpak remotes (system,oci)

Ask Fedora
,
1

Hi!

This is my first time reporting a bug. I have been using Fedora for some time, starting from Fedora 42 Workstation, and now for the last couple of months I am using Fedora 44 KDE Desktop Edition. The experience is quite smooth, except for a recent hiccup. Whenever there is a pop-up for new update, opening Discover and checking for it keeps the “Fetching update” screen hung up indefinitely. This surfaced a few weeks ago, and I for the time being installed the updates from Konsole. However, I noticed one thing that the progress bar always stuck up while refreshing flatpaks, and thus I suspected something was wrong with the flatpak remotes.

I disabled all the repos and ran Discover again to check if the problem was solved, and voila! It sure worked. Then I turned on Flathub and checked for update and it was working well. And then, as I turned on the in-built Fedora and Fedora Testing repo, guess what: the update checking got stuck up again.

Another point I noticed is that when all the repos were active (flathub, fedora, and fedora-testing), Discover was only “seeing” the flathub repo (check the images).

I didn’t tinker any dnf/flatpak repo at all before: this was the first time I had to go through them.

1421df75-3f09-4f74-b297-c71febdb07a8
1421df75-3f09-4f74-b297-c71febdb07a81581×1134 250 KB

21b62236-6f02-4807-97a6-7b0994a4e156
21b62236-6f02-4807-97a6-7b0994a4e1561562×1065 65.9 KB

2

Most users would never use the fedora updates-testing repo since that is upcoming package updates that have not yet been released.

Similarly they would not use the fedora-testing flatpak repo for the same reasons.

On my system I have these and never see any hangups.

$ flatpak remotes
Name    Options
fedora  system,oci
flathub system,filtered
flathub user
3

I also never use the fedora/fedora-testing repo, but only download apps from flathub. Right now this is my flatpak repo status:

$ flatpak remotes
Name    Options 
flathub system 
fedora  system,oci

It is quite weird because the issue never happened all these time, and yet what I wrote is my experience. :slight_smile:

4

It would appear the error may be a result of enabling the fedora-testing flatpak repo.

5

Might be related to, https://bugs.kde.org/show_bug.cgi?id=521682

6

Seems like those reports all are related to snaps somehow. Neither do I have any snap-app installed, nor I have snapd installed. Discover also reports that snap backend is missing.

For the time being I have removed all Fedora flatpak repos, and currently have only Flathub enabled. Things are working normally.

$ flatpak remotes
Name    Options
flathub system
7

Hi, pinging once again.

There has been a small development. As I had said earlier that I had disabled the fedora and fedora-testing repos and kept only flathub enabled: this was working well. Today, for testing purposes (after running a routine weekly system update), I once again enabled those repos by running:

$ flatpak remote-add --title "Fedora Flatpaks" fedora oci+https://registry.fedoraproject.org
$ flatpak remote-add --title "Fedora Flatpaks (testing)" fedora-testing oci+https://registry.fedoraproject.org#testing

Then I went to Discover again, and I found that Discover again hung up at the “Fetching updates” screen.

I googled a bit, and then decided to run these commands as a last resort:

# Kill Frozen Backends
$ sudo pkill -f discover && sudo pkill -f packagekitd

# Clear Discover Cache
$ rm -rf ~/.cache/discover/*

# Reset AppStream Metadata
$ sudo pkcon refresh force -c 0

# Re-trigger flatpak backend
$ flatpak update

# Restart the Daemon
$ sudo systemctl restart packagekit

Re-ran Discover. All the repos are now showing correctly.

image
image1581×1134 240 KB

Also the update screen is fixed.

image
image1581×1134 103 KB

I hope this helps. Cheers! :smiley: