https://bugs.kde.org/show_bug.cgi?id=436227
--- Comment #5 from guimarcalsi...@gmail.com --- This is a valid bug report and in the current state, offline updates represent a UX problem, specially in a distro like Neon that updates frequently. I do agree that it's important to have the system reboot in some situations to improve stability. The real problem is the amount of reboots and that not all package updates need a reboot. You will probably want to restart to apply a Plasma or Kernel update, but it's not a good experience to expect the user to restart to update Firefox or Kate. I don't know if this already exists, and if it does, support for it should be included in Discover, but in order to differentiate between system updates that need a reboot and ordinary app updates, I believe it would be ideal to have a multi-format standard where .deb/.rpm packages get a tag that tells Discover if they require a reboot to be installed. This tag would then be set for packages by packagers based on some criteria, like if it's a system package, a security update, or for some other technical reason. This should probably be proposed upstream and when/if support lands, Discover should be able to read that tag and prompt for a reboot based on it. This would be the best option, as it would seriously reduce the need for reboots and thus improve UX, while still making important system updates less bug prone. Does any developer know where this could be discussed upstream? I could file a feature request for such functionality. -- You are receiving this mail because: You are watching all bug changes.
