Comment 8 for bug 2017401

Regardless I'm not sure if this provides any additional information/context, I faced this issue during using Cloudron.io as a paying customer (see forum thread https://forum.cloudron.io/topic/9720/reboot-for-security-updates-broken-on-livepatch/) on our Ubuntu 22 LTS server. So the current bug/change in behavior has a productive impact: Due to this, Cloudron doesn't detect anymore that a reboot is required for patching the OS and thus no notification is shown to the admin of the Cloudron instance. The workaround is to logon via shell onto the server and see the reboot hint in the welcome message.