Gimp does more disk work than most apps, in order to handle editting very large images. It maintains a cache of blocks, usualy in the user's homedir, so NFS issues are a likely target. strace is often your friend for this sort of thing.
Ross -- Ross Reedstrom On Fri, Feb 21, 2014 at 12:12:23PM +0100, Petter Reinholdtsen wrote: > [Nigel Barker] > > Does anyone have a good suggestion? > > I would suggest running 'strace -p <pidofgimp>' to see what gimp is > doing when gimp is slow to save, and 'tcptrace' to see if there is > something network wise going on. No experience in what the problem > could be. Perhaps it is NFS locking related? > > -- > Happy hacking > Petter Reinholdtsen > > > -- > To UNSUBSCRIBE, email to [email protected] > with a subject of "unsubscribe". Trouble? Contact [email protected] > Archive: http://lists.debian.org/[email protected] > > -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/[email protected]
