Why does Bottles want to continually update to 67.2 in the Software App?

Is there any reason Bottles wants to continually update after I have run the update in the Software App/Store a few times?

I already have Bottles version 67.2 installed - see output below from terminal command flatpak list --show-details

Gnome updater's implementation of the Flatpak plugin is a bit spotty. I would suggest running the full flatpak update command in terminal, then reboot and see if that quiets Gnome Software down.
IF you prefer to not reboot, then killing the gnome-updater, then restarting it is viable, too.

Thanks... would you happen to have the terminal command(s) for the full flatpak update command in terminal? :grin:

This one is actually an easy one to remember:

flatpak update

1 Like

Thanks!

I got a streaming error when running the command:

scott@scott-Falcon-Talon:~$ flatpak update
Looking for updates…

    ID                                                Branch                 Op            Remote             Download
  1. [✗] org.freedesktop.Platform.GL32.default 26.08 i flathub 12.6 MB / 158.2 MB
  2. [✗] org.freedesktop.Platform.GL32.default 26.08-extra i flathub 11.6 MB / 158.3 MB

Warning: While pulling runtime/org.freedesktop.Platform.GL32.default/x86_64/26.08 from remote flathub: While fetching https://dl.flathub.org/repo/objects/94/6c2b5c57340e5c6b6a8e13f881976167d28161e42c45d5d6876cbeba64fb66.filez: [92] Stream error in the HTTP/2 framing layer
Warning: While pulling runtime/org.freedesktop.Platform.GL32.default/x86_64/26.08-extra from remote flathub: While fetching https://dl.flathub.org/repo/objects/94/6c2b5c57340e5c6b6a8e13f881976167d28161e42c45d5d6876cbeba64fb66.filez: [92] Stream error in the HTTP/2 framing layer
Installation complete.

That explains where the problem is. It could be a server error.
But you could try

flatpak repair

just in case...

Other than that - flatpak users can only wait on a maintainer fix.

Thanks again!

I believe you are correct that this is most likely a server error and will need maintainer fix as others have reported the same issue on Reddit.

See screen-shot:

All good and working now! :grinning_face_with_smiling_eyes:

2 Likes