| Summary: | Discover Flatpak updates for applications are listed as "Refresh of version X" | ||
|---|---|---|---|
| Product: | [Applications] Discover | Reporter: | EpicTux123 <EpicTux123> |
| Component: | Flatpak Backend | Assignee: | Plasma Bugs List <plasma-bugs> |
| Status: | REPORTED --- | ||
| Severity: | normal | CC: | aleixpol, jgrulich, john.kde, nate, pbpublic, prettyvanilla, sitter, sosekeitto, travier |
| Priority: | NOR | ||
| Version First Reported In: | 6.1.3 | ||
| Target Milestone: | --- | ||
| Platform: | Fedora RPMs | ||
| OS: | Linux | ||
| See Also: |
https://bugs.kde.org/show_bug.cgi?id=464128 https://bugs.kde.org/show_bug.cgi?id=501188 |
||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: |
breeze gtk theme update from discover
App versions on Discover |
||
|
Description
EpicTux123
2024-08-05 21:06:23 UTC
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.
I'm also having this problem, as I reported at https://old.reddit.com/r/kde/comments/1hrw56i/discover_insists_on_offering_flatpak_refreshes. I'm on MX Linux 23 (Debian bookworm), using KDE Plasma v: 5.27.5 and Discover 5.27.5. I keep getting Refresh offerings from flathub, and they are large, typically 360MB or more. Most of them seem to be some kind of system files. One speech to text program was just short of 1GB. I even get these when I disabled all my flathub repos. I'm not interested in these refreshes, especially when they are so large. This started maybe 3 months ago. The number of refreshes have been increasing daily, so I did a little poking around. I have three flathub repos, flathub, user, and beta. All were disabled. I enabled them, and then about a dozen refreshes presented themselves. Then I disabled them again, and ZERO showed, even after refreshing the Updates tab. But this morning it's back to showing four offered refreshes, worth about 1.3GB. There seems to be a problem with the disabling of repos. This needs more research I guess. I'm currently wading through 2.6GB of nonsense "Refresh" entries from flathub. They do not show up on either Synaptic or MX Package Installer. https://i.postimg.cc/YCDCF25K/2025-02-14-36.png I think this problem is related to https://github.com/flatpak/flatpak/issues/5974 which is that flatpak doesn't always update version numbers even when the version numbers should change. Discover therefore sees the same version number and so presents this as a "refresh" when actually it isn't. Doing "flatpak update --appstream" will fix the problem, until the next update. Maybe Discover can do that for us when refreshing? Until the upstream issue is fixed anyway. (In reply to John Veness from comment #12) > I think this problem is related to > https://github.com/flatpak/flatpak/issues/5974 which is that flatpak doesn't > always update version numbers even when the version numbers should change. > Discover therefore sees the same version number and so presents this as a > "refresh" when actually it isn't. John, if that were so, that actual updates had been made, then wouldn't other package handlers offer the updates as such? That hasn't been happening here. (In reply to Paul B. from comment #13) > John, if that were so, that actual updates had been made, then wouldn't > other package handlers offer the updates as such? That hasn't been happening > here. Assuming you mean the updates aren't showing up in Synaptic or MX Package Installer, I don't know about MX Package Installer but Synaptic only shows apt updates, not flatpaks. (In reply to John Veness from comment #14) > (In reply to Paul B. from comment #13) > > John, if that were so, that actual updates had been made, then wouldn't > > other package handlers offer the updates as such? That hasn't been happening > > here. > > Assuming you mean the updates aren't showing up in Synaptic or MX Package > Installer, I don't know about MX Package Installer but Synaptic only shows > apt updates, not flatpaks. It appears you are correct about Synaptic. MX Package Installer has a tab devoted to Flatpaks. Here is a copy of its Flatpak settings, including the "remote" it uses: https://i.postimg.cc/0yx1Qdyw/2025-03-06-31.png |
