Bugzilla – Bug 168849
Some mouse cursors in Gimp leave trails over the window
Last modified: 2006-06-27 14:43:26 UTC
It seems that the screen is updated incorrectly in Gimp with some types of tool cursors (e.g. pencil, paintbrush). These cursors leave some kind of trails over both the canvas and the unused area of the image window. The trails are only temporary, they disappear after the window is redrawn (e.g. by moving another window over it), and the edited image is not affected. Please see the attached screenshot.
Created attachment 79721 [details] Traces over the window left by the pencil tool pointer.
Could you attach hwinfo output and your xorg.conf file? All I can imagine here is some sort of X problem.
Created attachment 81179 [details] Output of 'hwinfo --gfxcard'
Created attachment 81180 [details] The xorg.conf file.
Here they come :-) But as this seems to happen only in Gimp, and just with some types of cursors, I am not sure if the X is guilty. Looks rather like a GTK bug to me...
When you say with certain cursors, do you mean with certain cursor themes, or with particular cursors of the app as you mention above. What other cursors have the problem in gimp? Are you running under kde? Perhaps the gtk-qt-engine is causing an issue.
No, not cursor themes. I wanted to say that some Gimp tool cursors do it (like pencil, spray or paintbrush) while others do not (selector, magnifying glass). I think the problem only occurs with those types of tools which show a wireframe sample of the shape that would be drawn. I was running Gnome when the problem appeared.
Hmm, I'm still unable to make this happen, but I don't have an nvidia machine to test on. X team, any ideas?
I will re-test this with the RC2 soon, maybe it is related to some already fixed bug.
Jiri?
Sorry, I forgot... :-) I have reproduced this on the same machine with SL10.2 Alpha1. I don't have a SLES where I could test it right now, but it is the same code base.
Now I have reproduced it on SLES10 RC 2.5 x86_64 as well.
Hm, *could* be a duplicate of bug #157581. You could help us by checking whether installing the proprietary drivers from nvidia help.
Yes, the problem disappears when the proprietary drivers are employed.
*** This bug has been marked as a duplicate of 157581 ***