Bug 9877 - XOR function apparently not working correctly.
Summary: XOR function apparently not working correctly.
Status: RESOLVED WONTFIX
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/Radeon (show other bugs)
Version: 7.2 (2007.02)
Hardware: x86 (IA32) Linux (All)
: high normal
Assignee: xf86-video-ati maintainers
QA Contact: Xorg Project Team
URL: https://bugs.launchpad.net/xserver-xo...
Whiteboard:
Keywords:
: 12853 (view as bug list)
Depends on:
Blocks:
 
Reported: 2007-02-04 14:28 UTC by Christopher Sawtell
Modified: 2010-03-26 19:00 UTC (History)
2 users (show)

See Also:
i915 platform:
i915 features:


Attachments
Eric's xorg.conf (4.31 KB, application/octet-stream)
2007-10-25 13:21 UTC, Eric Seppanen
no flags Details
Eric's Xorg.0.log (215.89 KB, patch)
2007-10-25 13:21 UTC, Eric Seppanen
no flags Details | Splinter Review
screenshot of problem (325.74 KB, image/png)
2007-10-25 13:22 UTC, Eric Seppanen
no flags Details

Description Christopher Sawtell 2007-02-04 14:28:21 UTC
Moving cursor in GIMP leaves trail. See:-
http://shell.clug.net.nz:8080/~chris/gimpSnapshot.png
Comment 1 Michel Dänzer 2007-02-05 01:37:54 UTC
Please attach (as opposed to paste) the full xorg.conf and Xorg.0.log files.
Comment 2 Daniel Stone 2007-02-27 01:36:10 UTC
Sorry about the phenomenal bug spam, guys.  Adding xorg-team@ to the QA contact so bugs don't get lost in future.
Comment 3 Eric Seppanen 2007-10-25 13:15:58 UTC
This problem exists in the code released with Ubuntu 7.10.

I have seen scattered reports of this all around the net.  It seems that recent versions of Gimp use new XOR code that reveal a problem with the driver for ATI Radeon VE/7000 RV100 cards.

Please see https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/156556

I will attach screenshot, conf, and logs.
Comment 4 Eric Seppanen 2007-10-25 13:21:06 UTC
Created attachment 12197 [details]
Eric's xorg.conf
Comment 5 Eric Seppanen 2007-10-25 13:21:28 UTC
Created attachment 12198 [details] [review]
Eric's Xorg.0.log
Comment 6 Eric Seppanen 2007-10-25 13:22:22 UTC
Created attachment 12199 [details]
screenshot of problem
Comment 7 Alex Deucher 2007-10-25 13:51:44 UTC
*** Bug 12853 has been marked as a duplicate of this bug. ***
Comment 8 Rolf Leggewie 2008-06-16 10:02:53 UTC
I confirm the existence of this problem.
Comment 9 Christopher Sawtell 2008-06-16 13:35:09 UTC
As of GNU Image Manipulation Program version 2.4.5 using:-

X.Org X Server 1.4.0.90
Release Date: 5 September 2007
X Protocol Version 11, Revision 0
Build Operating System: Linux Ubuntu
(xorg-server 2:1.4.1~git20080131-1ubuntu9.2)
Current Operating System: Linux imogen 2.6.24-18-generic #1 SMP Wed May 28 20:27:26 UTC 2008 i686
Build Date: 13 June 2008  01:08:21AM


That's Kubuntu Hardy Heron fully updated as of 2008-06-17 this bug appears to have been fixed.
Comment 10 Rolf Leggewie 2008-06-16 15:45:00 UTC
well, I just confirmed three hours ago that this problem still exists in my equally up-to-date ubuntu hardy install (which probably prompted you to look back here).  I assume, you just masked the problem by one of the various workarounds.

Reopening.
Comment 11 Alex Deucher 2008-06-16 16:11:45 UTC
(In reply to comment #10)
> well, I just confirmed three hours ago that this problem still exists in my
> equally up-to-date ubuntu hardy install (which probably prompted you to look
> back here).  I assume, you just masked the problem by one of the various
> workarounds.

What exactly is the problem here?  Is it a particular tool in GIMP, or just GIMP in general?  Also can you attach your xorg log and config? Do any of the following options help?

Option "RenderAccel" "FALSE"
Option "AccelMethod" "EXA"
Option "AccelMethod" "XAA"
Comment 12 James Cloos 2008-06-16 17:13:32 UTC
The various linked bug reports strongly suggest it only occurs when
using XAA.
Comment 13 Paulo César Pereira de Andrade 2008-06-16 18:09:27 UTC
  I think it may be related to composite.

  Try adding

Section "Extensions"
    Options "Composite" "disable"
EndSection

to xorg.conf

But the problem seems to be related to some ati cards.
Comment 14 Rolf Leggewie 2008-06-16 23:27:22 UTC
https://bugs.launchpad.net/xserver-xorg-driver-ati/+bug/156556 should have all the necessary information.  Yes, it seems to be an ATI problem.  There are various workarounds.  Decreasing importance.
Comment 15 Alex Deucher 2008-12-02 23:47:23 UTC
is this still an issue with a more recent driver/xserver version?
Comment 16 Rolf Leggewie 2008-12-03 00:12:12 UTC
I am still on hardy, but comment 18 from https://bugs.launchpad.net/xserver-xorg-driver-ati/+bug/156556 confirms this to be still present in Intrepid.  xserver-xorg seems to be at version 1:7.4~5ubuntu3 in Intrepid.
Comment 17 Corbin Simpson 2010-03-26 19:00:19 UTC
Closing as WONTFIX; XAA is too far gone these days. If EXA does not work, file a new bug or attach yourself to an existing bug matching your issues.

For this particular bug, I'd say that re-opening is fine if it still happens with EXA.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.