I'm using elementary OS, an Ubuntu derivate, on a IBM Thinkpad T40 with a ATI RV200/Mobility Radeon 7500 and a variety of graphical glitches occur during regular usage. I've reported the issues to the distribution team but they think it's a driver issue. I've made a short video showing the glitches and extracted some screenshots. In the video you can see that the dock is invisible at first and that the menus at the top of the screen don't open. At about 1:50 I restart the window manager via ssh which then shows the dock and the menus at the top. Then I launch several applications to demonstrate the graphical glitches. Demonstration: http://www.youtube.com/watch?v=zmmDJglt2V4 Xorg.0.log: http://git.io/FB8xCQ dmesg.log: http://git.io/UsMneg dpkg.log: http://git.io/V9bOpA glxinfo.log: http://git.io/Uk9H0A hardinfo.log: http://git.io/hgwulw lightdm.log: http://git.io/134lLg lshw.log: http://git.io/X1bCmA ps.log: http://git.io/m6DNAg x-0.log: http://git.io/1ynXfg xsession-errors.log: http://git.io/JYnivQ Screenshots: https://launchpadlibrarian.net/145047160/dock-invisible.jpg https://launchpadlibrarian.net/145047167/dock-visible.jpg https://launchpadlibrarian.net/145047177/empathy.jpg https://launchpadlibrarian.net/145047189/geary.jpg https://launchpadlibrarian.net/145047198/shotwell.jpg https://launchpadlibrarian.net/145047204/shutdown-dialog.jpg Original bug report on the distribution bug tracker: https://bugs.launchpad.net/elementaryos/+bug/1201630
This is probably a duplicate of bug 51658.
I installed all 9.2.0~git20130729+9.2.9b8ad643-0ubuntu0sarvatt~precise updates via https://launchpad.net/~xorg-edgers but sadly nothing changed. Any further ideas?
As mentioned in bug 51658, r1xx/r2xx hardware supports texture formats that cannot be rendered to: "> r200 essential patches (1st 3 patches) for gnome shell: > "Essential patch to disable texture formats that are reported unrenderable > elsewhere in driver." I'm not really happy with that. I guess the problem is if we try to attach a texture to a fbo it is too late to notice we cannot render to that format. But this sort of sucks for ordinary textures. Ideally we'd probably be able to really determine our format only at the first upload of data to the texture (which presumably won't happen) so we could change it if we attach it to a fbo. Though if there is indeed already data uploaded we're screwed." You could try applying attachment 63711 [details] [review].
FWIW maybe that patch really is a good idea. I don't really look at r200 much these days, and since it doesn't really seem possible to change the format later so we can render to it if necessary sacrificing texture upload speed might be well worth the tradeoff of avoiding troubles with fbos.
Nice! Would this patch also be meaningful for a R100? I'm not firm in this topic, but to my understanding a RV200 is (confusingly) part of the R100 family.
The patch touched code that is shared by both r100 and r200 so it's relevant to and applies to both.
In regards to this bug does the patch fix the issue you are seeing?
Great, then I'll give it a try and report the result.
(In reply to comment #6) > The patch touched code that is shared by both r100 and r200 so it's relevant > to and applies to both. Actually it shouldn't do anything on r100, since it always should have used the same format there anyway. So this bug seems to be something else entirely unfortunately.
Oh bummer, any other ideas?
Okay, I played a little around with window managers. Mutter also has graphical glitches (a little different ones though), Compiz doesn't work at all, Xfce and Fluxbox work and If I replace elementary's window manager gala with xfwm4 then as far as I can see the severe glitches disappear with only minor glitches remaining.
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/mesa/mesa/issues/286.
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.