Bug 5108 - screen artifacts with icons on desktop and in toolbars
Summary: screen artifacts with icons on desktop and in toolbars
Status: RESOLVED DUPLICATE of bug 3944
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/Vesa (show other bugs)
Version: 6.99.99.902 (7.0 RC2)
Hardware: x86 (IA32) Linux (All)
: high normal
Assignee: Xorg Project Team
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 1690
  Show dependency treegraph
 
Reported: 2005-11-21 01:23 UTC by Willem Riede
Modified: 2005-11-29 20:56 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
Screenshot demonstrating problem (126.03 KB, image/png)
2005-11-21 01:24 UTC, Willem Riede
no flags Details
configuration file used (2.81 KB, text/plain)
2005-11-21 01:25 UTC, Willem Riede
no flags Details
xorg startup log (65.45 KB, text/plain)
2005-11-21 01:25 UTC, Willem Riede
no flags Details
Another screenshot (ppc) (40.80 KB, image/png)
2005-11-28 08:16 UTC, Frank Arnold
no flags Details

Description Willem Riede 2005-11-21 01:23:27 UTC
On my opteron with ATI Radeon X300SE icons are displayed incorrectly placed
initially and differently on mouse-over. While this graphics card was not
recognized by name at the time, this worked fine before the upgrade to modular X
from Fedora fc5-devel.

See attached screenshot, xorg.conf and Xorg log.
Comment 1 Willem Riede 2005-11-21 01:24:44 UTC
Created attachment 3851 [details]
Screenshot demonstrating problem
Comment 2 Willem Riede 2005-11-21 01:25:21 UTC
Created attachment 3852 [details]
configuration file used
Comment 3 Willem Riede 2005-11-21 01:25:59 UTC
Created attachment 3853 [details]
xorg startup log
Comment 4 Michel Dänzer 2005-11-21 19:44:16 UTC
You're using the vesa driver, not radeon. Does this also happen with the radeon
driver?
Comment 5 Willem Riede 2005-11-22 10:50:47 UTC
The radeon driver does not exhibit this problem.

[non-related observation: the radeon driver tries very hard to do drmOpen - each
of card0 to 254 is tried twice, card0 even more often, then the driver says
drmOpen failed followed by DRIScreenInit failed - is that a bug or due to a
limitation of my graphics card?]
Comment 6 Michel Dänzer 2005-11-22 19:31:13 UTC
(In reply to comment #5)
> The radeon driver does not exhibit this problem.

Good, but then why did you set the component field back to the wrong driver?

> [non-related observation: the radeon driver tries very hard to do drmOpen - each
> of card0 to 254 is tried twice, card0 even more often, then the driver says
> drmOpen failed 

This is all done by drmOpen and not driver specific.

> followed by DRIScreenInit failed - is that a bug or due to a limitation of my
> graphics card?]

Most likely a configuration issue.
Comment 7 Frank Arnold 2005-11-28 08:16:13 UTC
Created attachment 3922 [details]
Another screenshot (ppc)

I am seeing a similar problem on my Powerbook (Radeon Mobility 9700). I'm using
the radeon driver, so I doubt it's a driver issue.

There are some differences (see attached screenshot):
1. The displacement is upwards instead of right (perhaps because it is PPC)
2. Panels are working nicely. Both, vertical and horizontal types.
3. No color variations.

X itself seems to work as expected. I have no problems with windows and their
contents, graphical boot or anything else. If the Nautilus desktop is disabled,
the background looks fine too and shows no remaining patterns while moving
windows. Command to do this:
gconftool-2 --type bool --set /apps/nautilus/preferences/show_desktop false

I think we have at least a starting point to track this down. Nautilus worked
fine with X11R6 and seems to use GDK to draw it's desktop. I haven't looked
further because I have not much insight.

Just for completeness: System is up to date Fedora Rawhide with Nautilus 2.12.1
and GTK2 2.8.7.

Mike:
Please tell me if I should file a bug against Nautilus or GTK in Redhat BTS.
Comment 8 Sadda Teh 2005-11-28 13:40:09 UTC
Same problem with the vesa driver on a Dell Inspiron 8000 laptop (latest BIOS)
with ATI Mobility M4 running latest Fedora rawhide. Though the ati driver works
(though r128 driver fails to load if I specify "r128" as the driver in
xorg.conf). The vesa driver worked fine before Fedora upgraded to modular X.
Comment 9 Michel Dänzer 2005-11-28 20:09:30 UTC
Comment #8 seems to confirm that this is a vesa driver specific bug. Comment #7
looks like a duplicate of bug 4456.
Comment 10 Frank Arnold 2005-11-30 05:20:06 UTC
Yes, comment #7 is definitly bug 4456. Thanks for pushing into the right
direction and sorry for the noise.
Comment 11 Søren Sandmann Pedersen 2005-11-30 05:34:49 UTC
This is pretty likely to be a duplicate of 3944
Comment 12 Søren Sandmann Pedersen 2005-11-30 05:35:07 UTC
This is pretty likely to be a duplicate of bugs 3944
Comment 13 Adam Jackson 2005-11-30 15:56:51 UTC
agreed

*** This bug has been marked as a duplicate of 3944 ***


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.