https://bugs.kde.org/show_bug.cgi?id=445503
--- Comment #12 from Edmund Laugasson <edmund.laugas...@protonmail.ch> --- You as a developer possibly know, which component is binded with which app. But most users and admins do not know that, at least not in complete extent. We may know some components, but not all of them. Therefore it is solely on developer's duty to pay enough attention during upgrade, when restarting plasmashell, logging off or even rebooting is necessary. To be honest, it isn't very hard to announce it in a noticeable way, so it won't be missed. E.g. in EndeavourOS there will be always message on CLI and if in GUI, pop-up says, that rebooting necessary. Such messaging isn't hard but would help avoid lots of troubles unless user, admin understands, that rerunning plasmashell, relogin or reboot is necessary. You may imagine, that people work with Linux and sometimes lots of apps, files are opened. Doing reboot after every small update is not appropriate and makes Linux even worse than MS Windows, that requires reboot after software update, upgrade. In Linux most cases we do not need reboot. Quite often just rerunning plasmashell would help. Certainly I need save work beforehand, if it will close any app, which I don't know. Even closing apps and reopening them after rerunning plasmashell would work much faster, than rebooting all the time. You may imagine, that people use also filesystem encryption and perhaps some integration between PAM and KWallet, at least I do. So rebooting and re-entering encryption, PAM passwords takes much longer than just saving work and closing apps, rerunning plasmashell and reopening apps. E.g. ProtonMail Bridge is quite reluctant and requires separate approach (pass CLI app for GPG-key) and does not work via KWallet. So I need re-enter all these credentials, when rebooting or even relogin. Again - saving work, rerunning plasmashell or GUI effects (kwin_x11) is very often much faster than rebooting. Quite often I don't even need to close all apps but some of them. I try to watch, what apps will be updated and will save work, close only these. Besides, I never ignore the message, that says me to do reboot or relogin or whatever else is needed to do. I can confirm, that no message did not appear at the time I made current report and that was main reason for my reporting. As mentioned, rerunning plasmashell solved issue and no reboot was necessary. To be honest, Linux is not Windows, that we need to reboot all the time. If you just ignore my report and do not announce reboot, even if it is necessary, then you are making KDE usage experience worse. People might even start thinking over Linux in general not good. If the announcement appears on CLI among other output, that quickly flows away, then it is not a proper way to communicate as it is very hard to notice among other text output at CLI the message, that I need to reboot. As I use EndeavourOS, which updates quite often software, I do also quite often reboots. New kernel, init, other system components diligently tell me to do reboot and I never ignore it. Usually I check the list of packages, that will be updated and usually when I see kernel, init, etc system components in that updates list; I already start closing all apps, virtual machines, etc and saving work if needed to prepare for reboot. If I notice e.g. Electron framework will be updated - I close all apps I know, are using that framework. Then I don't need to close all apps and reboot. Just reopening updated apps would be enough EndeavourOS announces via eos-update-notifier app the GUI pop-up about the need of reboot and it is very well visible. I've used libnotify my own to announce critical messages for users. I've used update scripts via CRON and used such messaging. There are many ways to show such pop-up messages, that is well seen on screen. -- You are receiving this mail because: You are watching all bug changes.
