Can not open Blender 2.81.12 under Ubuntu 18.04.3 LTS #70209

New Issue

Anton Raves · 2019-09-24T17:09:08+02:00

Anton Raves commented

2019-09-24 17:09:08 +02:00

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: 5a6ab6f594

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 `5a6ab6f594`

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]

**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: `5a6ab6f594` **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]

Anton Raves commented

2019-09-24 17:09:08 +02:00

Added subscriber: @Memento

Rombout Versluijs commented

2019-09-24 18:37:16 +02:00

Added subscriber: @RomboutVersluijs

Rombout Versluijs commented

2019-09-24 18:37:16 +02:00

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

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 ```

Brecht Van Lommel commented

2019-09-24 19:10:05 +02:00

Added subscriber: @brecht

Brecht Van Lommel commented

2019-09-24 19:10:05 +02:00

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

Jeroen Bakker commented

2019-09-25 07:46:25 +02:00

Added subscriber: @Jeroen-Bakker

Jeroen Bakker commented

2019-09-25 08:15:25 +02:00

Hi @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 #70187 (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.

Hi @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 #70187 (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.

Anton Raves commented

2019-09-25 08:57:21 +02:00

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!

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 commented

2019-09-25 16:52:35 +02:00

In #70209#782787, @brecht wrote:
@RomboutVersluijs 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

> In #70209#782787, @brecht wrote: > @RomboutVersluijs 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

noki paike commented

2019-09-25 22:18:47 +02:00

Added subscriber: @nokipaike

noki paike commented

2019-09-25 22:18:47 +02:00

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.)

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.)

noki paike commented

2019-09-25 23:51:16 +02:00

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

test.mkv

``` 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 [test.mkv](https://archive.blender.org/developer/F7775214/test.mkv)

noki paike commented

2019-09-27 13:39:34 +02:00

@Jeroen-Bakker 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

@Jeroen-Bakker 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

pat commented

2020-01-01 14:13:25 +01:00

Added subscriber: @pat-3

pat commented

2020-01-01 14:13:25 +01:00

hi,
i have the same problem that in previous post :
Blender 2.81 (sub 12), Commit date: 2019-09-23 20:20, Hash 5a6ab6f594
backtrace

premierstests-iceland-r101-03.crash.txt

i don't know how to solve , thinked that nvidia driver was in cause , but do the same error with nvidia 340 and 390 , cant test 435 doesn't work

my config is ubuntu 18.04lts 64 NVIDIA gt730 (64-2GB GDDR5) MB: P5K Q9400 quad-core 8GB tests with both GPU CPU in cuda settings
fresh installed system since 2 weeks looks stable & python 2.7 ? should have an effect ?.

Thanks,
Bye

hi, i have the same problem that in previous post : Blender 2.81 (sub 12), Commit date: 2019-09-23 20:20, Hash 5a6ab6f59468 backtrace [premierstests-iceland-r101-03.crash.txt](https://archive.blender.org/developer/F8254722/premierstests-iceland-r101-03.crash.txt) i don't know how to solve , thinked that nvidia driver was in cause , but do the same error with nvidia 340 and 390 , cant test 435 doesn't work my config is ubuntu 18.04lts 64 NVIDIA gt730 (64-2GB GDDR5) MB: P5K Q9400 quad-core 8GB tests with both GPU CPU in cuda settings fresh installed system since 2 weeks looks stable & python 2.7 ? should have an effect ?. Thanks, Bye

Richard Antalik commented

2020-01-13 16:22:28 +01:00

Added subscriber: @iss

Richard Antalik commented

2020-01-13 16:22:28 +01:00

Changed status from 'Needs Triage' to: 'Needs User Info'

Richard Antalik commented

2020-01-13 16:22:28 +01:00

@Memento Is this still an issue with latest build? https://builder.blender.org/download/

Anton Raves commented

2020-01-13 16:42:51 +01:00

I have been running the 2.82 beta on that same machine now, which has been updated to Ubuntu 19.10 in the mean time. So not an issue at this moment, no.

Richard Antalik commented

2020-01-13 18:02:55 +01:00

Changed status from 'Needs User Info' to: 'Resolved'

Richard Antalik closed this issue

2020-01-13 18:02:55 +01:00

Richard Antalik self-assigned this 2020-01-13 18:02:55 +01:00

Richard Antalik commented

2020-01-13 18:02:55 +01:00

Thanks for update.

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Can not open Blender 2.81.12 under Ubuntu 18.04.3 LTS #70209

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

backtrace

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