Created attachment 145998 [details]
The screenshot shows that only the "Software & Updates" component shows EOL information.
it would be helpful, if the package updater would notify the user, if there are no more security updates. I think this would be inline with the user's expectation, since there are system notifications when there are regular updates (both for manually and automatically performed "apt update"). Only the "Software & Updates" component shows EOL information.
I presume that issues exists for the current Kubuntu versions as well.
In my case, I missed the EOL announcement online and only noticed because I was wondering why no update was coming to fix CVE-2021-4034.
Operating System: Kubuntu 21.04
KDE Plasma Version: 5.21.4
KDE Frameworks Version: 5.80.0
Qt Version: 5.15.2
Kernel Version: 5.11.0-49-generic
OS Type: 64-bit
Graphics Platform: X11
Processors: 8 × Intel® Core™ i7-4800MQ CPU @ 2.70GHz
Memory: 15.5 GiB of RAM
Graphics Processor: Mesa DRI Intel® HD Graphics 4600
Is anyone aware of (hopefully standard) ways to know if distros are EOL?
In Debian/Ubuntu, the utility 'distro-info' (package 'distro-info') can be used to list the currently supported releases with 'distro-info --supported'. Alternatively the package 'distro-info-data' provides .csv files with the support dates of each release from Ubuntu and Debian.
A possibly relevant merge request was started @ https://invent.kde.org/plasma/discover/-/merge_requests/249
Git commit 01ca64c0144a3bcbe48ed3e732eab94f7b76b24a by Aleix Pol Gonzalez, on behalf of Aleix Pol.
Committed on 21/02/2022 at 15:56.
Pushed by apol into branch 'master'.
pk: Tell our users when they're running an unsupported version of their Distro
M +5 -0 discover/qml/DiscoverPage.qml
M +8 -0 discover/qml/DiscoverWindow.qml
M +19 -0 libdiscover/backends/PackageKitBackend/PackageKitBackend.cpp
M +9 -0 libdiscover/resources/AbstractResourcesBackend.h
M +1 -0 libdiscover/resources/ResourcesModel.cpp
M +1 -0 libdiscover/resources/ResourcesModel.h
*** Bug 450877 has been marked as a duplicate of this bug. ***