Red Hat Bugzilla – Bug 200223
trident(4) XAA screen-to-screen copy is busted
Last modified: 2007-11-30 17:11:38 EST
Description of problem:
I'm experiencing problems with the the display such as:
- Scrolling up through documents in Firefox, list controls, OOo, etc. causes
the canvas area to become messed.
- Moving any windows in GNOME (Nautilus, terminal, firefox) causes the
the canvas are to become messed.
These problems can be fixed my minimising and restoring the window. (I assume
they're the same problem).
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Open home directory Nautilus window in GNOME.
2. Click on caption bar and move window.
1. Open a long page in Firefox.
2. Press End to got the bottom of the page.
3. Press Page Up.
Window canvas is filled with nonsense. In Nautilus it is filled blue with some
geometric lines. In Firefox parts of the page are displayed horizontally sliced
up and down the window.
Window contents is preserved or repainted normally.
I'm testing on a Toshiba Tecra M1 and the adaptor is reported as a
Trident CyberBlade XP4m32. It worked fine with FC5.
Please attach your X server log file and config file as individual uncompressed
file attachments. Also attach a screenshot showing the corruption if
possible. If you can't capture it with a screenshot, a digital picture would
be ok too if possible.
Also, please try disabling 2D acceleration with:
Does the problem go away with noaccel? Please also test the 'vesa' driver
to see if it happens there too. These tests will help narrow down where
the problem is for deeper investigation.
Thanks in advance.
"noaccel" fixes the problem.
I'm not sure how to test with the vesa driver. Changing xorg.conf to:
results in a blank screen when X starts and nothing else.
I'm attaching the requested information.
Created attachment 133099 [details]
Original xorg.conf (i.e. without noaccel)
Created attachment 133100 [details]
Xorg log (without noaccel specified)
Created attachment 133101 [details]
Screen capture of moved Nautilus window showing problem
Created attachment 133102 [details]
Screenshot of firefox showing problem
This is a shot of scrolling back (Page Up) up a web page from the end.
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=195387 is a similar
It could be 2 independent but similar driver-specific issues, or it could
point to a flaw in the X server's acceleration common code paths perhaps.
I don't think this is a dup of bug #193387. The trident driver grew XAA support
for XP4 and XP5 between 7.0 and now, so it's likely to just be that.
Reporter, does using Option "AccelMethod" "EXA" instead of Option "noaccel" also
fix the problem?
Yes, adding 'Option "AccelMethod" "EXA"' to the Device section also fixes the
I also have a Toshiba Tecra M1 with a Trident CyberBlade XP4m32 graphics card
and I found that although using 'Option "AccelMethod" "EXA" as the only option
in the Device Section fixes the corruption of the displayed images, watching OGG
videos no longer works when using Totem (only a blank window is shown).
Additionally, after using Totem, a green rectangle appears across the top of the
screen. I am running xorg-x11-drv-trident-1.2.1-3.fc6 and the final release of FC6.
Fedora Core 5 and Fedora Core 6 are, as we're sure you've noticed, no longer
test releases. We're cleaning up the bug database and making sure important bug
reports filed against these test releases don't get lost. It would be helpful if
you could test this issue with a released version of Fedora or with the latest
development / test release. Thanks for your help and for your patience.
[This is a bulk message for all open FC5/FC6 test release bugs. I'm adding
myself to the CC list for each bug, so I'll see any comments you make after this
and do my best to make sure every issue gets proper attention.]
Even after almost three months there has been no activity on these bugs, so we
consider them obsolete and they are being closed as INSUFFICIENT_DATA.
Please, if you are able to reproduce this bug on currently supported (FC6 and
F7) non-test distribution, or if there is any other reason why this bug should
be kept alive, please, reopen, change the product to something more recent and
add an additional information to the comment of such bug.
Thank you very much.