Page MenuHome

Can not open Blender 2.81.12 under Ubuntu 18.04.3 LTS
Open, Needs Triage by DeveloperPublic

Description

System Information
Operating system: Linux-5.0.0-29-generic-x86_64-with-debian-buster-sid 64 Bits
Graphics card: AMD RV630 (DRM 2.50.0 / 5.0.0-29-generic, LLVM 8.0.0) X.Org 3.3 (Core Profile) Mesa 19.0.8

Blender Version
Broken: version: 2.81 (sub 12), branch: master, commit date: 2019-09-23 20:20, hash: rB5a6ab6f59468

Short description of error
I can't start Blender 2.81.12 alpha, just getting a black screen inside a freshly drawn window and a full crash after a few seconds. Versions 2.80.75 (stable release) and 2.81.11 opened without any hiccups. The complete error list I get after starting Blender 2.81.2 from the Terminal:

Read prefs: /home/username/.config/blender/2.81/config/userpref.blend
Received X11 Error:
error code: 170
request code: 153
minor code: 34
error text: GLXBadFBConfig
Received X11 Error:
error code: 170
request code: 153
minor code: 34
error text: GLXBadFBConfig
Received X11 Error:
error code: 170
request code: 153
minor code: 34
error text: GLXBadFBConfig
Received X11 Error:
error code: 170
request code: 153
minor code: 34
error text: GLXBadFBConfig
Received X11 Error:
error code: 170
request code: 153
minor code: 34
error text: GLXBadFBConfig
Received X11 Error:
error code: 170
request code: 153
minor code: 34
error text: GLXBadFBConfig
Received X11 Error:
error code: 8
request code: 153
minor code: 34
error text: BadMatch (invalid parameter attributes)
Received X11 Error:
error code: 8
request code: 153
minor code: 34
error text: BadMatch (invalid parameter attributes)
Received X11 Error:
error code: 8
request code: 153
minor code: 34
error text: BadMatch (invalid parameter attributes)
Received X11 Error:
error code: 8
request code: 153
minor code: 34
error text: BadMatch (invalid parameter attributes)
Received X11 Error:
error code: 8
request code: 153
minor code: 34
error text: BadMatch (invalid parameter attributes)
Received X11 Error:
error code: 8
request code: 153
minor code: 34
error text: BadMatch (invalid parameter attributes)
found bundled python: /opt/blender/2.81/python
Writing: /tmp/blender.crash.txt
Segmentation fault (core dumped)

The file /tmp/blender.crash.txt contains:

Blender 2.81 (sub 12), Commit date: 2019-09-23 20:20, Hash 5a6ab6f59468

backtrace

./blender(BLI_system_backtrace+0x1d) [0x14dce4d]
./blender() [0x12beb99]
/lib/x86_64-linux-gnu/libc.so.6(+0x3ef20) [0x7fbdada52f20]
./blender(GPU_draw_list_command_add+0x48) [0x441c188]
./blender() [0x2b90c50]
./blender() [0x2b91fef]
./blender(workbench_deferred_draw_scene+0x4f2) [0x2bbffb2]
./blender() [0x2bbc7bb]
./blender(DRW_draw_render_loop_ex+0x274) [0x2b8b6c4]
./blender(view3d_main_region_draw+0x77) [0x2e66427]
./blender(ED_region_do_draw+0x8d1) [0x2edb461]
./blender(wm_draw_update+0x496) [0x168d876]
./blender(WM_main+0x30) [0x168af30]
./blender(main+0x2fe) [0x122af9e]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xe7) [0x7fbdada35b97]

Details

Type
Bug

Event Timeline

I see 2.81 daily builds also crash on OSX for 2 days know. Yesterday console showed something about illegal action??
Today i see this

dyld: lazy symbol binding failed: Symbol not found: _os_unfair_lock_lock
  Referenced from: /Applications/blender-2.81/Blender.app/Contents/MacOS/Blender
  Expected in: /usr/lib/libSystem.B.dylib

dyld: Symbol not found: _os_unfair_lock_lock
  Referenced from: /Applications/blender-2.81/Blender.app/Contents/MacOS/Blender
  Expected in: /usr/lib/libSystem.B.dylib

Trace/BPT trap: 5
logout

@Rombout Versluijs (rombout) that's an unrelated issue, please create a separate report for that. I guess you are using macOS 10.11 or older.

Hi @Anton Raves (Memento)

Can you check if blender starts when using
blender --factory-startup

Can you otherwise check if you can start blender when enabling some gpu workarounds
blender --debug-gpu-force-workarounds

The AMD/Mesa driver is flaky is some areas and this particular issue might have been solved by T70187: Segmentation fault with edit mode operation

Also note that your GPU is from 2007 and not officially supported (https://code.blender.org/2019/04/supported-gpus-in-blender-2-80/).

We accept community help to support these devices; but I hope the work around will work for you.

Bastien Montagne (mont29) lowered the priority of this task from Needs Triage by Developer to Needs Information from User.Wed, Sep 25, 8:41 AM

Goedemorgen Jeroen,

The

blender --factory-startup

check was what I did before reporting this issue, with the

blender --debug-gpu-force-workarounds

terminal command the Blender version 2.81.2 from yesterday launches all the way up into the Splash Screen! I can open files again and start renders... Yeah!

@Rombout Versluijs (rombout) that's an unrelated issue, please create a separate report for that. I guess you are using macOS 10.11 or older.

Correct, im on 10.12.6

Ill try to make a new post

I can guarantee that it works on linux with recent mesa drivers, I have an old laptop with a similar gpu .. there were some minor bugs in the display of the meshes, but perhaps with the implemented workaround they will have been solved (I have not yet verified this)

also try using

R600_DEBUG=nosb ./blender --debug-gpu-force-workarounds

by disabling backend shading acceleration you have more chances that it works, by unfortunately sacrificing fast compiling of shaders.

Edit:
I just did a test now out of curiosity.
it is obviously slower, soo slower, but it works.
eevee has the exact same problem with the acceleration of the shading backend of my radeon hd 7670.
https://www.phoronix.com/scan.php?page=news_item&px=MTQ0OTM
(better to turn off antialiasing features from blender preferences, they make visual defects.)

GPU: Bypassing workaround detection.
GPU: OpenGL identification strings
GPU: vendor: X.Org
GPU: renderer: AMD RV630 (DRM 2.50.0 / 5.0.0-27-generic, LLVM 9.0.0)
GPU: version: 3.3 (Core Profile) Mesa 19.3.0-devel (git-88f909e 2019-09-25 bionic-oibaf-ppa)

intel core duo 2.4 ghz , 2 gb ram , radeon HD 2000 512 mb ram. antialiasing dislabled, screen 1280x1024 , 2007 laptop, last mint linux , oibaf MESA ppa

R600_DEBUG=nosb,hyperz,llvm,sisched, ./blender --debug-gpu-force-workarounds

it could be better if the back-end shader acceleration worked

@Jeroen Bakker (jbakker) If you team solve this problem of the inverted colors of the shader back-end accelerator , you will extend the use of blender 2.8 to work well at 10 years of AMD gpu. from 2006 to 2016 more or less.
I think it's convenient. does not seem such a serious problem, also because in the first versions of blender 2.80 it worked well, it is just that until now no dev had a gpu of these on linux to be able to eliminate the bug.

I collected information here
https://devtalk.blender.org/t/amd-r600-mesa-linux-driver-eevee-broken/9294

Brecht Van Lommel (brecht) raised the priority of this task from Needs Information from User to Needs Triage by Developer.Mon, Oct 7, 11:37 PM