Bug 24868

Summary: Blender 2.80 user interface unusable with AMD A10 Kaveri and Mesa radeonsi
Product: Mageia Reporter: Richard Walker <richard.j.walker>
Component: RPM PackagesAssignee: Thomas Backlund <tmb>
Status: NEW --- QA Contact:
Severity: normal    
Priority: Normal CC: fri, tmb
Version: Cauldron   
Target Milestone: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Source RPM: mesa-19.1.0-0.rc3.1.mga7.src.rpm CVE:
Status comment:
Attachments: Correct appearance of Blender viewport
Blender viewport decorations missing

Description Richard Walker 2019-05-26 04:46:45 CEST 
Description of problem:
The new Blender user interface depends on OpenGL 3.1+. With no proprietary alternative for AMD GPUs there is only Mesa.

The screen effect is of overlays flashing on and off and an inability to select parts of a mesh with the mouse. Any attempt to select an edge or vertex causes the tool selection icon for "Move" to be selected and "Select" is deselected.

When rendering an image there is a random visible/invisible appearance of rendered tiles and when completed, all tiles but two are visible. The saved image on disc is correct. The degree of the visible render problem can be alleviated by selecting "2D Texture" rather than "Automatic" or "GLSL" for the Viewport drawing method in User Preferences, but not eliminated. 

The choice of "2D Texture" or "GLSL" has no effect on viewport behaviour.

The problem persists regardless of Blender 2.80 version. I have verified this with a variety of local build RPMs from git20190504 to the current Mageia release. The problem also exists in all Blender.org nightly builds I have tried over the same period.

The problem first appeared after installation of recent Mageia updates, including Mesa 19.1 rc3.1.

Version-Release number of selected component (if applicable):
The problem first appeared after installation of recent Mageia updates, including Mesa 19.1 rc3.1, on or about 21 May.


How reproducible:
There is no way I can find to stop it from happening every time I use Blender 2.80. However a similarly configured Mageia 7 system which still uses Mesa 19.1 rc3.5 and has not had the 21 May updates applied, works perfectly well with all of the many Blender 2.80 iterations at my disposal, including the current Mageia release.

Steps to Reproduce:
1.
2.
3.
Comment 1 Richard Walker 2019-05-26 04:50:31 CEST 
Correction to above:

How reproducible:
There is no way I can find to stop it from happening every time I use Blender 2.80. However a similarly configured Mageia 7 system which still uses Mesa 19.1 rc2.5 and has not had the 21 May updates applied, works perfectly well with all of the many Blender 2.80 iterations at my disposal, including the current Mageia release.

I mistakenly referred to the working Mesa as rc3.5 when it is actually rc2.5
Comment 2 Richard Walker 2019-05-26 04:57:41 CEST 
It may not be relevant, but the reason for updating the Mageia 7 installation was to test a partial solution to Bug 24546 (https://bugs.mageia.org/show_bug.cgi?id=24546)

This required an update to the nvidia-current packages, and nvidia-cuda-toolkit in order to test a workaround to that problem. All of the other updates looked harmless enough, even desirable, so I installed every update.
Comment 3 Richard Walker 2019-05-26 05:20:29 CEST 
Created attachment 11028 [details]
Correct appearance of Blender viewport

This screengrab from the Mesa 19.1 rc2.5 system shows the correct display of Viewport overlays and the 2D grid
Comment 4 Richard Walker 2019-05-26 05:22:38 CEST 
Created attachment 11029 [details]
Blender viewport decorations missing

This pic is from the Mesa 19.1 rc3.1 system and clearly shows the missing elements.
Comment 5 Thomas Backlund 2019-05-26 09:43:06 CEST 
yes, I'm aware of the bug.

There is a known regression in upstream mesa, I will fix it up today

CC: (none) => tmb

Thomas Backlund 2019-05-26 11:03:33 CEST

Assignee: bugsquad => tmb

Comment 6 Thomas Backlund 2019-05-26 14:28:13 CEST 
Please try with mesa-19.1.0-0.rc3.2.mga7
Comment 7 Morgan Leijström 2023-08-19 00:42:18 CEST 
I believe this got resolved?

CC: (none) => fri