search

Facepunch / garrysmod-issues

Garry's Mod issue tracker
147 stars 56 forks source link

Menu not appearing when using x86_64 branch on Flatpak #5371

Open kindacozi opened 1 year ago

kindacozi commented 1 year ago

Details

Loading the game with the x86_64 branch when using flatpak causes no menu to appear, with No support for unprivileged usernamespaces. Loading Stub instead of Chromium... showing up in the console

Branch is [x86_64] version command output

Exe version 2022.06.08 (garrysmod)
Exe build: 14:17:37 May 31 2022 (8606) (4000)
GMod version 2022.07.13, branch: x86-64, multicore: 1
Linux 64bit

OS is Fedora Silverblue 37, which is why I'd prefer to use flatpak if possible The issue happens regardless of if I've applied the GModCEFCodecFix or not, and only happens when trying to run on the x86_64/Chromium branches

It's the same as this issue here, but I haven't found an easy way to go in and add support for unprivileged namespaces into the flatpak

Technically, the gmod-lua-menu does give a menu but it's not fully featured, plus the underlying issue with chromium is still there, breaking addons like the media player addon

Steps to reproduce

ghost commented 1 year ago

A quick & dirty fix to this issue would be the ability to disable Chromium's process sandbox, since one of the ways it sandboxes itself is through unprivileged user namespaces (with a fall-back method based on SUID, which is useless here). Unless Garry's Mod already provides that functionality, something akin to Steam's -no-cef-sandbox parameter would work at the cost of security and at the user's discretion.

sammypanda commented 1 year ago

https://github.com/flatpak/flatpak/pull/3240

TheAnnoyingFruit commented 1 year ago

flatpak/flatpak#3240

This stuff has been merged does this just mean that they need to implement this in the steam flatpak?

ihatesoftwaresomuch commented 1 year ago

I'm having the same issue in gmod x86_64 on steam installed through flatpak. This has happened on OpenSUSE and Kubuntu.

santiagocezar commented 11 months ago

As a workaround you can use zypak, which electron apps use to work inside Flatpak, and it works with CEF too!

Then add ~/zypak/zypak-wrapper.sh %command% to gmod launch parameters and (hopefully) that's it!

MisterSheeple commented 11 months ago

As a workaround you can use zypak, which electron apps use to work inside Flatpak, and it works with CEF too!

* clone the zypak repo to `~/.var/app/com.valvesoftware.Steam/zypak`

* run `flatpak run -d --command=sh com.valvesoftware.Steam` to get inside the Steam sandbox with build tools enabled

* cd into the zypak repo and build it with `./configure && make`

* i think that's all?

Then add ~/zypak/zypak-wrapper.sh %command% to gmod launch parameters and (hopefully) that's it!

have you tested this? it doesn't work for me

MisterSheeple commented 11 months ago

I'm starting to think the issue might be on the end of the Steam Flatpak devs. I didn't see an issue there, so I've gone ahead and made one: https://github.com/flathub/com.valvesoftware.Steam/issues/1214

santiagocezar commented 11 months ago

i have no idea how I didn't notice, but the game was running with proton, i'm so sorry.

though i'm still looking into it, i think zypak is still the way to go