Confusing EOL messages are unactionable #3531
Comments
|
This message is set by the runtime: https://gitlab.gnome.org/GNOME/gnome-build-meta/ |
|
@da2x if your still seeing this message, one thing that removed it for me was uninstalling unused I really do agree though that flatpak should do something better to handle end of life for runtimes/apps. |
|
I stumbled upon the same issue. I think a more actionable message would be including the command you need to run to see the list of affected applications: "To see the list of affected applications, please run |
|
I'm on EndeavorOS and receiving the same message. On top that the one command returns nothing, but as you can see I have an extensive list of installed flatpaks. EDIT: fixed the command for 3.34 vs 3.32 and I get: |
|
I'm getting something like this myself: I can't tell why |
|
@HugLifeTiZ it seems flatpak doesn't remove old dependencies automatically you have to run |
That does nothing. It doesn't recognize it as "unused", which kind of tracks with the fact that something keeps pulling it back in every time I update. |
|
flatpak update flatpak list --app-runtime=org.freedesktop.Sdk//18.08 Please advise |
|
I'm running into the issue with 18.08 on Garuda Gaming an Arch based distro. Any suggestions on fixing? Thanks |
|
@HugLifeTiZ Same here, now with 19.08, did you find a solution? |
Using |
|
@fdaciuk |
|
What I ended up doing was |
> Please advise What I found works, and submit for sanity review to this august body... flatpak uninstall org.freedesktop.Sdk//19.08 where "org.freedesktop.Sdk//19.08" is the first thing giving one a problem. Then... flatpack update Looking for updates…
Uninstall complete. flatpak update Thoughts? |
|
This is bonkers. When I do When I then try to explicitly uninstall them via: It uninstalls them alright but when I then do IT WANTS TO REINSTALL THEM. I also don't get why update still tells me they are end-of-life when they are uninstalled. If I just abort this with So somehow this system is so in love with these packages that it just cannot get over them. |
|
Just a technical note for when this is being implemented, we can use |
|
Finally I could find a workaround on my machine: Still no clue on what pulled them in, just noticed the mirage repository was not working anymore in a |
|
I had the same problem on my system regarding the packages First I tried to uninstall the unused packages: Unfortunately, the unused packages had a different version (20.08) than the problematic ones (19.08) and thus, the warnings were still present when performing Then I manually installed the latest version of The last command also uninstalled the other problematic packages: After that, the warnings were gone: Hope this helps. |
|
I am still seeing
Both of these commands show nothing
|
|
@dik23 good luck in getting anyone to actually address this issue. I and at least 3 others that I know of have asked about how to fix this and if the codec pack is even needed. I use Topgrade to update everything and when it gets to the Flatpak section if this is installed it uninstalls it, if it's not installed it installs it. Doesn't seem to be hurting anything on the system, but would still be nice to get it fixed so we can stop receiving the message. |
|
First find which platform pulls outdated extension as dependency: Then then you can check which apps depends on that platform and optionally uninstall them later: Also only removing platform should tell you which apps use it: |
|
@konradmb Thank you so much for this! Helped me knock out the app that pinned it down for me: Kdenlive (from the flathub-beta repo). It depended on the 5.12 Plasma SDK which pulled in the html5-codecs runtime |
|
Unfortunately this issue has become a thread where people discuss related but distinct issues, and it's hard to make progress on it without disentangling them. Here's a shot at that:
|
Filed https://invent.kde.org/packaging/flatpak-kde-runtime/-/issues/32 |
I think the "app//branch" syntax is pretty ugly, and maybe not all users understand it. Helps: #3531
Currently if a runtime extension, e.g. org.freedesktop.Platform.html5-codecs//18.08 is used by a runtime org.kde.Platform//5.12 which itself is used by one or more apps, when we print a message to the user about html5-codecs being EOL, we don't find any apps using it and don't print any. Fix this by including apps that indirectly use a runtime extension in the "Applications using this runtime:" list. In a later commit we can re-use the helper function added here to add a confirmation dialog if the user tries to remove a runtime extension that's being used; currently we just let them remove it. This is limited to only looking in the current flatpak installation, so a per-user app using a system-wide runtime extension would not be found. Helps: #3531
Currently if a runtime extension, e.g. org.freedesktop.Platform.html5-codecs//18.08 is used by a runtime org.kde.Platform//5.12 which itself is used by one or more apps, when we print a message to the user about html5-codecs being EOL, we don't find any apps using it and don't print any. Fix this by including apps that indirectly use a runtime extension in the "Applications using this runtime:" list. In a later commit we can re-use the helper function added here to add a confirmation dialog if the user tries to remove a runtime extension that's being used; currently we just let them remove it. This is limited to only looking in the current flatpak installation, so a per-user app using a system-wide runtime extension would not be found. Helps: #3531
Currently if a runtime extension, e.g. org.freedesktop.Platform.html5-codecs//18.08 is used by a runtime org.kde.Platform//5.12 which itself is used by one or more apps, when we print a message to the user about html5-codecs being EOL, we don't find any apps using it and don't print any. Fix this by including apps that indirectly use a runtime extension in the "Applications using this runtime:" list. In a later commit we can re-use the helper function added here to add a confirmation dialog if the user tries to remove a runtime extension that's being used; currently we just let them remove it. This is limited to only looking in the current flatpak installation, so a per-user app using a system-wide runtime extension would not be found. Helps: #3531
Great! I also used it to remove |
I think the "app//branch" syntax is pretty ugly, and maybe not all users understand it. Helps: #3531
I think the "app//branch" syntax is pretty ugly, and maybe not all users understand it. Helps: #3531
Currently if a runtime extension, e.g. org.freedesktop.Platform.html5-codecs//18.08 is used by a runtime org.kde.Platform//5.12 which itself is used by one or more apps, when we print a message to the user about html5-codecs being EOL, we don't find any apps using it and don't print any. Fix this by including apps that indirectly use a runtime extension in the "Applications using this runtime:" list. In a later commit we can re-use the helper function added here to add a confirmation dialog if the user tries to remove a runtime extension that's being used; currently we just let them remove it. This is limited to only looking in the current flatpak installation, so a per-user app using a system-wide runtime extension would not be found. Helps: #3531
Currently if a runtime extension, e.g. org.freedesktop.Platform.html5-codecs//18.08 is used by a runtime org.kde.Platform//5.12 which itself is used by one or more apps, when we print a message to the user about html5-codecs being EOL, we don't find any apps using it and don't print any. Fix this by including apps that indirectly use a runtime extension in the "Applications using this runtime:" list. In a later commit we can re-use the helper function added here to add a confirmation dialog if the user tries to remove a runtime extension that's being used; currently we just let them remove it. This is limited to only looking in the current flatpak installation, so a per-user app using a system-wide runtime extension would not be found. Helps: #3531
Currently if a runtime extension, e.g. org.freedesktop.Platform.html5-codecs//18.08 is used by a runtime org.kde.Platform//5.12 which itself is used by one or more apps, when we print a message to the user about html5-codecs being EOL, we don't find any apps using it and don't print any. Fix this by including apps that indirectly use a runtime extension in the "Applications using this runtime:" list. In a later commit we can re-use the helper function added here to add a confirmation dialog if the user tries to remove a runtime extension that's being used; currently we just let them remove it. This is limited to only looking in the current flatpak installation, so a per-user app using a system-wide runtime extension would not be found. This is implemented using in-memory caches because otherwise it is horribly slow; see #4835 (comment) Helps: #3531
Currently if a runtime extension, e.g. org.freedesktop.Platform.html5-codecs//18.08 is used by a runtime org.kde.Platform//5.12 which itself is used by one or more apps, when we print a message to the user about html5-codecs being EOL, we don't find any apps using it and don't print any. Fix this by including apps that indirectly use a runtime extension in the "Applications using this runtime:" list. In a later commit we can re-use the helper function added here to add a confirmation dialog if the user tries to remove a runtime extension that's being used; currently we just let them remove it. This is limited to only looking in the current flatpak installation, so a per-user app using a system-wide runtime extension would not be found. This is implemented using in-memory caches because otherwise it is horribly slow; see #4835 (comment) Helps: #3531
Currently if a runtime extension, e.g. org.freedesktop.Platform.html5-codecs//18.08 is used by a runtime org.kde.Platform//5.12 which itself is used by one or more apps, when we print a message to the user about html5-codecs being EOL, we don't find any apps using it and don't print any. Fix this by including apps that indirectly use a runtime extension in the "Applications using this runtime:" list. In a later commit we can re-use the helper function added here to add a confirmation dialog if the user tries to remove a runtime extension that's being used; currently we just let them remove it. This is limited to only looking in the current flatpak installation, so a per-user app using a system-wide runtime extension would not be found. This is implemented using in-memory caches because otherwise it is horribly slow; see #4835 (comment) Helps: #3531
Currently if a runtime extension, e.g. org.freedesktop.Platform.html5-codecs//18.08 is used by a runtime org.kde.Platform//5.12 which itself is used by one or more apps, when we print a message to the user about html5-codecs being EOL, we don't find any apps using it and don't print any. Fix this by including apps that indirectly use a runtime extension in the "Applications using this runtime:" list. In a later commit we can re-use the helper function added here to add a confirmation dialog if the user tries to remove a runtime extension that's being used; currently we just let them remove it. This is limited to only looking in the current flatpak installation, so a per-user app using a system-wide runtime extension would not be found. This is implemented using in-memory caches because otherwise it is horribly slow; see #4835 (comment) Helps: #3531
This was fixed by #4835 |
These two things are perhaps what's remaining on this issue, but since they don't have well-defined solutions yet, and it's not even clear they are accurate descriptions of user experiences, this issue will stall until we have those things. |
Not... quite (I found this issue googling solutions to the EOL message and my problem was neither of these two) Let me start by pasting my terminal and what I was thinking working through it. A paraphrase of my internal narrative as I did this:
~ ~ fin ~ ~ Full terminal, start to end, without my narrative: |
|
I think the concepts of alarm fatigue and banner blindness should be taken into consideration here. I have a flood of these sorts of messages that appear before I run anything. Are some of them actionable? Yes... but I never read them anymore because they're buried in a flood of messages from applications that are just a little bit slow in upgrading to the latest version of their particular runtime. The only reason I know some are actionable is that I assume one of them still says this: (No, thank you. I'd rather have jstest-gtk with my customized (tightened) Flatpak sandbox than to have to manage the APT version plus Firejail. Installing yet another package manager is not an option I'm willing to consider... though after I upgrade to Kubuntu 24.04 LTS, I'll reconsider whether the KDE gamepads control panel is now acceptable.) Just as Raymond Chen described how Microsoft tried very hard to avoid popups that would train people to just click Yes without reading to get past the "noise", Flatpak needs to re-think this feature. These days, I almost literally see this: Hell, I've been considering writing a wrapper that functions as a multi-line-aware |
Linux distribution and version
Fedora 31
Flatpak version
1.4.4
Whenever I run
flatpak updateI get these un-actionable info messages:The action I’m asked to make is to contact an application developer. But who should I contact? The message doesn’t even tell me which apps use this runtime and there is no info provided to let me identify affected apps or their developers’ contact information.
These errors needs to include a list of affected applications. Armed with this information, I could lookup the app developer’s website and find their contact information.
The text was updated successfully, but these errors were encountered: