On Thu, 2011-07-21 at 09:29 -0400, Felix Miata wrote: > On 2011/07/21 15:16 (GMT+0800) Ed Greshko composed: > > > Jim Dean wrote: > > >> A recent discussion on Fedora forums raised the need to logout and back > >> after a KDE version update. I've noticed that the system becomes > >> unstable, last time I got a plasma crash, and others reported similar things. Is this > >> common or just a few people? > > > FWIW, I have not seen this problem. Last update, I waited 2 days before a logout/login. > > I find it difficult for anyone to expect updates to complex interdependent > running binaries to continue to function correctly while and after updates to > them are applied. I always turn off automatic desktop updaters and update > notifiers, usually exit X before applying updates, and when not, restart > immediately after application completes, if not reboot the system. See the recent thread on "needs-updating" on the Users list. Updating the on-disc binary of a running process has no effect on said process, it simply creates a new file. New execs of the program will execute from that file rather than the old one, but the old one will persist until the last running instance of it dies. Of course problems can in theory arise if a set of interacting processes are partially updated, depending on exactly when each of them executes, but in practice I've rarely seen any problems with this (mainly I think because apps don't tend to change radically from one version to the next, especially in their external interfaces). The main reason for restarting a session is to get the new version of long-running components, which would include plasma and the like. poc _______________________________________________ kde mailing list kde@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/kde New to KDE4? - get help from http://userbase.kde.org
