| Summary: | screen artifacts with icons on desktop and in toolbars | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | xorg | Reporter: | Willem Riede <wriede> | ||||||||||
| Component: | Driver/Vesa | Assignee: | Xorg Project Team <xorg-team> | ||||||||||
| Status: | RESOLVED DUPLICATE | QA Contact: | |||||||||||
| Severity: | normal | ||||||||||||
| Priority: | high | CC: | mharris | ||||||||||
| Version: | 6.99.99.902 (7.0 RC2) | ||||||||||||
| Hardware: | x86 (IA32) | ||||||||||||
| OS: | Linux (All) | ||||||||||||
| Whiteboard: | |||||||||||||
| i915 platform: | i915 features: | ||||||||||||
| Bug Depends on: | |||||||||||||
| Bug Blocks: | 1690 | ||||||||||||
| Attachments: |
|
||||||||||||
|
Description
Willem Riede
2005-11-21 01:23:27 UTC
Created attachment 3851 [details]
Screenshot demonstrating problem
Created attachment 3852 [details]
configuration file used
Created attachment 3853 [details]
xorg startup log
You're using the vesa driver, not radeon. Does this also happen with the radeon driver? 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?] (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. 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.
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 #8 seems to confirm that this is a vesa driver specific bug. Comment #7 looks like a duplicate of bug 4456. Yes, comment #7 is definitly bug 4456. Thanks for pushing into the right direction and sorry for the noise. This is pretty likely to be a duplicate of 3944 This is pretty likely to be a duplicate of bugs 3944 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.