If I may: I don't think this is a hugely technical issue. It comes down to unintended consequences caused by the fix for bug #1747499 - while its purpose was to resolve confusing user messaging, it probably took the wrong approach.
A straightforward fix would be to:
1. Revert the changes from bug #1747499.
2. Change the "System restart required" text applied by /usr/share/update-notifier/notify-reboot-required to something more specific and user-friendly, like "System restart required to finish applying updates."
3. Change the output from canonical-livepatch kernel-upgrade-required so that it doesn't reference restarting the system. (As we've seen this month - July 2023 - the message isn't always valid anyway.) For example the text could be simply: "Livepatch has fixed kernel vulnerabilities. Kernel upgrade recommended when available."
I believe that's all that is required, although I do understand that it's complicated somewhat by the functionality being split across different packages with different people responsible, and that it involves internationalised strings.
If I may: I don't think this is a hugely technical issue. It comes down to unintended consequences caused by the fix for bug #1747499 - while its purpose was to resolve confusing user messaging, it probably took the wrong approach.
A straightforward fix would be to: update- notifier/ notify- reboot- required to something more specific and user-friendly, like "System restart required to finish applying updates." upgrade- required so that it doesn't reference restarting the system. (As we've seen this month - July 2023 - the message isn't always valid anyway.) For example the text could be simply: "Livepatch has fixed kernel vulnerabilities. Kernel upgrade recommended when available."
1. Revert the changes from bug #1747499.
2. Change the "System restart required" text applied by /usr/share/
3. Change the output from canonical-livepatch kernel-
I believe that's all that is required, although I do understand that it's complicated somewhat by the functionality being split across different packages with different people responsible, and that it involves internationalised strings.