Continuation of issue https://bugs.kde.org/show_bug.cgi?id=464128. Updates to Flatpak applications are listed on Plasma Discover as "Refresh of version X", when they are, actually, normal updates and not just refresh of libraries/runtimes used to compile the Flatpak. Example: "Mahjong Game" from Flatpak needs the "cards library" ("libcards"). "Mahjong Game" is on version 1.0. "libcards" is on version 1.1. Then it gets an update to version 1.2. "Mahjong Game" itself does not get any new features, but the mantainer goes and update "libcards" to version 1.2. In this situation, the word "refresh" would be appropriate, because the game was not updated, only the library used to compile the game was. But I don't believe Discover can differentiate between an actual refresh vs. an actual update (with new features) from the game. If "Mahjong Game" was updated to version 1.1, Discover would still show it as "Refresh of version X". And I know it because most (if not all) updates to Flatpak applications I have downloaded are only called "Refresh of version X", even if it's an actual update. In the linked issue, Nate asked me for a screenshot of the problem (showing Discover). I can't provide one currently since I don't have anything to update. However, I can say it is the same content as the attachment present in the other issue (https://bugsfiles.kde.org/attachment.cgi?id=155202); the only difference are app names and versions. I can attest an actual update shows "Refresh of version X" because today I updated OpenRCT2 (https://github.com/OpenRCT2/OpenRCT2) from Flathub and it showed "Refresh of version 0.4.12", when it was actually updating to version 0.4.13. Also, the command "flatpak history" shows "deploy update" (does not mention any "refresh" for any update from all of my history). OpenRCT2 team released an update yesterday: https://github.com/OpenRCT2/OpenRCT2/releases/tag/v0.4.13 Flathub app was updated today: https://github.com/flathub/io.openrct2.OpenRCT2/commit/2e8e7429eccc45e2562acc3a293d9e2968845814 I believe the simplest solution would be just to rename "Refresh of version" to "Update to version", and also show the new version (as dictated by the manifest file from Flathub) instead of the current version. So, for example, instead of getting "Refresh of version 0.4.12" for OpenRCT2, I would get "Update to vresion 0.4.13". SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora Linux 40 KDE Plasma Version: 6.1.3 KDE Frameworks Version: 6.4.0 Qt Version: 6.7.2
Please attach your own screenshot.
Hello, I'll attach an screenshot next time I have an update.
According to the code this only can happen if the available version and the installed version are already the same.
That's what I was getting at, yeah.
Created attachment 172362 [details] breeze gtk theme update from discover Hello. I had an update today for "Breeze GTK Theme". I have attached a screenshot from Discover. "flatpak list" command before the update: Breeze GTK theme org.gtk.Gtk3theme.Breeze 6.1.3 3.22 system "flatpak list" command after the update: Breeze GTK theme org.gtk.Gtk3theme.Breeze 6.1.4 3.22 system "flatpak history" shows: ago 6 19:45:49 deploy update org.gtk.Gtk3theme.Breeze 3.22 system flathub "Breeze GTK Theme" was updated today to version 6.1.4: https://github.com/flathub/org.gtk.Gtk3theme.Breeze/commits/master/
Looks to me the appstream cache may only be reporting the installed version, not the candidate version.
Created attachment 172605 [details] App versions on Discover Interesting fact: Some apps report as "Applications" instead of "System Software", and those correctly display the candidate version.