[BUG] - when start a game it said "Steam now requires user namespaces to be enabled."

[paras-zomby]

Describe the bug

When I start Risk of Rain 2 using r2modman, it popped up and said "Steam now requires user namespaces to be enabled." I follow the instructions on "https://github.com/flatpak/flatpak/wiki/User-namespace-requirements" and checked that my bwrap and sysctl's config all work fine.

Additionally, when I start r2modman it told that my GPU process isn't usable and exit, so I start r2modman with "--no-sandbox" param.

I want to know how to fix it, thank u.

To Reproduce

Open the r2modman, select Risk of Rain 2, click "Start modded" or "Start vanilla".

Screenshots

Additional context

My environment is Ubuntu 24.04, using Proton to play RoR2.

[flackr]

I see the same issue with Lethal Company

[flackr]

FYI I found that you can work around this issue by going to Help > Launching the game from outside the mod manager where it will give you the command-line arguments you can add to the steam launch options which will look like this:

--doorstop-enable true --doorstop-target "Z:/home/$USER/.config/r2modmanPlus-local/LethalCompany/profiles/Default/BepInEx/core/BepInEx.Preloader.dll" --r2profile "Default"

Add these to the launch options of the game and you can manage / update the mods from r2modman and launch from steam directly.

[paras-zomby]

FYI I found that you can work around this issue by going to Help > Launching the game from outside the mod manager where it will give you the command-line arguments you can add to the steam launch options which will look like this:

--doorstop-enable true --doorstop-target "Z:/home/$USER/.config/r2modmanPlus-local/LethalCompany/profiles/Default/BepInEx/core/BepInEx.Preloader.dll" --r2profile "Default"

Add these to the launch options of the game and you can manage / update the mods from r2modman and launch from steam directly.

Wow, thks a lot!

[micproietti]

FYI I found that you can work around this issue by going to Help > Launching the game from outside the mod manager where it will give you the command-line arguments you can add to the steam launch options which will look like this:

--doorstop-enable true --doorstop-target "Z:/home/$USER/.config/r2modmanPlus-local/LethalCompany/profiles/Default/BepInEx/core/BepInEx.Preloader.dll" --r2profile "Default"

Add these to the launch options of the game and you can manage / update the mods from r2modman and launch from steam directly.

Hi, im facing the same issue. Im trying to fix it as you said, but even if i set the launch options it gives me the same problem

how can i solve it?

[flackr]

After setting those launch arguments, you run the game normally from steam (i.e. the green "Play" button). In your screenshot it looks like you may have been using the "Start modded" button in r2modman.

[micproietti]

After setting those launch arguments, you run the game normally from steam (i.e. the green "Play" button). In your screenshot it looks like you may have been using the "Start modded" button in r2modman.

I tried to start it from steam as well, but it launches on default mode, not modded

[paras-zomby]

After setting those launch arguments, you run the game normally from steam (i.e. the green "Play" button). In your screenshot it looks like you may have been using the "Start modded" button in r2modman.

I tried to start it from steam as well, but it launches on default mode, not modded

@flackr means that you should copy this cmd options and go to steam->"game settings"->"launch options" and add it to custom start parameters. if you just click "start game" on steam without doing this, it will be not modded.

cmd options looks like:

--doorstop-enable true --doorstop-target "Z:/home/$USER/.config/r2modmanPlus-local/LethalCompany/profiles/Default/BepInEx/core/BepInEx.Preloader.dll" --r2profile "Default"

[olekw]

FWIW, the workarounds do not work on any of the 4 Ubuntu 24.04 computers in my house. I'm messing around with Limo in the meantime.

Based on reading an excellent user namespace primer and perusing the Release Notes for Ubuntu 24.04, it sounds like the proper solution for this issue in r2modman is for it to have an AppArmor profile. Hopefully the info I've found will help someone in that effort.

[skiman6010]

Not to be a big proponent of completely disabling security features, but you can also just run this command:

sudo sysctl -w kernel.apparmor_restrict_unprivileged_userns=0

To revert the Ubuntu 24.04 changes and run games through r2modman again. This will reset on reboot and probably best practice to enable it again after by changing the 0 to a 1. I'm not smart enough to write an AppArmor profile so I've been doing it this way. I wouldn't recommend it though since it disables these restrictions systemwide, not just for appimages.

[lucasdaweb95]

i'd like to note that this issue also seems to be in the deb file

[Aravisian]

I had this same issue. However, when I looked - the compatibility tab was set to Linux Runtime Scout 1.0 instead of G.E. proton, Proton Experimental or the other later proton versions. I switched to Proton Experimental, then G.E. Proton and then Proton 10; each worked and launched without issue - so it seems that Linux Runtime Scout is what is wrapping and containerizing the title (In my case it was Valheim). EDIT: I may have spoken too soon. Success doing this is wildly intermittent and only @skiman6010 's suggestion above as a temporary test seems to consistently overcome the issue. I suspect I experienced a fluke.