On Thu, 2011-07-21 at 11:17 +0100, John Pilkington wrote: > On 21/07/11 09:21, Roderick Johnstone wrote: > > On 21/07/11 03:38, 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? > >> It was suggested that a bug should be raised for it. > >> > > > > This doesn't seem to be a problem for us on F14 usually, although things > > did go a bit odd after the kde 4.5.x to 4.6 update until we logged out > > and in again. > > > > Roderick > > A post on Fedora-users (poc, 28/06/11 17:22) drew my attention to > needs-restarting, which is part of the yum-utils package. > > [John@localhost ~]$ needs-restarting --help > Usage: > needs-restarting: Report a list of process ids of programs that > started running before they or some component they use were updated. > > Options: > -h, --help show this help message and exit > -u, --useronly show processes for my userid only > [John@localhost ~]$ > > Null output suggests that all should be ok. > > I haven't used this because I thought it might be yum-specific, and I > normally use smart, but this --help info makes it look depsolver agnostic. It has nothing to do with yum, or indeed with depsolvers of any sort. It just looks at the actual running binary and checks the file(s) it came from. Which is pretty cool IMHO. The code is a page or two of Python and is very educational to read. poc _______________________________________________ kde mailing list kde@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/kde New to KDE4? - get help from http://userbase.kde.org
