Closed
Bug 1216664
Opened 9 years ago
Closed 8 years ago
Pretty awesome glitches related to xrender on Linux
Categories
(Core :: Graphics, defect)
Core
Graphics
Tracking
()
RESOLVED
FIXED
People
(Reporter: nical, Assigned: nical)
References
Details
(Whiteboard: gfx-noted)
Attachments
(3 files)
I had this once on my new computer. it has a nvidia quadro gpu (GM107GL [Quadro K620] (rev a2)) with nouveau driver. I just set the computer up today and had this glitch only once, so I don't know if it's anything we can do at the gecko level. Looking at the glitches and how they span across layers I assume this is happening between xrender and the driver. Scrolling all the way down and back up cleared the artifacts.
Assignee | ||
Updated•9 years ago
|
Whiteboard: gfx-noted
Assignee | ||
Comment 1•9 years ago
|
||
Assignee | ||
Comment 2•9 years ago
|
||
This one's interesting because the screenshot does not show exactly what I was seeing on the screen: although most of the screen looked like this attachment, I could see parts of my text editor in the bottom right which doesn't appear here.
Assignee | ||
Comment 3•9 years ago
|
||
I am now using the proprietary nvidia drivers and the problem still occurs, so it's not specific to nouveau. The problem disappears when using cairo's image backend rather than xrender.
See Also: → 1225044
Summary: Pretty awesome glitches (could be related to nvidia nouveau drivers) on Linux → Pretty awesome glitches related to xrender on Linux
Assignee | ||
Comment 4•8 years ago
|
||
(In reply to Nicolas Silva [:nical] from comment #3) > I am now using the proprietary nvidia drivers and the problem still occurs, > so it's not specific to nouveau. The problem disappears when using cairo's > image backend rather than xrender. I was actually still on nouveau (I think). Anyway, xrender for painting is disabled since bug 1180942 landed which fixed this in the process.
Assignee: nobody → nical.bugzilla
Status: NEW → RESOLVED
Closed: 8 years ago
Depends on: 1180942
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•