Nvidia driver 550.90.07 needs access to /sys/module/nvidia* #6372

GreatBigWhiteWorld · 2024-06-07T11:19:46Z

Description

Steam fail to launch (it has been ok for a long time in the past).

Steps to Reproduce

Steps to reproduce the behavior
With 'ignore noroot' and 'ignore private-dev' in firejail.local already, I got X error:

Expected behavior

Launch normally as before.

Actual behavior

steam showing in running process without any window or system tray.

Behavior without a profile

What changed calling LC_ALL=C firejail --noprofile /path/to/program in a
terminal?

Nothing changes. I get the same error with '--noprofile' option.

Additional context

This issue is new. It has been running fine with firejail. It started to appear after an OS update and reboot.

Environment

opensusetumbleweed
firejail version 0.9.72

Checklist

The issues is caused by firejail (i.e. running the program by path (e.g. /usr/bin/vlc) "fixes" it).
I can reproduce the issue without custom modifications (e.g. globals.local).
The program has a profile. (If not, request one in https://github.com/netblue30/firejail/issues/1139)
The profile (and redirect profile if exists) hasn't already been fixed upstream.
[x ] I have performed a short search for similar issues (to avoid opening a duplicate).
- [x ] I'm aware of browser-allow-drm yes/browser-disable-u2f no in firejail.config to allow DRM/U2F in browsers.
I used --profile=PROFILENAME to set the right profile. (Only relevant for AppImages)

The text was updated successfully, but these errors were encountered:

kmk3 · 2024-06-11T10:53:20Z

06/07 19:00:32 Init: Installing breakpad exception handler for appid(steam)/version(1716584667)/tid(119)
SteamUpdateUI: An X Error occurred
X Error of failed request:  BadValue (integer parameter out of range for operation)

The error is rather vague, so it's hard to tell.

I'd try commenting lines in steam.profile until it works to narrow it down.

Also, I see that there are quite a few results when searching for this error on
the steam issue tracker:

https://github.com/search?q=repo%3AValveSoftware%2Fsteam-for-linux+SteamUpdateUI%3A+An+X+Error+occurred&type=issues

The following issue has the same exact error in the title:

Steam doesn't launch - SteamUpdateUI: An X Error occurred ValveSoftware/steam-for-linux#4909

Maybe the workarounds posted there could help.

orzogc · 2024-06-14T09:42:41Z

I had also encountered this error after upgrading the NVIDIA driver from 550.78 to 550.90.07 on Arch Linux KDE wayland desktop. I ran firejail with --noprofile option but the error was the same.

Parent pid 5245, child pid 5246
Child process initialized in 7.50 ms
steam.sh[4]: Running Steam on arch rolling 64-bit
steam.sh[4]: STEAM_RUNTIME is disabled by the user
steam.sh[4]: Can't find 'steam-runtime-check-requirements', continuing anyway
[2024-06-14 17:39:39] Startup - updater built May 24 2024 20:46:19
[2024-06-14 17:39:39] Startup - Steam Client launched with: '/home/orzogc/.local/share/Steam/ubuntu12_32/steam'
06/14 17:39:39 minidumps folder is set to /tmp/dumps
06/14 17:39:39 Init: Installing breakpad exception handler for appid(steam)/version(1716584667)/tid(86)
SteamUpdateUI: An X Error occurred
X Error of failed request:  BadValue (integer parameter out of range for operation)

This error is used to be fixed by installing the 32-bits NVIDIA driver, but I had installed lib32-nvidia-utils on Arch Linux.

kmk3 · 2024-06-14T10:56:20Z

I had also encountered this error after upgrading the NVIDIA driver from
550.78 to 550.90.07 on Arch Linux KDE wayland desktop. I ran firejail
with --noprofile option but the error was the same.

Does anything change with firejail --profile=noprofile /usr/bin/steam?

Does anything change with Xorg?

Parent pid 5245, child pid 5246
Child process initialized in 7.50 ms
steam.sh[4]: Running Steam on arch rolling 64-bit
steam.sh[4]: STEAM_RUNTIME is disabled by the user
steam.sh[4]: Can't find 'steam-runtime-check-requirements', continuing anyway
[2024-06-14 17:39:39] Startup - updater built May 24 2024 20:46:19
[2024-06-14 17:39:39] Startup - Steam Client launched with: '/home/orzogc/.local/share/Steam/ubuntu12_32/steam'
06/14 17:39:39 minidumps folder is set to /tmp/dumps
06/14 17:39:39 Init: Installing breakpad exception handler for appid(steam)/version(1716584667)/tid(86)
SteamUpdateUI: An X Error occurred
X Error of failed request:  BadValue (integer parameter out of range for operation)

This error is used to be fixed by installing the 32-bits NVIDIA driver

To clarify, do you mean that in the past the error could be fixed by installing
that driver but now it doesn't fix the error anymore?

but I had installed lib32-nvidia-utils on Arch Linux.

Is that the "32-bits NVIDIA driver" or something else?

Does installing that fix the error?

orzogc · 2024-06-14T11:59:31Z

Does anything change with firejail --profile=noprofile /usr/bin/steam?

Nothing changes. Output is here:

Parent pid 8379, child pid 8380
Child process initialized in 6.34 ms
steam.sh[4]: Running Steam on arch rolling 64-bit
steam.sh[4]: STEAM_RUNTIME is enabled automatically
libEGL warning: egl: failed to create dri2 screen
MESA: error: ZINK: vkCreateInstance failed (VK_ERROR_INCOMPATIBLE_DRIVER)
libEGL warning: egl: failed to create dri2 screen
libEGL warning: egl: failed to create dri2 screen
MESA: error: ZINK: vkCreateInstance failed (VK_ERROR_INCOMPATIBLE_DRIVER)
libEGL warning: egl: failed to create dri2 screen
setup.sh[221]: Forced use of runtime version for 32-bit libgtk-x11-2.0.so.0
setup.sh[221]: Found newer runtime version for 32-bit libGLU.so.1. Host: 1.3.1 Runtime: 1.3.8004
setup.sh[221]: Forced use of runtime version for 32-bit libcurl-gnutls.so.4
setup.sh[221]: Forced use of runtime version for 32-bit libcurl.so.4
setup.sh[221]: Forced use of runtime version for 32-bit libdbusmenu-glib.so.4
setup.sh[221]: Forced use of runtime version for 32-bit libdbusmenu-gtk.so.4
setup.sh[221]: Found newer runtime version for 64-bit libGLU.so.1. Host: 1.3.1 Runtime: 1.3.8004
setup.sh[221]: Forced use of runtime version for 64-bit libcurl-gnutls.so.4
setup.sh[221]: Forced use of runtime version for 64-bit libcurl.so.4
setup.sh[221]: Found newer runtime version for 64-bit libdbusmenu-glib.so.4. Host: 4.0.12 Runtime: 4.0.13
setup.sh[221]: Found newer runtime version for 64-bit libdbusmenu-gtk.so.4. Host: 4.0.12 Runtime: 4.0.13
steam.sh[4]: Steam client's requirements are satisfied
[2024-06-14 19:21:14] Startup - updater built May 24 2024 20:46:19
[2024-06-14 19:21:14] Startup - Steam Client launched with: '/home/orzogc/.local/share/Steam/ubuntu12_32/steam'
06/14 19:21:14 minidumps folder is set to /tmp/dumps
06/14 19:21:14 Init: Installing breakpad exception handler for appid(steam)/version(1716584667)/tid(1123)
SteamUpdateUI: An X Error occurred
X Error of failed request:  BadValue (integer parameter out of range for operation)

Does anything change with Xorg?

I will test it later.

To clarify, do you mean that in the past the error could be fixed by installing that driver but now it doesn't fix the error anymore?

People said they fixed this error by installing the 32-bit NVIDIA driver in ValveSoftware/steam-for-linux#4909.

Is that the "32-bits NVIDIA driver" or something else?

Does installing that fix the error?

lib32-nvidia-utils on Arch Linux contains the 32-bit NVIDIA driver. I had installed it before upgrading NVIDIA driver so installing it doesn't fix this error anymore.

krop · 2024-06-14T18:11:49Z

https://bbs.archlinux.org/viewtopic.php?id=296675 is probably related.

Even a simple firejail glxgears produces the same error (same thing with --noprofile but --profile=noprofile works)

I'm also using openSUSE Tumbleweed with NVidia driver 550.90.07

krop · 2024-06-14T18:56:37Z

https://bbs.archlinux.org/viewtopic.php?id=296675 is probably related.

Even a simple firejail glxgears produces the same error (same thing with --noprofile but --profile=noprofile works)

firejail --trace glxgears reported 5:glxgears:access /sys/module/nvidia/initstate:-1

Adding noblacklist /sys/module to the default profile helps

Adding the line to steam.profile also allows running it with firejail

Edit

For anyone finding this bug report, you can also be a bit more restrictive and only un-blacklist what the NVidia driver wants to access:

Create a ~/.config/firejail folder if it doesn't exist
Add:

noblacklist /sys/module/nvidia/initstate
noblacklist /sys/module/nvidia_drm/initstate
noblacklist /sys/module/nvidia_uvm/initstate
noblacklist /sys/module/nvidia_modeset/initstate

to ~/.config/firejail/globals.local

orzogc · 2024-06-14T19:27:55Z

I can confirm adding noblacklist /sys/module to profile fixes the error.

GreatBigWhiteWorld · 2024-06-15T03:49:46Z

I can confirm adding noblacklist /sys/module to profile fixes the error.

I'm having another kind of error now (popup window) after using noblacklist /sys/module in ~/.config/firejail/globals.local.

A popup window that says "Error: Couldn't setup Steam data. Please contact technical support" when in console:

Reading profile /home/johnDoe/.config/firejail/steam.profile
Parent pid 22806, child pid 22807
Warning: cannot find /var/run/utmp
Child process initialized in 5.42 ms
bin_steam.sh[4]: Setting up Steam content in /home/johnDoe/.local/share/Steam

I have the following in ~/.config/firejail/steam.profile

ignore private-dev
ignore noroot
...

Running steam directly has no problem.

glitsj16 · 2024-06-15T04:20:22Z

@GreatBigWhiteWorld

The current steam.profile in git changed the seccomp option compared to 0.9.72. You might want to give that a try.

firejail/etc/profile-m-z/steam.profile

Line 170 in 0fb4753

    
           seccomp !chroot,!mount,!name_to_handle_at,!pivot_root,!process_vm_readv,!ptrace,!umount2

GreatBigWhiteWorld · 2024-06-15T07:44:26Z

@GreatBigWhiteWorld

The current steam.profile in git changed the seccomp option compared to 0.9.72. You might want to give that a try.

firejail/etc/profile-m-z/steam.profile

Line 170 in 0fb4753

seccomp !chroot,!mount,!name_to_handle_at,!pivot_root,!process_vm_readv,!ptrace,!umount2

Tried 'ignore seccomp' and I got the same error of not able to setup steam data.

krop · 2024-06-15T07:44:35Z

Note: I edited my previous comment: both /sys/module/nvidia/initstate and /sys/module/nvidia_modeset/initstate need to be un-blacklisted for e.g the Steam of itch.io clients.

I ran more tests with other applications and added /sys/module/nvidia_uvm/initstate which is needed by e.g Blender. While I didn't find a user yet for /sys/module/nvidia_drm/initstate, I also added it to the snippet to add to $HOME/.config/firejail/globals.local.

GreatBigWhiteWorld · 2024-06-15T09:01:48Z

I can confirm adding noblacklist /sys/module to profile fixes the error.

I'm having another kind of error now (popup window) after using noblacklist /sys/module in ~/.config/firejail/globals.local.

A popup window that says "Error: Couldn't setup Steam data. Please contact technical support" when in console:
Reading profile /home/johnDoe/.config/firejail/steam.profile
Parent pid 22806, child pid 22807
Warning: cannot find /var/run/utmp
Child process initialized in 5.42 ms
bin_steam.sh[4]: Setting up Steam content in /home/johnDoe/.local/share/Steam
I have the following in ~/.config/firejail/steam.profile
ignore private-dev
ignore noroot
...
Running steam directly has no problem.

This might be an unrelated problem to this thread, since adding 'noblacklist /sys/module' to globals.profile fix 'firejail glxgear'.
But I don't know why the new issue emerges after the first one fixed.
firejail steam had worked for a long time before all of this.

glitsj16 · 2024-06-15T14:21:54Z

Update

On the arch linux forum thread someone confirmed they've got a working steam when using the below (cfr. what we do in the blender profile):

noblacklist /sys/module
whitelist /sys/module/nvidia*
read-only /sys/module/nvidia*

kmk3 · 2024-06-16T09:15:07Z

On the arch linux forum
thread someone
confirmed they've got a working steam when using the below (cfr. what we do
in the blender profile):
noblacklist /sys/module
whitelist /sys/module/nvidia*
read-only /sys/module/nvidia*

Good catch!

I found a way to allow the amd/nvidia modules by default in the code (as in the
above entries) if no3d is not used and it seems to work.

Though I'm not sure what exactly the files in /sys/module provide, so it might
be better to only do so if the proprietary driver is in use/installed.

For nvidia it seems that the presence of the proprietary driver can be detected
by checking whether /dev/nvidiactl exists.

Any idea about AMDGPU Pro?

If not, I think I'll just do it for nvidia for now.

Relates to #841 #1932.

Cc: @RDProjekt (from #1932)

glitsj16 · 2024-06-16T10:17:23Z

Any idea about AMDGPU Pro?

Alas, no. We can add that later like you suggested when we find out. I'll ask around on our IRC channel.

kmk3 · 2024-06-17T08:15:18Z

NVIDIA PRIME offload fails with nvidia driver 550.90.07 #6385

kmk3 · 2024-06-17T11:58:20Z

(Quoting the following comment for reference as its OpenGL error output is more
complete)

@michelesr on Jun 16:

I'm not sure why, but since last nvidia driver:

$ vkcube
Selected GPU 0: NVIDIA GeForce GTX 1050 Ti with Max-Q Design, type: DiscreteGpu

$ firejail --noprofile /bin/vkcube
Parent pid 13174, child pid 13175
Child process initialized in 6.22 ms
Selected GPU 0: Intel(R) UHD Graphics 630 (CFL GT2), type: IntegratedGpu

OpenGL apps work fine with prime-run without firejail but they crash with firejail --noprofile

$ firejail --noprofile prime-run /bin/glxdemo
Parent pid 14198, child pid 14199
Child process initialized in 6.04 ms
X Error of failed request:  BadValue (integer parameter out of range for operation)
  Major opcode of failed request:  150 (GLX)
  Minor opcode of failed request:  3 (X_GLXCreateContext)
  Value in failed request:  0x0
  Serial number of failed request:  22
  Current serial number in output stream:  23

Parent is shutting down, bye...

What could be causing this?

@GreatBigWhiteWorld

It has been reported in netblue30#6372 that after upgrading the nvidia proprietary driver from version 550.78 to 550.90.07, programs using hardware acceleration fail unless paths in `/sys/module/nvidia*` are accessible. Example: $ firejail --noprofile prime-run /bin/glxdemo [...] X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 150 (GLX) Minor opcode of failed request: 3 (X_GLXCreateContext) Value in failed request: 0x0 Serial number of failed request: 22 Current serial number in output stream: 23 [...] Meanwhile, the AMD proprietary driver (AMDGPU Pro) seems to depend on `/sys/module/amdgpu` for OpenCL (though it is unclear how to detect that driver). See commit 95c8e28 ("Allow accessing /sys/module directory", 2018-05-08) and commit 9dd581d ("Allow AMD GPU usage by Blender", 2018-05-08) from PR netblue30#1932. So whitelist `/sys/module/nvidia*` by default if the nvidia proprietary driver is detected and `no3d` is not used. Note: The driver check is copied from src/firejail/util.c (see netblue30#841). To keep the current behavior (that is, block all modules), add `blacklist /sys/module` to globals.local. Fixes netblue30#6372. Reported-by: @GreatBigWhiteWorld Reported-by: @orzogc Reported-by: @krop Reported-by: @michelesr Suggested-by: @glitsj16

@GreatBigWhiteWorld

It has been reported in netblue30#6372 that after upgrading the nvidia proprietary driver from version 550.78 to 550.90.07, programs using hardware acceleration fail unless paths in `/sys/module/nvidia*` are accessible. Example: $ firejail --noprofile prime-run /bin/glxdemo [...] X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 150 (GLX) Minor opcode of failed request: 3 (X_GLXCreateContext) Value in failed request: 0x0 Serial number of failed request: 22 Current serial number in output stream: 23 [...] Meanwhile, the AMD proprietary driver (AMDGPU Pro) seems to depend on `/sys/module/amdgpu` for OpenCL (though it is unclear how to detect that driver). See commit 95c8e28 ("Allow accessing /sys/module directory", 2018-05-08) and commit 9dd581d ("Allow AMD GPU usage by Blender", 2018-05-08) from PR netblue30#1932. So whitelist `/sys/module/nvidia*` by default if the nvidia proprietary driver is detected and `no3d` is not used. Note: The driver check is copied from src/firejail/util.c (see netblue30#841). To keep the current behavior (that is, block all modules), add `blacklist /sys/module` to globals.local. Fixes netblue30#6372. Reported-by: @GreatBigWhiteWorld Reported-by: @orzogc Reported-by: @krop Reported-by: @michelesr Suggested-by: @glitsj16 Tested-by: @flyxyz123

kmk3 · 2024-06-25T22:56:06Z

Fixed in #6387; thanks for all the reports and tests!

Relates to #6372 #6379 #6380 #6382 #6387 #6390 #6398.

kmk3 changed the title ~~Steam fails to launch with 'X error...'~~ Steam fails to launch with "SteamUpdateUI: An X Error occurred" Jun 11, 2024

kmk3 added the needinfo More information is needed from the issue author label Jun 11, 2024

kmk3 changed the title ~~Steam fails to launch with "SteamUpdateUI: An X Error occurred"~~ Steam fails to launch with "SteamUpdateUI: An X Error occurred" (nvidia) Jun 17, 2024

kmk3 removed the needinfo More information is needed from the issue author label Jun 17, 2024

kmk3 changed the title ~~Steam fails to launch with "SteamUpdateUI: An X Error occurred" (nvidia)~~ Nvidia driver 550.90.07 needs access to /sys/module/nvidia* Jun 17, 2024

kmk3 added the bug Something isn't working label Jun 17, 2024

kmk3 mentioned this issue Jun 17, 2024

modif: keep /sys/module/nvidia* if prop driver and no no3d #6387

Merged

kmk3 closed this as completed in #6387 Jun 25, 2024

kmk3 closed this as completed in af44e33 Jun 25, 2024

kmk3 added a commit that referenced this issue Jul 9, 2024

RELNOTES: add feature, modif and docs items

aed94a3

Relates to #6372 #6379 #6380 #6382 #6387 #6390 #6398.

github-project-automation bot added this to Release 0.9.74 Aug 28, 2024

github-project-automation bot moved this to Done (on RELNOTES) in Release 0.9.74 Aug 28, 2024

kmk3 added the graphics Issues related to GPU acceleration and drivers (mesa, nvidia, etc) label Sep 14, 2024

pjhfggij mentioned this issue Oct 18, 2024

Nvidia driver 560.35.03 cannot access gpu #6509

Closed

7 tasks

kmk3 mentioned this issue Dec 15, 2024

Vulkan applications don't work even with --noprofile (nvidia) #6566

Closed

5 tasks

kmk3 mentioned this issue Jan 28, 2025

zoom: program does not start (nvidia) #6634

Closed

7 tasks

rusty-snake marked this as a duplicate of #6634 Jan 28, 2025

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Nvidia driver 550.90.07 needs access to /sys/module/nvidia* #6372

Nvidia driver 550.90.07 needs access to /sys/module/nvidia* #6372

GreatBigWhiteWorld commented Jun 7, 2024

kmk3 commented Jun 11, 2024 •

edited

Loading

orzogc commented Jun 14, 2024 •

edited

Loading

kmk3 commented Jun 14, 2024 •

edited

Loading

orzogc commented Jun 14, 2024

krop commented Jun 14, 2024

krop commented Jun 14, 2024 •

edited

Loading

orzogc commented Jun 14, 2024

GreatBigWhiteWorld commented Jun 15, 2024

glitsj16 commented Jun 15, 2024

GreatBigWhiteWorld commented Jun 15, 2024

krop commented Jun 15, 2024

GreatBigWhiteWorld commented Jun 15, 2024

glitsj16 commented Jun 15, 2024 •

edited

Loading

kmk3 commented Jun 16, 2024

glitsj16 commented Jun 16, 2024

kmk3 commented Jun 17, 2024

kmk3 commented Jun 17, 2024

kmk3 commented Jun 25, 2024

Nvidia driver 550.90.07 needs access to /sys/module/nvidia* #6372

Nvidia driver 550.90.07 needs access to /sys/module/nvidia* #6372

Comments

GreatBigWhiteWorld commented Jun 7, 2024

Description

Steps to Reproduce

Expected behavior

Actual behavior

Behavior without a profile

Additional context

Environment

Checklist

kmk3 commented Jun 11, 2024 • edited Loading

orzogc commented Jun 14, 2024 • edited Loading

kmk3 commented Jun 14, 2024 • edited Loading

orzogc commented Jun 14, 2024

krop commented Jun 14, 2024

krop commented Jun 14, 2024 • edited Loading

orzogc commented Jun 14, 2024

GreatBigWhiteWorld commented Jun 15, 2024

glitsj16 commented Jun 15, 2024

GreatBigWhiteWorld commented Jun 15, 2024

krop commented Jun 15, 2024

GreatBigWhiteWorld commented Jun 15, 2024

glitsj16 commented Jun 15, 2024 • edited Loading

kmk3 commented Jun 16, 2024

glitsj16 commented Jun 16, 2024

kmk3 commented Jun 17, 2024

kmk3 commented Jun 17, 2024

kmk3 commented Jun 25, 2024

kmk3 commented Jun 11, 2024 •

edited

Loading

orzogc commented Jun 14, 2024 •

edited

Loading

kmk3 commented Jun 14, 2024 •

edited

Loading

krop commented Jun 14, 2024 •

edited

Loading

glitsj16 commented Jun 15, 2024 •

edited

Loading