Skip to content

bitwarden: MESA: error: Failed to query drm device (intel/no3d) #6464

Closed Answered by rusty-snake
hellodword asked this question in Q&A
Discussion options

You must be logged in to vote

I would like to understand how no3d works

blacklist /dev/dri (intel, amd, nouveau?) and nvidia stuff

what attack surface it mitigates.

Access to hardware accelerated rendering/decoding (GPU). Otherwise software rendering/decoding (CPU) should be used.

Additionally, how can I optimize and minimize the firejail profile instead of simply ignoring no3d?

Not really if you're on a nvidia-free systemd system. Then it's just allow/deny /dev/dri. If you want to fine-tune things there, you need to create a virtual GPU and pipe to/from it.

Replies: 3 comments 3 replies

Comment options

You must be logged in to vote
1 reply
@hellodword
Comment options

Answer selected by hellodword
Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
2 replies
@rusty-snake
Comment options

@kmille
Comment options

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
duplicate This issue or pull request already exists notourbug The issue is valid, but it isn't directly caused by (or cannot be fixed by) firejail graphics Issues related to GPU acceleration and drivers (mesa, nvidia, etc)
4 participants