ChromeOS: Black screen/window on startup: #77651
Labels
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset System
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Viewport & EEVEE
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Asset Browser Project
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Module
Viewport & EEVEE
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Severity
High
Severity
Low
Severity
Normal
Severity
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
18 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#77651
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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 Alpha)
Worked: (2.82a)
First bad commit:
001f7c92d1
Short description of error
![Screenshot 2020-06-08 at 22.27.27.png](https://archive.blender.org/developer/F8602589/Screenshot_2020-06-08_at_22.27.27.png)
Black window/screen never shows the splashscreen
See attached picture
Exact steps for others to reproduce the error
Based on the default startup or an attached .blend file (as simple as possible).
P1458
Added subscriber: @baastrup
#80674 was marked as duplicate of this issue
#77970 was marked as duplicate of this issue
#77952 was marked as duplicate of this issue
Added subscriber: @ankitm
https://developer.blender.org/T72098#938339
https://developer.blender.org/T77381#945090
Try these workarounds
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.
Added subscriber: @mano-wii
Have you tried upgrading GPU drivers? See https://docs.blender.org/manual/en/dev/troubleshooting/gpu/index.html
Its a chromebook,so thats not possible and 2.82a works
Please run
and upload the file.
blender_system_info.txt
Here you go
blender_system_info.txt
and one for blender 2.9 as well
Added subscriber: @fclem
@baastrup So are you stuck with this Mesa version ? Mesa 20.x is the latest.
@fclem is this renderer not supported?
blender_system_info.txt
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):
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
Added subscriber: @AestheticArson
Black screen/window on startupto ChromeOS: Black screen/window on startup:Changed status from 'Needs Triage' to: 'Needs Developer To Reproduce'
@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, runmake
and test that Blender opens. If it does, entergit bisect good
otherwisegit bisect bad
and repeat.Added subscribers: @Phoney, @EAW
This comment was removed by @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?
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/
Good idea
Wait, what about the Steam version of Blender?
This happens on my brand new Asus chromebook flip with 10th gen intel chipset as well. tested 2.83.2 as well
Added subscriber: @brecht
@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
Same issue with 2.90
Added subscriber: @biscuitlad
I report all the same issues on my 2015 Pixelbook.
2.82a works, all subsequent versions black screen on start up.
Added subscriber: @rayfoss
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.)
Added subscriber: @rsturgell
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
Removed subscriber: @rayfoss
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:
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 ;-)
Added subscriber: @eric.svard
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
Added subscriber: @Ankit-1
@Ankit-1 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?
Removed subscriber: @Ankit-1
Added subscriber: @PratikPB2123
@ankitm ^
Added subscriber: @mkimball
Another datapoint - Blender 2.82a works fine on my Asus Flip C434, but Blender 2.92.0 does not work. (Other than with 'LIBGL_ALWAYS_SOFTWARE')
Regarding "maybe we should try just recognizing virgl as an Intel", I tried modifying 'GLBackend::platform_init()' to do this, and it did not help. I also enabled all GL workarounds, as seen at the top of 'detect_workarounds()' at that didn't fix the issue either.
Added subscriber: @Pykorm
Added subscriber: @sabai
I see this issue persists with v2.92 on Chrome v90.
Is a fix in progress?
Cheers
Added subscriber: @david82194
I ran git bisect between 2.82a and 2.83 on my Acer Chromebook Spin 713.
The offending commit for me is 001f7c92d1452e01622f066d37bd42545b650a27 .
Reverting it allows v2.83 to start on my chromebook.
Note that the virgl warning appears on working and non-working versions.
Changed status from 'Needs Developer To Reproduce' to: 'Confirmed'
Thanks for the bisect @dave1853.
We could revert that commit, but it brings more than a simple optimization.
There is a reduction in memory usage in the VRAM (especially when the font is resized).
Before any further action, it would be useful to be able to identify what the real trigger of this driver problem is.
So, for anyone who is able to replicate the problem and compile the Blender code, could you test some code changes to find out what causes it?
The changes to test would look something like this:
Even if the interface is messy, if Blender doesn't turn black it's a good sign.
It might also be useful to run blender with the
--debug-gpu
arg:https://docs.blender.org/manual/en/latest/advanced/command_line/render.html
Commenting out the size_x lines in
texel_fetch
ofsource/blender/gpu/shaders/gpu_shader_text_frag.glsl
seems to fix the issue. I think the driver doesn't like thetextureSize
call.What do the lines I commented out do?
If they're meaningful, perhaps we can work around this by passing the texture size in as a uniform.
Commenting out those 4 lines allows v2.93 to work on my chromebook as well.
Here is a build of v2.93 for anyone who needs it:
https:*drive.google.com/file/d/19PlYHfS-DK5V3E1GxiSIfYULDJaYnHoh/view?usp=sharing
This issue was referenced by
a925c8969d
This issue was referenced by
706c7d775d
This issue was referenced by
6e56b42faa
Good to see we're getting close to a solution :)
GPUTexture
s have a relatively small width and height limit (this is seen inGPU_max_texture_size
).Due to this limitation, we cannot cache the entire
glyph
in a single 1D texture.To work around this problem, we use a 1DArray texture. So whenever the limit is reached on the first line, we move to the second line and so on.
This is what the
texel_fetch
function does.Can you try using a 2d texture instead of 1DArray?
Theoretically the result would be the same.
That works too! I tested on tag v2.93 with everything else unchanged from the original, including the
texel_fetch
function.I suppose
textureSize
just doesn't work withsampler1DArray
on my Chromebook.Here is an updated build:
https:*drive.google.com/file/d/1soWG84bfvP70cs8DVYroshS9FH75TCdu/view?usp=sharing
Changed status from 'Confirmed' to: 'Resolved'
I see this issue was resolved and closed today.
I'm not a coder and am unfamiliar with the process, but may I ask when the fix might be available for download in v2.92+?
Cheers
Long-term Support and 2.93+ versions
https://www.blender.org/download/lts/
Blender 3.0.0 - Alpha
June 08, 03:36:14 - master -
ef5a362a5b
- tar.xz - 149.62MBx64 Release
Works on my chromebook ;-)
Mine, too. Yay!
Though I note this message in Terminal after Blender started:
Read prefs: /home/sabai/.config/blender/3.0/config/userpref.blend
Warning: Could not find a matching GPU name. Things may not behave as expected.
Detected OpenGL configuration:
Vendor: Red Hat
Renderer: virgl
Thank you very much for fixing this issue, David and Germano. I'm super happy that Blender now works on my Chromebook as well.
3.0.0 Alpha loads successfully on Pixelbook.
Added subscriber: @g-easy
Thanks for working around this bug! The fix on the virgl side is https://gitlab.freedesktop.org/virgl/virglrenderer/-/merge_requests/770 and will be in ChromeOS M101.
Anyone running Debian 11 (bullseye) in Crostini: it ships Blender 2.83, which is affected by this bug, and should be fixed in M101 and later.