Bug 79858

Summary:	Artifacts/Glitches in Blender menu
Product:	Mesa	Reporter:	nucrap
Component:	Mesa core	Assignee:	mesa-dev
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	medium	CC:	nucrap, sa
Version:	unspecified
Hardware:	x86-64 (AMD64)
OS:	Linux (All)
Whiteboard:
i915 platform:		i915 features:
Attachments:	glitch in blender menu glitch in blender menu 2

Description nucrap 2014-06-09 23:42:45 UTC

Created attachment 100776 [details]
glitch in blender menu

Mostly when maximizing blender (you might need to try a few times) the menu at the top is full of artifacts and glitches.
It is independent of DE or any compositing effects because I tested this under compiz and openbox (without compiz) and it always occurs.

I have attached screenshots for better understanding.
I have tested it with both a HD4770 and a R7 260x graphics card (and I think it also happened on my laptop HD 5xxx).

My bugreport on the blender bugtracker: https://developer.blender.org/T37504

This should be really easy to reproduce. I use Archlinux with the latest software.

Comment 1 nucrap 2014-06-09 23:43:15 UTC

Created attachment 100777 [details]
glitch in blender menu 2

Comment 2 smoki 2014-06-10 05:48:23 UTC

 Cannot reproduce by maximizing this in current Debian Sid: kernel 3.14.5, mesa 10.1.4, blender 2.70, openbox, Radeon 8400 / r3.

 But of course i can see those artifacts when resizing, but it got refreshed here does not stay :). 

 Area with those artifacts are black with LIBGL_ALWAYS_SOFTWARE=1 blender

Comment 3 Michel Dänzer 2014-06-10 06:18:40 UTC

I think this is more likely a generic DRI2 issue related to front buffer rendering than anything driver specific.

Comment 4 Sven Arvidsson 2014-07-31 15:46:12 UTC

I used to see this all the time, but not lately. 

For me it was specific to r600g, I have never seen this on i965.

Comment 5 Edward O'Callaghan 2016-11-05 12:49:23 UTC

(In reply to Michel Dänzer from comment #3)
> I think this is more likely a generic DRI2 issue related to front buffer
> rendering than anything driver specific.

Correct yes,

Run blender with `LIBGL_DRI3_DISABLE=1`. I reported it to them however they don't listen well.

Comment 6 Michel Dänzer 2017-03-18 02:27:51 UTC

Assuming this is fixed, per comment 4. Please don't reopen unless this can be reproduced with DRI2.

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.