[FFe] plasma-distro-release-notifier for Ubuntu Studio and Kubuntu
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
kubuntu-meta (Ubuntu) |
Fix Released
|
Undecided
|
Rik Mills | ||
Kinetic |
Fix Released
|
Undecided
|
Rik Mills | ||
ubuntustudio-meta (Ubuntu) |
Fix Released
|
High
|
Erich Eickmeyer | ||
Kinetic |
Fix Released
|
High
|
Erich Eickmeyer |
Bug Description
plasma-
Currently, users are not prompted when a new version of Ubuntu is released, and as such, users of the Plasma desktop (Ubuntu Studio and Kubuntu) get stuck on an EOL release very quickly. I have seen several posts on #kubuntu and Reddit requesting help because the user simply did not know that they needed to update their machine to a newer release. Including this package would prevent that.
Tests on 20.04 using the same package have been successful, with not only a notification, but also a tray icon indicating that the upgrade is available.
The intention will be, once through this FFe process, to backport the package via SRU to 22.04. A stretch goal would be to backport the same package to Kubuntu 20.04 through the same process as it is still supported until April 2023 and many users there are not getting the prompt to upgrade.
As of this writing, plasma-
Changed in ubuntustudio-meta (Ubuntu Kinetic): | |
milestone: | none → ubuntu-22.10-beta |
description: | updated |
summary: |
- [FFe] plasma-distro-release-notifier for Ubuntu Studio + [FFe] plasma-distro-release-notifier for Ubuntu Studio and/or Kubuntu |
Changed in kubuntu-meta (Ubuntu Kinetic): | |
assignee: | nobody → Rik Mills (rikmills) |
milestone: | none → ubuntu-22.10-beta |
description: | updated |
summary: |
- [FFe] plasma-distro-release-notifier for Ubuntu Studio and/or Kubuntu + [FFe] plasma-distro-release-notifier for Ubuntu Studio and Kubuntu |
Changed in ubuntustudio-meta (Ubuntu Kinetic): | |
status: | Triaged → Fix Committed |
Changed in kubuntu-meta (Ubuntu Kinetic): | |
status: | Triaged → Fix Committed |
Status changed to 'Confirmed' because the bug affects multiple users.