Chrome and Firefox WebGL not working on Autodesk Rocky Linux 9.7 (DKU 21.0.1 / NVIDIA 580)

Flame Hardware Questions
, , , ,
1

Hi everyone,

I’m running Autodesk Flame 2027.1 on the official Autodesk Rocky Linux 9.7 image with DKU 21.0.1.

System

  • Autodesk Flame 2027.1
  • Rocky Linux 9.7 (official Autodesk image)
  • DKU 21.0.1
  • NVIDIA Driver 580.159.04 (installed by DKU)
  • NVIDIA RTX 4080
  • X11 session

OpenGL itself appears to work correctly.

glxinfo -B reports:

  • OpenGL vendor: NVIDIA Corporation
  • Renderer: NVIDIA GeForce RTX 4080
  • OpenGL 4.6
  • Direct rendering: Yes

Flame itself runs normally with no graphics issues.

However, WebGL is unavailable in both Google Chrome and Firefox.

I also noticed that the X server is running in a 30-bit (10 bpc) configuration:



depth of root window: 30 planes
DefaultDepth 30

This comes from the Autodesk-provided xorg.conf, so I would prefer not to modify it since it is the recommended and supported configuration for Flame.

The NVIDIA driver itself appears healthy, but browsers do not expose WebGL.

Why I need WebGL

This isn’t for gaming or browser benchmarks. I occasionally use browser-based AI tools (motion capture, pose estimation, and other WebGL/WebGPU-powered applications) as part of my VFX workflow. Everything else runs on this Linux workstation, so I’d prefer not to reboot into Windows just to use those web-based tools if there is a supported solution.

Has anyone running an official Flame Linux workstation experienced the same issue?

I’m mainly trying to determine:

  • Is WebGL unsupported when using the standard Autodesk 30-bit X configuration?
  • Has anyone managed to get Chrome or Firefox WebGL working without modifying the Autodesk xorg.conf?
  • Is this simply an expected limitation of the Flame Linux environment?
  • Has anyone tested whether DKU 21.1.0 changes this behavior?

For now I’m considering running browser-based AI tools from a separate Windows SSD, but I’d like to know whether anyone has already found a clean solution.

Thanks!

2

Additional troubleshooting already performed

I also tested launching Chrome from the terminal using:



__EGL_VENDOR_LIBRARY_FILENAMES=/usr/share/glvnd/egl_vendor.d/10_nvidia.json \
google-chrome \
  --ignore-gpu-blocklist \
  --use-gl=angle \
  --use-angle=gl \
  --ozone-platform=x11 \
  --disable-software-rasterizer

Unfortunately, WebGL still remains unavailable.

3

I can test it on my official config. What’s a good command to verify?

And I’m running ComfyUI on this same system without issues. So may be driver/GPU related.

4

I am running with DKU_21.1.0. Looking at version history, difference between DKU_21.0.1 and DKU_21.1 does not touch graphics. It’s just other drivers.

Here’s what I get from glxinfo:

OpenGL vendor string: NVIDIA Corporation
direct rendering: Yes
OpenGL version string: 4.6.0 NVIDIA 580.159.04

Checking in Firefox / Troubleshooting info it shows:

WebGL1 Driver Renderer: NVIDIA Corporation

Going to webglreport.com I get:

✓ This browser supports WebGL 1
✓ This browser supports WebGL 2

And all the renderer and other information that you’d suspect.

My suspicion is that it has something to do with the RTX 4080 config, which means you’re a bit on your own from ADSK’s perspective.

5

Hi @allklier,

Thank you for taking the time to test it.

That’s actually very useful information.

It confirms that WebGL does work on an official Flame workstation, so this is apparently not an Autodesk/DKU limitation.

On my system, Firefox reports:



WebGL creation failed:
AllowWebglOutOfProcessNativeGl:false restricts context creation on this system.

FEATURE_FAILURE_WEBGL_EXHAUSTED_DRIVERS

The GPU is still detected correctly:

  • RTX 4080
  • NVIDIA 580.159.04
  • OpenGL 4.6
  • Direct Rendering = Yes

Flame itself runs perfectly.

Mixamo reports that WebGL is unavailable, Meshy fails during initialization, and other browser-based 3D applications also fail.

So it looks like the browser cannot create a WebGL context even though OpenGL itself is functional.

I’ll continue investigating what is different on this workstation compared to yours.

Thanks again for confirming that it works on the standard Autodesk configuration.

6

I think you have enough error messages that a Claude/ChatGPT session will solve this in 10min.

One area that may matter is how your browser was installed, and if the process is sandboxed. But there may be other causes too.