Repository navigation
Conversation
RaphvK
approved these changes
Nov 17, 2026
RaphvK
left a comment
Member
There was a problem hiding this comment.
This fixes using RViz on a remote (single-GPU) machine via TurboVNC for me, as well 👍
cgeller
marked this pull request as ready for review
November 17, 2026 10:08
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
RViz fails in remote setups such as VNC, because the compose template forces
__GLX_VENDOR_LIBRARY_NAME=nvidia(#10) and the remote X server does not support NVIDIA GLX.__GLX_VENDOR_LIBRARY_NAMEfrom the host, so the OpenGL vendor is auto-detected by defaultexport __GLX_VENDOR_LIBRARY_NAME=nvidiaTested on a single-GPU desktop (still renders on NVIDIA) and via TurboVNC (now works). @MikkelDLR, could you confirm that the export restores the previous behavior on your multi-GPU setup?