Segfault when starting blender #48700

New Issue

Stephane Mutz · 2016-06-21T18:14:18+02:00

Stephane Mutz commented

2016-06-21 18:14:18 +02:00

System Information
Linux Mint 17.3 VM (KVM) running on Dell R610 server with remote X connection (X2go)

Blender Version
Broken: latest git tree as of 2016-06-21
Worked: (optional)

Short description of error
Blender crashes with an Xerror:
Received X11 Error:
error code: 1
request code: 147
minor code: 34
error text: BadRequest (invalid request code or no such operation)
Segmentation fault
Thhis happens before the splash screen (or has it is being drawns)

Exact steps for others to reproduce the error
Compile blender from the git tree as described in the wiki for Ubuntu distribution
on a Linux Mint 17.3 VM. Run blender over x2go connection.

**System Information** Linux Mint 17.3 VM (KVM) running on Dell R610 server with remote X connection (X2go) **Blender Version** Broken: latest git tree as of 2016-06-21 Worked: (optional) **Short description of error** Blender crashes with an Xerror: Received X11 Error: error code: 1 request code: 147 minor code: 34 error text: BadRequest (invalid request code or no such operation) Segmentation fault Thhis happens before the splash screen (or has it is being drawns) **Exact steps for others to reproduce the error** Compile blender from the git tree as described in the wiki for Ubuntu distribution on a Linux Mint 17.3 VM. Run blender over x2go connection.

Stephane Mutz commented

2016-06-21 18:14:18 +02:00

Changed status to: 'Open'

Stephane Mutz commented

2016-06-21 18:14:18 +02:00

Added subscriber: @smutz

NikoLeopold commented

2016-06-21 18:55:39 +02:00

Added subscriber: @NikoLeopold

NikoLeopold commented

2016-06-21 18:55:39 +02:00

147 should be about GLX (OpenGL Extension to the X Window System).
What version of OpenGL / GLX does your system implement? Check via glxinfo | grep -i version.
Could be that your client requires a more recent version not compatible with what X2Go supports: It seems that X2Go is based on nxagent which supports GLX only up to 1.2.
http://wiki.x2go.org/doku.php/doc:de-compat
It also says that Cinnamon 2.2 (Linux Mint 17) is not compatible and reverts to fallback mode.

Maybe that could be the reason?

147 should be about GLX (OpenGL Extension to the X Window System). What version of OpenGL / GLX does your system implement? Check via `glxinfo | grep -i version`. Could be that your client requires a more recent version not compatible with what X2Go supports: It seems that X2Go is based on nxagent which supports GLX only up to 1.2. http://wiki.x2go.org/doku.php/doc:de-compat It also says that Cinnamon 2.2 (Linux Mint 17) is not compatible and reverts to fallback mode. Maybe that could be the reason?

Stephane Mutz commented

2016-06-21 19:01:01 +02:00

A GLX related issue would not be surprising indeed. This is the glxinfo results:
server glx version string: 1.2
client glx version string: 1.4
GLX version: 1.2
OpenGL version string: 2.1 Mesa 10.1.3
OpenGL shading language version string: 1.30

Is there a compatibilty issue?

A GLX related issue would not be surprising indeed. This is the glxinfo results: server glx version string: 1.2 client glx version string: 1.4 GLX version: 1.2 OpenGL version string: 2.1 Mesa 10.1.3 OpenGL shading language version string: 1.30 Is there a compatibilty issue?

NikoLeopold commented

2016-06-21 19:21:19 +02:00

Since X2Go only supports GLX until 1.2 and your client has 1.4 that could be it.
Did you try any other OpenGL apps?

Since X2Go only supports GLX until 1.2 and your client has 1.4 that could be it. Did you try any other OpenGL apps?

Stephane Mutz commented

2016-06-21 19:24:26 +02:00

CAD tools using OpenGL we use are working fine. So does glxgears.

NikoLeopold commented

2016-06-21 19:53:33 +02:00

Only thing i can guess is that Blender needs some specific functions related to GLX >1.2 and then crashes.
Found this possible workaround but haven't looked into it: http://wiki.x2go.org/doku.php/wiki:development:glx-xlib-workaround

Only thing i can guess is that Blender needs some specific functions related to GLX >1.2 and then crashes. Found this possible workaround but haven't looked into it: http://wiki.x2go.org/doku.php/wiki:development:glx-xlib-workaround

Campbell Barton commented

2016-06-21 20:12:05 +02:00

Changed status from 'Open' to: 'Resolved'

Campbell Barton closed this issue

2016-06-21 20:12:05 +02:00

blender-admin commented

2016-06-21 20:17:02 +02:00

This issue was referenced by e783fddc01

This issue was referenced by e783fddc0167eeb58bd69ed08ff31d0746772ad6

Campbell Barton commented

2016-06-21 20:45:17 +02:00

Added subscriber: @ideasman42

Campbell Barton commented

2016-06-21 20:45:17 +02:00

We now depend on OpenGL2.1,
If GLX fails to initialize, its unlikely we can work-around this (unless its a mistake or so).
However since this is remote desktop software, its likely a limit in its GLX support.
So for now just avoid crash and fail gracefully.

We now depend on OpenGL2.1, If GLX fails to initialize, its unlikely we can work-around this (unless its a mistake or so). However since this is remote desktop software, its likely a limit in its GLX support. So for now just avoid crash and fail gracefully.

Stephane Mutz commented

2016-06-21 22:32:11 +02:00

Ok, that's clear. Remote desktops are often limited in which version of OpenGL is supported. We use it extensively to share more powerful servers so it would have been convenient. Anyway, a graceful failure is preferable to a crash. Thank you for the very reactive feedback.

Campbell Barton commented

2016-06-21 22:38:33 +02:00

Note that in cases like this it can work to use software-gl

Run blender-softwaregl or set LIBGL_ALWAYS_SOFTWARE,

Of course software gl may be unusably slow. YMMV.

Note that in cases like this it can work to use software-gl Run blender-softwaregl or set LIBGL_ALWAYS_SOFTWARE, Of course software gl may be unusably slow. YMMV.

Stephane Mutz commented

2016-06-22 10:10:45 +02:00

I tested the latest tree this morning. The segfault is gone but I get only a window frame and the executable remains stuck in this state with the Xerror reported in the shell. So in short, no more crash but no graceful exit either.
I tried the sotftwaregl option (both through the var and the command line option) and the result is the same. glxinfo outputs the same openGL version info. I believe this is due to x2go and I will check on this side what limits the openGL version supported in software rendering.
The speed would not be a major concern as I intend to explore how I could use Blender for radio wave propagation simulations in relatively simple geometries (by modifying the renderer). My fallback is to switch to a local VM and see if I can make it work there.

I tested the latest tree this morning. The segfault is gone but I get only a window frame and the executable remains stuck in this state with the Xerror reported in the shell. So in short, no more crash but no graceful exit either. I tried the sotftwaregl option (both through the var and the command line option) and the result is the same. glxinfo outputs the same openGL version info. I believe this is due to x2go and I will check on this side what limits the openGL version supported in software rendering. The speed would not be a major concern as I intend to explore how I could use Blender for radio wave propagation simulations in relatively simple geometries (by modifying the renderer). My fallback is to switch to a local VM and see if I can make it work there.

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

Segfault when starting blender #48700