Created attachment 339691 [details] screenshot Lately, I am seeing glyphs turn to garbage on my screen. It seems affect individual glyphs, but it is progressive and gets worse over time. The attached screenshot shows many corrupted glyphs in firefox, and a few in xchat.
I see this a lot on an i830 (for the past two months or more); starts pretty soon after login. Killing the X server (ie, logout and log back in) brings glyphs back to normal for a few minutes before the corruption starts again. It usually gets worse doing a lot of stuff with gnome-terminal. It usually only affects one size of one font; ie 9pt will be corrupted, but the same font at 12pt will be fine (until it eventually gets corrupted too). Matthias, I assume you've got GMA4500 or something?
Created attachment 339699 [details] Xorg.0.log
Looks similar to https://bugzilla.redhat.com/show_bug.cgi?id=495323 . Are you guys running Compiz, or KDE with desktop effects, or anything at all 3D-accelerated, as described in that report? Thanks. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
Looks visually similar, indeed. However, the corruption has not reappeared on my machine so far, since reporting this bug.
Haven't seen this again, so I'll assume for now that whatever caused it has resolved itself.
I am seeing this all of a sudden today.
again, see my question in comment #3. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
No compiz, no 3D accelerated.
I see this very often, I just need to keep the pc (firefox?) running long enough
(In reply to comment #9) > I see this very often, I just need to keep the pc (firefox?) running long > enough It seems to me that it could somehow relate to upgrade of your computer (and something between different versions of driver/kernel in memory and on disk). I know it sucks, but reboot makes font nice again, right?
yes, rebooting makes the font nice again. Killing firefox and restarting it doesn't.
Is this not the same as Bug 495323?
*** This bug has been marked as a duplicate of bug 495323 ***