Compressed Image Display not working with latest nvidia-drivers about studio HOT 10 CLOSED

Internal tracking ticket: FG-6472

from studio.

How did you install Foxglove – from the snap or deb? If it was the snap, please try installing from the deb directly.

from studio.

I installed using debian.

from studio.

The following issues seem related:

• ValveSoftware/steam-for-linux#9630
• https://forums.developer.nvidia.com/t/no-hardware-acceleration-in-google-chrome-with-535-x-drivers/269398
• https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-535/+bug/2026295

What do you see when visiting about:gpu in chrome?

What do you see when opening the developer tools in foxglove (ctrl+shift+i)? Any relevant errors in there?

from studio.

I have attached the output of about:gpu in the text file
about-gpu.txt

Also, floxglove is complaining about not finding sharers. See the attached log below
`main.js:5862 WebGL: INVALID_OPERATION: drawElements: no valid shader program in use
v1 @ main.js:5862
V6.renderBufferDirect @ main.js:5920
J9 @ main.js:5920
v9 @ main.js:5920
Nm @ main.js:5920
V6.render @ main.js:5920
#k @ 2890.js:345
animationFrame @ 2890.js:345
F @ main.js:6323
requestAnimationFrame (async)
(anonymous) @ main.js:6326
queueAnimationFrame @ 2890.js:345
(anonymous) @ main.js:2051
Promise.then (async)
setImage @ main.js:2051
setImage @ main.js:6423
#d @ main.js:2051
#p @ main.js:2051
(anonymous) @ main.js:2051
#c @ main.js:2051
handleImage @ main.js:2051
handleCompressedImage @ main.js:2051
#z @ 2890.js:345
#k @ 2890.js:345
animationFrame @ 2890.js:345
(anonymous) @ 2890.js:345
f4 @ main.js:1412
hc @ main.js:1412
Po @ main.js:1412
c3 @ main.js:1410
Ei @ main.js:1412
c4 @ main.js:1410
(anonymous) @ main.js:1410
(anonymous) @ main.js:6311
d @ main.js:6311
dispatch @ main.js:1630
listener @ main.js:1630
#R @ main.js:6407
await in #R (async)
processPlayerState @ main.js:6407
(anonymous) @ main.js:1605
(anonymous) @ main.js:1507
(anonymous) @ main.js:2168
(anonymous) @ main.js:2168
L @ main.js:2168
Promise.then (async)
T @ main.js:2168
(anonymous) @ main.js:2168
v @ main.js:2168
runExclusive @ main.js:2168
runExclusive @ main.js:2168
runExclusive @ main.js:1507
#s @ main.js:1605
(anonymous) @ main.js:1605
(anonymous) @ main.js:1633
g @ main.js:1507
(anonymous) @ main.js:1507
Promise.finally (async)
g @ main.js:1507
b @ main.js:1507
(anonymous) @ main.js:1633
f.emit @ main.js:1320
#t.onmessage @ main.js:1632
Ye.#e.onmessage @ main.js:1632
main.js:5888 THREE.WebGLProgram: Shader Error 0 - VALIDATE_STATUS false

Program Info Log: Program binary could not be loaded. Binary is not compatible with current driver/hardware combination. Driver build date Dec 28 2023. Please check build information of source that generated the binary.
Location of variable pc_fragColor conflicts with another variable.
A4 @ main.js:5888 `

from studio.

Also sounds like this error. #6706 (electron/electron#40450)

from studio.

Not sure. Is there any easy fix? Otherwise I guess I will have to revert the driver update.

Are you using electron for foxglove studio desktop app? So unless the latest electron is used during build, it's going to persist I guess.

from studio.

The title of electron/electron#40450 implies it is a problem with a cached shader, so you could try deleting app data and caches, reinstalling the app, etc. You could also try using Chrome and see if it helps. But there is unfortunately probably not much we can do on the Foxglove side to help resolve it if the root cause is upstream in Chrome/Electron.

from studio.

Okay.

from studio.

I'm going to close out this ticket because I'm not aware of anything we can do here other than trying the steps recommended above. If it continues to be a problem feel free to continue posting updates here and we can try to help.

from studio.