[GH-ISSUE #879] Can't run any OpenGL apps using nvidia drivers #595

Closed
opened 2026-05-05 06:14:49 -06:00 by gitea-mirror · 10 comments
Owner

Originally created by @bog-dan-ro on GitHub (Oct 28, 2016).
Original GitHub issue: https://github.com/netblue30/firejail/issues/879

Hi,

I'm trying to use firejail (from debian sid packages) to run some opengl games (0ad, openarena, etc.) but none of them seems to work. Not even the humble glxgears ...
It doesn't crash, just the window is black.

Is this a know problem, or the debian package is broken?

Originally created by @bog-dan-ro on GitHub (Oct 28, 2016). Original GitHub issue: https://github.com/netblue30/firejail/issues/879 Hi, I'm trying to use firejail (from debian sid packages) to run some opengl games (0ad, openarena, etc.) but none of them seems to work. Not even the humble glxgears ... It doesn't crash, just the window is black. Is this a know problem, or the debian package is broken?
gitea-mirror 2026-05-05 06:14:49 -06:00
Author
Owner

@valoq commented on GitHub (Oct 28, 2016):

How do you start firejail?
Are you using any profiles, the default profiles or your own?
Are you using any additional firejail options like --x11 to start the applications?

Can you verify that the applications run normally without firejail?

<!-- gh-comment-id:256986170 --> @valoq commented on GitHub (Oct 28, 2016): How do you start firejail? Are you using any profiles, the default profiles or your own? Are you using any additional firejail options like --x11 to start the applications? Can you verify that the applications run normally without firejail?
Author
Owner

@netblue30 commented on GitHub (Oct 29, 2016):

What firejail version are you running? There have been some Nvidia fixes in 0.9.44.

Also try "firejail --noprofile 0ad". If this works, we'll need to fix the profile file.

<!-- gh-comment-id:257095396 --> @netblue30 commented on GitHub (Oct 29, 2016): What firejail version are you running? There have been some Nvidia fixes in 0.9.44. Also try "firejail --noprofile 0ad". If this works, we'll need to fix the profile file.
Author
Owner

@bog-dan-ro commented on GitHub (Nov 2, 2016):

@valoq

How do you start firejail?

firejail 0ad

Are you using any profiles, the default profiles or your own?

default profiles

Are you using any additional firejail options like --x11 to start the applications?

Nope

Can you verify that the applications run normally without firejail?

It runs perfectly!

@netblue30

What firejail version are you running? There have been some Nvidia fixes in 0.9.44.

0.9.44-1 from https://packages.debian.org/sid/firejail

Also try "firejail --noprofile 0ad". If this works, we'll need to fix the profile file.

I'll try it when I get home.

I tried it on my laptop (intel video card) and everything works ok !

<!-- gh-comment-id:257888922 --> @bog-dan-ro commented on GitHub (Nov 2, 2016): @valoq > How do you start firejail? `firejail 0ad` > Are you using any profiles, the default profiles or your own? default profiles > Are you using any additional firejail options like --x11 to start the applications? Nope > Can you verify that the applications run normally without firejail? It runs perfectly! @netblue30 > What firejail version are you running? There have been some Nvidia fixes in 0.9.44. 0.9.44-1 from https://packages.debian.org/sid/firejail > Also try "firejail --noprofile 0ad". If this works, we'll need to fix the profile file. I'll try it when I get home. I tried it on my laptop (intel video card) and everything works ok !
Author
Owner

@bog-dan-ro commented on GitHub (Nov 4, 2016):

@netblue30 firejail --noprofile any_open_gl_app works perfectly!
Let me know how can I help to fix the profile files.

<!-- gh-comment-id:258504193 --> @bog-dan-ro commented on GitHub (Nov 4, 2016): @netblue30 `firejail --noprofile any_open_gl_app` works perfectly! Let me know how can I help to fix the profile files.
Author
Owner

@netblue30 commented on GitHub (Nov 5, 2016):

OK, you need to find in the profile file the line or the lines that are creating the problem.

For example, you open in a text editor /etc/0ad.profile and start commenting the lines one by one (add a '#' in front of the line). Then, you run "firejail 0ad". In a few iterations you'll find out what line or lines are creating the problem.

Also take a look at this issue: https://github.com/netblue30/firejail/issues/631

<!-- gh-comment-id:258613007 --> @netblue30 commented on GitHub (Nov 5, 2016): OK, you need to find in the profile file the line or the lines that are creating the problem. For example, you open in a text editor /etc/0ad.profile and start commenting the lines one by one (add a '#' in front of the line). Then, you run "firejail 0ad". In a few iterations you'll find out what line or lines are creating the problem. Also take a look at this issue: https://github.com/netblue30/firejail/issues/631
Author
Owner

@bog-dan-ro commented on GitHub (Nov 6, 2016):

I found it, it's noroot option from default.profile

<!-- gh-comment-id:258692349 --> @bog-dan-ro commented on GitHub (Nov 6, 2016): I found it, it's `noroot` option from `default.profile`
Author
Owner

@bog-dan-ro commented on GitHub (Nov 6, 2016):

For 0ad there are a few more in 0ad.profile

#caps.drop all
#nonewprivs
#noroot
#protocol unix,inet,inet6
#seccomp
<!-- gh-comment-id:258692648 --> @bog-dan-ro commented on GitHub (Nov 6, 2016): For **0ad** there are a few more in **0ad.profile** ``` #caps.drop all #nonewprivs #noroot #protocol unix,inet,inet6 #seccomp ```
Author
Owner

@netblue30 commented on GitHub (Nov 6, 2016):

I think the driver uses some suid binary to start opengl, or maybe ptrace. Is this the opensource driver from Debian or some closed-source driver from Nvidia?

We have something similar with AMDGPU Pro drivers from AMD: https://firejail.wordpress.com/support/known-problems/#amdgpu - in this case they seem to be using ptrace for some reasons and they get killed by seccomp.

This is how you fix it: for all opengl programs you use, make a local copy of the profile file (example: /etc/firejail/0ad.profile) in your home directory in ~/.config/firejail/ (example: ~/.config/firejail/0ad.profile). Then. you edit the local copy and disable the lines. For programs without a specific profile file in /etc/firejail, copy /etc/firejail/default.profile (example: cp /etc/firejail/default.profile ~/.config/firejail/openarena.profile).

<!-- gh-comment-id:258700690 --> @netblue30 commented on GitHub (Nov 6, 2016): I think the driver uses some suid binary to start opengl, or maybe ptrace. Is this the opensource driver from Debian or some closed-source driver from Nvidia? We have something similar with AMDGPU Pro drivers from AMD: https://firejail.wordpress.com/support/known-problems/#amdgpu - in this case they seem to be using ptrace for some reasons and they get killed by seccomp. This is how you fix it: for all opengl programs you use, make a local copy of the profile file (example: /etc/firejail/0ad.profile) in your home directory in ~/.config/firejail/ (example: ~/.config/firejail/0ad.profile). Then. you edit the local copy and disable the lines. For programs without a specific profile file in /etc/firejail, copy /etc/firejail/default.profile (example: cp /etc/firejail/default.profile ~/.config/firejail/openarena.profile).
Author
Owner

@bog-dan-ro commented on GitHub (Nov 7, 2016):

I think the driver uses some suid binary to start opengl, or maybe ptrace. Is this the opensource driver from Debian or some closed-source driver from Nvidia?

I'm using NVidia proprietary drivers from debian packages https://packages.debian.org/sid/nvidia-driver :(

I "fixed" it by changing the files from /etc/firejail/ but ... Isn't better to trace the problem and contact nvidia and request them to fix their drivers?

<!-- gh-comment-id:258773695 --> @bog-dan-ro commented on GitHub (Nov 7, 2016): > I think the driver uses some suid binary to start opengl, or maybe ptrace. Is this the opensource driver from Debian or some closed-source driver from Nvidia? I'm using NVidia proprietary drivers from debian packages https://packages.debian.org/sid/nvidia-driver :( I "fixed" it by changing the files from /etc/firejail/ but ... Isn't better to trace the problem and contact nvidia and request them to fix their drivers?
Author
Owner

@netblue30 commented on GitHub (Nov 7, 2016):

Isn't better to trace the problem and contact nvidia and request them to fix their drivers?

Good luck with that!

<!-- gh-comment-id:258831677 --> @netblue30 commented on GitHub (Nov 7, 2016): > Isn't better to trace the problem and contact nvidia and request them to fix their drivers? Good luck with that!
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/firejail#595
No description provided.