On Fri, 21 Apr 2006, Christopher Martin wrote:
Could you run 'top' from konsole, to verify that it is gwenview that is eating the CPU when it tries to view the next image, and not some other process? The fam daemon has caused problems with KDE apps in the past, for instance, though that's just a wild guess.
I already did that. I'm not running famd (nor GNOME or KDE). My pictures are quite large, averaging about 1Mb.
Also, I don't think I was quite clear: the CPU usage occurs *after* it has displayed the next picture. The picture itself displays reasonably quickly.
-- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
