Gimp lags and misses some strokes especially when drawing fast
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gimp (Ubuntu) |
Fix Released
|
Medium
|
Ubuntu Desktop Bugs |
Bug Description
When drawing in the Gimp, the cursor often lags behind, and some strokes are sometimes missing completely. This gets worse as one draws faster, up till almost unusable if trying to draw "normally".
Trying applications like Inkscape, everything is registered perfectly, no matter how fast I make lines and calligraphy.
I'm using a Wacom board, and this is not on a slow or even slowish computer, it's on a 2.4MHz with large memory, quite recent Nvidia card and accelerated drivers. No other graphics applications, including stuff like Unreal Tournament has any trouble, so I don't think that's it, and the tablet works fine in other gfx apps.
I'm not using unreasonable image sizes either, this happens and behaves mostly the same on a 72dpi 1024x768 image just as well as a 300dpi A3.
Not actually being an artist myself, but I work with a lot of them, and honestly, I can't show Gimp to any of them in this state. I don't know if this is a general Gimp issue or if it's only in Ubuntu, or even just in Dapper, since I don't have other distros to compare with. Any clues to investigate and fix, and opinions from others would be welcome.
Found another one with the same problem: http:// ubuntuforums. org/showthread. php?t=142832& highlight= gimp+lag
That description is probably better, too:
"have my Wacom Graphire 4 tablet working on Linux (Ubuntu 6.04,
kernel 2.6.15, built-in tablet drivers) and get bad pressure sensivity
and line quality in The GIMP 2.2.10, but at least it's working.
However, when using any of the paint/ink tools, although producing a
decent stroke, it fails to keep up. The stroke does not lag as if on a
slow system, but if I end a stroke and quicky make another stroke, the
second stroke does not appear.
I notice that the CPU goes up to 100% whenever I paint with the
paint/ink tool, and there's a slight cursor-lag at the end of each
stroke, which I guess is why the system is not catching the next one.
I'm sure this is not due to GIMP's inefficiency, as it works fine on
my friend's much slower computer."