Sven Neumann [EMAIL PROTECTED] wrote:
Hi,
On Mon, 2007-07-16 at 19:20 +0200, Olivier Lecarme wrote:
I'm probably stupid, but I did not find anything related to the graphics
card driver in the gimprc man page. Except maybe putting off the option
show-brush-outline?
Quoting from the manual page:
(xor-color (color-rgb 0.501961 1.00 0.501961))
Sets the color that is used for XOR drawing. This setting only
exists as a workaround for buggy display drivers. If lines on
the canvas are not correctly undrawn, try to set this to white.
The color is specified in the form (color-rgb red green blue)
with channel values as floats in the range of 0.0 to 1.0.
I did it (setting color-rgb to 1.0 1.0 1.0). Unfortunately, the only
result is that the brush outline is now white, and still persistent.
Thus my current solution is to have the Option AccelMethod EXA in my
xorg.conf file, and not use the Wacom mouse as a painting tool. This
does not prevent me to use Gimp 2.3, fortunately.
--
Olivier Lecarme
___
Gimp-user mailing list
Gimp-user@lists.XCF.Berkeley.EDU
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-user

Hi,
On Sat, 2007-07-14 at 23:15 +0930, David Gowers wrote:
The drawing color changed (and I think the way GDK implements the
draw, which matters because GIMP increased the version of GTK they
require (GTK includes GDK)) between 2.2 and 2.3
Yes, the color changed. No, there was no relevant change in GDK and you
can easily verify that by running 2.2 and 2.3 against the same version
of GTK+.
Have a look at gimprc manual page. It explains how to work around the
bug in the graphics card driver.
Sven
___
Gimp-user mailing list
Gimp-user@lists.XCF.Berkeley.EDU
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-user

Sven Neumann [EMAIL PROTECTED] wrote:
Hi,
On Sat, 2007-07-14 at 23:15 +0930, David Gowers wrote:
The drawing color changed (and I think the way GDK implements the
draw, which matters because GIMP increased the version of GTK they
require (GTK includes GDK)) between 2.2 and 2.3
Yes, the color changed. No, there was no relevant change in GDK and you
can easily verify that by running 2.2 and 2.3 against the same version
of GTK+.
Have a look at gimprc manual page. It explains how to work around the
bug in the graphics card driver.
I'm probably stupid, but I did not find anything related to the graphics
card driver in the gimprc man page. Except maybe putting off the option
show-brush-outline?
By the way, Michel Daenzer from the xorg-driver-ati list suggested me to
try the driver from the experimental Debian depot (with no result), and
to put the Option AccelMethod EXA in my xorg.conf file. The second
suggestion suppresses the xor error problem, but the Wacom tablet mouse
no longer traces at all, at least visibly: nothing appears in the
window, but Gimp considers it to be modified. The PS/2 mouse still works
normally, as well as the Wacom stylus and eraser.
Does this strange behavior suggests you something?
--
Olivier Lecarme
___
Gimp-user mailing list
Gimp-user@lists.XCF.Berkeley.EDU
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-user

David Gowers [EMAIL PROTECTED] wrote:
On 7/14/07, Olivier Lecarme [EMAIL PROTECTED] wrote:
I installed version 2.3.18 on two similar computers: Debian Sid and
kernel 2.6.21. The problem occurs only on one of the computers, not the
other. It does not occur at all with version 2.2.
With all the tracing tools that use a brush (pencil, brush, eraser,
dodge and burn, etc.) but only with them, as soon as the pointer is in
the image window, there appears a series of images of the current brush,
light green. They don't modify the image itself, as simply redrawing it
makes the images to disappear.
An example can be seen on http://pierredelune.i3s.unice.fr/bizarre.png
Since this problem makes Gimp 2.3 pretty unusable for me, I would very
much like to find a solution. What other information would be useful?
I don't know. But this is a bug in your X server; it does not handle
XOR drawing correctly. You may be able to configure X to work around
the bug. You should probably ask this question on the appropriate list
for XFree86 or X.org, whichever you are using, and provide the
contents of the Device section for your video card (found in
/etc/X11/XF86Config-4 or /etc/X11/Xorg.conf depending on whether you
use XF86 or Xorg)
Maybe a bug in the X server, but then, why does it occur only in Gimp
version 2.3, not 2.2, and in no other graphic tool ? Moreover, I have
the same version of Xorg on both computers, and the problem occurs on
only one. Still moreover, is not XOR drawing used for moving the pointer
image anywhere on the screen?
Thus I'm asking what could be specific to Gimp 2.3.
--
Olivier Lecarme
___
Gimp-user mailing list
Gimp-user@lists.XCF.Berkeley.EDU
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-user

David Gowers [EMAIL PROTECTED] wrote:
On 7/14/07, Olivier Lecarme [EMAIL PROTECTED] wrote:
David Gowers [EMAIL PROTECTED] wrote:
I don't know. But this is a bug in your X server; it does not handle
XOR drawing correctly. You may be able to configure X to work around
the bug. You should probably ask this question on the appropriate list
for XFree86 or X.org, whichever you are using, and provide the
contents of the Device section for your video card (found in
/etc/X11/XF86Config-4 or /etc/X11/Xorg.conf depending on whether you
use XF86 or Xorg)
Maybe a bug in the X server, but then, why does it occur only in Gimp
version 2.3, not 2.2, and in no other graphic tool ? Moreover, I have
The drawing color changed (and I think the way GDK implements the
draw, which matters because GIMP increased the version of GTK they
require (GTK includes GDK)) between 2.2 and 2.3
the same version of Xorg on both computers, and the problem occurs on
only one.
The version of Xorg is irrelevant -- that comparison only makes sense
if you have the same *video card* in both systems. This bug has been
reported several times, and it's directly related to X's driver for
your video card.
OK. The video cards are different:
- on the computer where it works correctly: ATI Technologies Inc RV 370
5B60 [Radeon X300 (PCIE)]
- on the computer where it fails: ATI Technologies Inc Radeon RV100 QY
[Radeon 7000/VE]
But the X driver is the same in both cases, i.e. ati. Should I try the
proprietary fglrx driver?
Anyway, thanks a lot for answering me questions not really relevant to
this list!
--
Olivier Lecarme
___
Gimp-user mailing list
Gimp-user@lists.XCF.Berkeley.EDU
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-user

On 7/15/07, Olivier Lecarme [EMAIL PROTECTED] wrote:
David Gowers [EMAIL PROTECTED] wrote:
The version of Xorg is irrelevant -- that comparison only makes sense
if you have the same *video card* in both systems. This bug has been
reported several times, and it's directly related to X's driver for
your video card.
OK. The video cards are different:
- on the computer where it works correctly: ATI Technologies Inc RV 370
5B60 [Radeon X300 (PCIE)]
I'll add that here, I have an 'ATI Technologies Inc RV280 [Radeon 9200 PRO]'
running under the normal X.org ATI driver (X.org version 7.0.0) with
no XOR problems.
- on the computer where it fails: ATI Technologies Inc Radeon RV100 QY
[Radeon 7000/VE]
But the X driver is the same in both cases, i.e. ati. Should I try the
proprietary fglrx driver?
Yes, that would probably be wise.
Anyway, thanks a lot for answering me questions not really relevant to
this list!
No problem.
___
Gimp-user mailing list
Gimp-user@lists.XCF.Berkeley.EDU
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-user