Page MenuHome

System freezes completely on staring Blender 2.8 (Ubuntu using RX 5700)
Open, Needs Triage by DeveloperPublic


System Information
Operating system: Ubuntu 18.04 LTS and 19.04
Graphics card: Sapphire Radeon RX 5700 ("reference card")

Blender Version
Broken: tested (2.81 Alpha, 900a9a4b06a6, master, 2019-09-25) and (2.80 Release, 2019-07-30)
Worked: (2.79.b, 2019-09-24 last updated in repository)

Short description of error
If I try to open Blender the screen (to be more exact both of my screens) freeze. The audio of music or videos I had opened in other applications still play but everything is frozen except my mouse-cursor. But not a single window reacts to clicks or any key-presses. I can only end this state of my system by rebooting the whole computer. So I can't practically use the current version of Blender.

Exact steps for others to reproduce the error
If you have a Navi-GPU from AMD and their amdgpu-pro-drivers installed (which support Ubuntu 18.04) on Ubuntu 18.04 or 19.04, you should be able to reproduce it by executing the "blender" called binary from Blender 2.80. The other binary "blender-softwaregl" does not cause this error in any version tested but is rather slow in performance (but I guess this is expected).

My thoughts what causes the problem
The reason I post this problem around here and not only to the side of AMDs support fixing the drivers is that I think I know what's causing this problem. Because Blender 2.79 still seems to work fine on Ubuntu, I thought it could have something to do with Blender using Uniform Buffer Objects or even Shader Storage Buffer Objects from OpenGL in a wrong way. This thought came to me when I tried to develop an own application on my system using OpenGL 4.3 and its SSBOs in a shader but I made the mistake to call the shader before binding a SSBO to the appropriate Shader Storage Buffer Block. The result was the same error I got from calling Blender. So maybe it could just be fixed like in my own code by swapping some few lines in order which would remove this undefined behavior which causes this problem with the current Navi-drivers from AMD. Because I think AMD will probably need more time than you guys. Keep up the great work!



Event Timeline

This seem directly related to the OpenGL support of your card in your environment. Using "Software-gl" is only using the CPU to do everything. Have you tried something else that require HARDWARE OPENGL on your system? It almost look like you don't have openGL drivers installed. Version 2.79 is less demanding for video card requirement and can almost run on anything.

I have installed the official drivers from AMD for Ubuntu which can be found here:

The problem with my graphics card is that it is really new and the most forums tell you need mesa 19.2 and Linux 5.13 installed at least. But Ubuntu got official drivers, so I could use a linux distro in a more stable way.

I have also a partition with Archlinux using the mesa-git repository but I get system wide freezes on it more randomly than on Ubuntu. So I stay with it until they release properly running drivers and firmware. What I could test on Arch so far seems to conclude that my 'problem' is mostly depending on the drivers. Blender 2.8 seems to run fine.

But since I had tested debugging my own lines of code and I got the same result, I thought I should report this problem. Because maybe it depends on a wrong/undefined use of OpenGL in Blender too.

Anyway to answer your question if something else using OpenGL runs:

  • "Tomb Raider" starts but does not render properly
  • "Witcher 2" runs fine without problems on high settings
  • "BioShock Infinite" starts but renders a black screen
  • "Counter-Strike: Global Offensive" is not responding
  • "Cities: Skylines" crashes
  • "HITMAN" runs perfectly on high settings
  • "Dota 2" runs fine using independent of using the Vulkan- or OpenGL-port
  • "Deus Ex: Mankind Divided" runs okay (performance is playable I guess but no problems)

These games should all make use of OpenGL on linux as far as I know.