Page MenuHome

ChromeOS: Black screen/window on startup:
Needs Information from Developers, NormalPublicBUG

Description

System Information
Operating system: Chromeos 83/84/85 buildin linux VM
Graphics card: Intel Gen8, HD Graphics 5500/UHD Graphics 620

Blender Version
Broken: (2.83 LTS, 2.90 Aplha)
Worked: (2.82a)

Short description of error
Black window/screen never shows the splashscreen
See attached picture

Warning: Could not find a matching GPU name. Things may not behave as expected.
Detected OpenGL configuration:
Vendor: Red Hat
Renderer: virgl

Exact steps for others to reproduce the error
Based on the default startup or an attached .blend file (as simple as possible).

  1. start ./blender from its home folder
  2. Black window/screen shows up

P1458

Event Timeline

I have tried with blender-softwaregl and it starts blender (both 2.83,290) but its too slow ofcause as no hardware acceleration is used.

Its a chromebook,so thats not possible and 2.82a works

Received X11 Error:

error code:   165
request code: 150
minor code:   34
error text:   GLXBadFBConfig
Received X11 Error:

error code:   165
request code: 150
minor code:   34
error text:   GLXBadFBConfig
Warning: Could not find a matching GPU name. Things may not behave as expected.
Detected OpenGL configuration:
Vendor: Red Hat ...

Please run

./blender --python-expr "import bpy; bpy.ops.wm.sysinfo(filepath=r'./blender_system_info.txt')"

and upload the file.

Here you go

and one for blender 2.9 as well

renderer:	'virgl'
vendor:		'Red Hat'
version:	'4.3 (Core Profile) Mesa 19.2.8'

Its a chromebook,so thats not possible and 2.82a works

@Kåre Baastrup (baastrup) So are you stuck with this Mesa version ? Mesa 20.x is the latest.

Warning: Could not find a matching GPU name. Things may not behave as expected.

@Clément Foucault (fclem) is this renderer not supported?

found a way to replace the debain container with arch linux but seems to be the same issue. see attached file.

Arch glxinfo -B
name of display: :0
display: :0 screen: 0
direct rendering: Yes
Extended renderer info (GLX_MESA_query_renderer):

Vendor: Red Hat (0x1af4)
Device: virgl (0x1010)
Version: 20.1.1
Accelerated: yes
Video memory: 0MB
Unified memory: no
Preferred profile: core (0x1)
Max core profile version: 4.3
Max compat profile version: 3.1
Max GLES1 profile version: 1.1
Max GLES[23] profile version: 3.2

OpenGL vendor string: Red Hat
OpenGL renderer string: virgl
OpenGL core profile version string: 4.3 (Core Profile) Mesa 20.1.1
OpenGL core profile shading language version string: 4.30
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile


OpenGL version string: 3.1 Mesa 20.1.1****
OpenGL shading language version string: 1.40
OpenGL context flags: (none)

OpenGL ES profile version string: OpenGL ES 3.2 Mesa 20.1.1
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20

Ankit Meel (ankitm) renamed this task from Black screen/window on startup to ChromeOS: Black screen/window on startup: .Jun 18 2020, 2:42 PM
Ankit Meel (ankitm) changed the task status from Needs Triage to Needs Information from Developers.
Ankit Meel (ankitm) updated the task description. (Show Details)

@Ankit Meel (ankitm) Hello. Any any updates on this bug? I just tried loading today's daily build, blender-2.90.0-b4e1571d0bcf-linux64 , and the issue persists.

I asked the developers: Blender doesn't treat virgl differently. That's why you see "Warning: Could not find a matching GPU name. Things may not behave as expected." in the console from gpu_platform.c .
So it has to be reviewed if it should be supported or not.

A note from me is that if some commit unintentionally broke the compatibility between 2.82a, and 2.83, git bisect can find the problem.
See this concise answer : https://stackoverflow.com/a/37306623
start with git bisect bad 2.83 , git bisect good 2.82a. Then it'll checkout a commit in between, run make and test that Blender opens. If it does, enter git bisect good otherwise git bisect bad and repeat.

This comment was removed by LF (Phoney).

Have you downloaded the source code ? https://wiki.blender.org/wiki/Building_Blender/Linux/Generic_Distro#Quick_Setup
For build questions, https://devtalk.blender.org/c/blender/building-blender/11
It's okay to not try it, if it becomes too much trouble.

Using git is seeming difficult for me. I've never used it before.

Is there any other way to fix this?

Using git is seeming difficult for me. I've never used it before.

You could ask doubts on https://blender.chat too.
Otherwise, before a developer decides to tackle this bug report, you may use 2.82a. https://download.blender.org/release/

Wait, what about the Steam version of Blender?

Clément Foucault (fclem) changed the subtype of this task from "Report" to "Bug".

This happens on my brand new Asus chromebook flip with 10th gen intel chipset as well. tested 2.83.2 as well

@Clément Foucault (fclem), maybe we should try just recognizing virgl as an Intel? Since that's the most likely one to be used. I'm not sure if that will actually solve the issue, but seems worth trying.

If it does work, we could perhaps also ask the virgl developers to pass through the renderer information.

Same issue with 2.83.4 and 2.91

I report all the same issues on my 2015 Pixelbook.

2.82a works, all subsequent versions black screen on start up.

Shouldn't this be labeled a regression? Also, I got a system dialog saying the app wasn't responding... might not be entirely graphics related.

Same issue on 2.90.1 with a an HP 360x 14c. I installed using the flatpak. The snap seems to try to run, but was so slow it... never really got there. Gimp for instance takes a whole minute to run with the software emulated snap, but with flatpak, it flies.

For reference, we can't modify the of the default debian image. To use other images we have to disable quite a few protections and deal with warnings and additional friction, developer mode is a lot like rooting an Android Phone or running Windows 10 Ameliorated edition.

(ChromeOS support for Linux is insanely good, aside from USB passthrough being mostly missing. I'm just happy to have linux on a fast 14 hour laptop.)

Same issue with 2.91 ;-(

Seems to be a packaging issue with OpenGL and Python... Lots of others have issues in Ubuntu as well

https://github.com/flathub/org.blender.Blender/issues/31

There is a workaround, but it will mean Blender will run like a dog. I got the latest 2.91 to run on my chromebook using:

LIBGL_ALWAYS_SOFTWARE=1 blender

But it would be great if the developers would let 2.91 run as well as 2.82 did. Seems we are to be frozen in time on ChromeOS

In fact the only solution I've found is install a dual boot version of linux, and that will run 2.91 fine-ish. Clearly not hardware, this is a software issue that seems unsolvable for crostini or whatever chromeos version of linux is.

LIBGL_ALWAYS_SOFTWARE=1 blender seems to start blender 2.91.2 but its useless

Hope someone can find the diffrents between 282 and 2.91.2 and fix it ;-)

Still and issue with 2.9.2 ;-(

~/blender-2.92.0-linux64$ ./blender
Warning: Could not find a matching GPU name. Things may not behave as expected.
Detected OpenGL configuration:
Vendor: Red Hat
Renderer: virgl
/run/user/1000/gvfs/ non-existent directory

@Ankit jain (Ankit) Meel (ankitm)

Version 2.9.2 same issue persists. We're coming up on a year since this issue was first reported. What needs to be done to get the developers to fix this issue?