https://bugs.kde.org/show_bug.cgi?id=435574
--- Comment #42 from Sadi <sadiyumu...@gmail.com> --- I can't believe that one year has elapsed since this issue was reported without any move towards some solution,y improvement etc. while a lot of development effort is being spent on many cosmetic enhancements here and there. I wish I had some programming skills to contribute to development. Isn't it possible to determine of all the packages installed which ones have some component running when the user logged in? Then, any pending package update could be compared with such a list to decide if any update should better be performed after the user logs off, and even as another level, after the computer reboots. Furthermore, some processes/apps started after the user logged in may just need to be stopped and restarted after an update affecting them is performed without even logging off. This sounds quite logical to me, although I'm also prepared to accept that this is just due to my complete ignorance in programming, in which case I apologize for my impatience. I can of course continue looking at the list first and make that decision myself and then performing some updates by quitting Discovery and launching my package manager... -- You are receiving this mail because: You are watching all bug changes.
