https://bugs.kde.org/show_bug.cgi?id=445503
--- Comment #11 from Nate Graham <n...@kde.org> --- To avoid weirdness, you always need to restart an app that was running when it was updated, or when any of the libraries that it uses are updated. Let's say we added a system to compare the list of updated packages with the list of running software and its library dependencies, and if there was any intersection between the two lists, we sent a notification asking people to reboot the system or those apps after updating. I think this would not solve the problem because Discover *already* asks you to reboot after updating, and evidently you ignored that notification. :) Discover already told you what you needed to do, but it was up to you to do it. Offline Updates solves this entire problem generically by not actually applying any of the pending updated until a reboot is done. -- You are receiving this mail because: You are watching all bug changes.
