Comment 13 for bug 1998947

> Currently, update-notifier will display the notification even if update-manager's previous notification is still open.

To expand on this, I believe that currently both unattended-upgrades and update-manager run by default on Desktop. I also think it must be fairly common for users to leave their systems for periods of time while they remain logged in, especially for example if a user sets off updates through update-manager before leaving for a break. Therefore, this proposed update will result in two reboot prompts appearing on the screen at once (one from update-notifier and one from update-manager). This seems like a significant UX regression to me that could be expected to affect a wide set of users, while providing relatively little benefit for the majority of users, so doesn't seem acceptable for SRU as-is.

Therefore I'm rejecting this upload from the queue. If after discussion you are able to persuade the SRU team otherwise, then we can accept directly from the rejected queue.

It also seems like this would be a UX regression between Lunar and Mantic given this change is already uploaded into Mantic, so I'll file a bug for that.

> The main rationale for this is that we needed to enable this for a special jammy-based customer and we do not want this functionality to regress whenever a new update-notifier is released.

I suggest using a recipe build against the git-ubuntu branch to keep a PPA updated. This technique can often work with no intervention required to maintain a patched local package, even merging in security updates - though it would still need monitoring and the occasional merge conflict resolving manually.