Summary: | [RV770] Permanently unrendered regions after loading/dismissing context menus | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Product: | xorg | Reporter: | Bryce Harrington <bryce> | ||||||||
Component: | Server/General | Assignee: | Xorg Project Team <xorg-team> | ||||||||
Status: | RESOLVED FIXED | QA Contact: | Xorg Project Team <xorg-team> | ||||||||
Severity: | major | ||||||||||
Priority: | medium | ||||||||||
Version: | 7.6 (2010.12) | ||||||||||
Hardware: | x86 (IA32) | ||||||||||
OS: | Linux (All) | ||||||||||
Whiteboard: | |||||||||||
i915 platform: | i915 features: | ||||||||||
Attachments: |
|
Description
Bryce Harrington
2011-04-29 17:25:43 UTC
Created attachment 46176 [details]
Screenshot showing 3 different unrendering regions
Created attachment 46177 [details]
dmesg
Created attachment 46178 [details]
Xorg.0.log
I've been having the same problem for a while on my ThinkPad T60p (FireGL V5250; RV530). I've been able to get rid of the garbage by setting a window as Always On Top and dragging it over the misrendered area. Usually, it happens in the top few lines of the Plasma panel (KDE 4.6.2), in which case it shows lines from the desktop wallpaper. I'll take a screenshot the next time it happens. In my case, setting a window to always on top seems to not make a difference - the unrendered regions remain unrendered (and the window just displays underneath. Only context menus and the mouse cursor draw over the top of the unrendered regions, and (usually) don't make the regions go away. Logging out and back in is sufficient for eliminating the unrendered regions; in fact they disappear as soon as the logout sequence begins (before many of the windows have actually closed). (Makes me wonder if it could be something bugged in metacity?) Sounds like bug 22566. At any rate though, this can't really be a driver bug, as the driver isn't actively involved in window management. Resolved in ubuntu. Metacity bug, like Michael suggested. |
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.