Created attachment 624822 [details] screenshot with severe glyph corruption Description of problem: ThinkPad T410 with Intel IronLake graphics Using the Switch User function in Gnome, causes Glyph corruption. Version-Release number of selected component (if applicable): xorg-x11-drv-intel-2.20.8-1.fc17.x86_64 kernel-3.5.6-1.fc17.x86_64 How reproducible: The corruption may not be instantly noticeable, it may take a switch or two to occur. Also, it does not seem to effect the Gnome Shell itself, but it does effect Firefox and terminal windows. Steps to Reproduce: 1. Login to Gnome Shell 2. Switch User 3. launch firefox and browse a bit 4. Logout 5. switch back to the first user Actual results: Glyph corruption. Severity of the corruption depends, sometimes it is minimal, other times it can be quite severe. Expected results: No glyph corruption Additional info: This corruption was introduced with an update along the way, as I did not experience it on F17 without updates. There are no errors in the kernel or xorg log files
Description: Same kind of problem here, corrupted glyphs (or disappearing glyphs) with Firefox and Terminal, but also gedit. Problem appears progressively, but faster when locking screen or suspending a lot. Version-Release number of selected component (if applicable): xorg-x11-drv-intel / x86_64 / 2.20.8 / 1.fc17 kernel / x86_64 / 3.6.3 / 1.fc17 Hardware: Integrated Intel GMA X4500 GPU Additional info: I think also that I was not experiencing this glyph corruption a few updates away. But a few updates away, I was dealing with another bug in xorg-x11-drv-intel, "Bug 845803 - wrong monitor resolution on wake from suspend with kernel 3.5.0-2.fc17.x86_64" <https://bugzilla.redhat.com/show_bug.cgi?id=845803>.
Nomore problems at this time... Version-Release number of selected component (if applicable): xorg-x11-drv-intel / x86_64 / 2.20.10 / 2.fc17 kernel / x86_64 / 3.6.6 / 1.fc17 I do not know if it's linked, but I get blank text with Firefox inside the URL dropdown of the navigation toolbar, from session start.
With recent updates the problem no longer occurs, as such closing this bug report.