-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't load the overlay over flatpak Steam #5951
Comments
@davidebeatrici any ideas? |
Could you pass the |
I always forget, sorry. I see many |
The usual problem: "sandbox" containers generally allow the bare minimum required in order for the application to work. In this case the overlay library cannot access the socket that is created by Mumble, see https://docs.flatpak.org/en/latest/sandbox-permissions.html. |
Do you know any way to punch a whole in the sandbox to allow system libraries to access a flatpak application? currently steam has the following socket permissions:
|
|
That improved the logs, yes! But it is still not completely fixed: mumble-overlay-flatpak.log I see a couple of |
As there has been no activity on this issue for a couple of days, we assume that your issue has been fixed in the meantime. If no further activity happens, this issue will be closed within 3 days. |
it is not fixed! |
As this is a flatpak-specific issue, it should be reported to https://github.com/flathub/info.mumble.Mumble/issues |
well this is about using native Mumble with flatpak'd Steam. It should not be reported to flatpak Mumble. But I guess that if atm @davidebeatrici can't figure it out from the log file, no one else can. In that case this issue remains unsolved |
Then I misunderstood - but it remains a flatpak issue as it does not appear in unsandboxed environment. |
I am trying to investigate on my own, then. |
If it is not built when using |
Tests that don't have their own subdirectory have never been enabled. I personally never ran them. |
Okay, me neither 🤷 |
I discovered that On the plus side: I managed to build |
also: flatpak steam must be run after mumble. Don't know why: I thought it was a matter of preloading the overlay library when running the game... |
Great to hear you got it working 👍 |
Thanks! However, do you have any idea why Mumble must be running before flatpak steam is launched? It otherwise cannot connect (error: regarding Mumble having to be launched before flatpak Steam: If I go into flatpak's bash ( Mumble after flatpak Steam. Only read permissions. Date/time is wrong.
[📦 com.valvesoftware.Steam ~]$ ls -l /run/user/1000/MumbleOverlayPipe
-r--r--r-- 1 carlo carlo 0 13 nov 10.24 /run/user/1000/MumbleOverlayPipe
Mumble after flatpak Steam. Works as intended. Full permissions. Date/time is correct.
[📦 com.valvesoftware.Steam ~]$ ls -l /run/user/1000/MumbleOverlayPipe
srwxrwxrwx 1 carlo carlo 0 13 nov 12.00 /run/user/1000/MumbleOverlayPipe
❯ ls -l /run/user/1000/MumbleOverlayPipe
srwxrwxrwx 1 carlo carlo 0 13 nov 12.00 /run/user/1000/MumbleOverlayPipe
Mumble restarted with flapak Steam running. Doesn't work. Full permissions.The number of hard links of the socket changes to
[📦 com.valvesoftware.Steam ~]$ ls -l /run/user/1000/MumbleOverlayPipe
srwxrwxrwx 0 carlo carlo 0 13 nov 12.00 /run/user/1000/MumbleOverlayPipe
❯ ls -l /run/user/1000/MumbleOverlayPipe
srwxrwxrwx 1 carlo carlo 0 13 nov 12.10 /run/user/1000/MumbleOverlayPipe Discordon a similar note Discord, which also communicates with Steam through a local socket, doesn't have this problem. They create links to sockets that do not (yet) exist if Discord isn't running: [📦 com.valvesoftware.Steam ~]$ ls -l /run/user/1000/
totale 0
-r--r--r-- 1 carlo carlo 0 13 nov 10.24 MumbleOverlayPipe
lrwxrwxrwx 1 carlo carlo 40 13 nov 10.24 discord-ipc-0 -> app/com.discordapp.Discord/discord-ipc-0
lrwxrwxrwx 1 carlo carlo 40 13 nov 10.24 discord-ipc-1 -> app/com.discordapp.Discord/discord-ipc-1
lrwxrwxrwx 1 carlo carlo 40 13 nov 10.24 discord-ipc-2 -> app/com.discordapp.Discord/discord-ipc-2
lrwxrwxrwx 1 carlo carlo 40 13 nov 10.24 discord-ipc-3 -> app/com.discordapp.Discord/discord-ipc-3
lrwxrwxrwx 1 carlo carlo 40 13 nov 10.24 discord-ipc-4 -> app/com.discordapp.Discord/discord-ipc-4
lrwxrwxrwx 1 carlo carlo 40 13 nov 10.24 discord-ipc-5 -> app/com.discordapp.Discord/discord-ipc-5
lrwxrwxrwx 1 carlo carlo 40 13 nov 10.24 discord-ipc-6 -> app/com.discordapp.Discord/discord-ipc-6
lrwxrwxrwx 1 carlo carlo 40 13 nov 10.24 discord-ipc-7 -> app/com.discordapp.Discord/discord-ipc-7
lrwxrwxrwx 1 carlo carlo 40 13 nov 10.24 discord-ipc-8 -> app/com.discordapp.Discord/discord-ipc-8
lrwxrwxrwx 1 carlo carlo 40 13 nov 10.24 discord-ipc-9 -> app/com.discordapp.Discord/discord-ipc-9
...
P.S. the following settings are set:
|
flathub/com.valvesoftware.Steam#273 is relevant. I'll try to make flatpak Steam maintainers aware of it. If they propose to do something similar to what they did to Discord, I'll come back to this issue |
I have no idea about any of this, unfortunately 🤷 |
I managed to make it work regardless if Mumble was running before Steam or not. |
Can we also change default runtime path, if (can we re-open this issue, btw?) |
Moving MumbleSocket and MumbleOverlayPipe to a dedicated subdirectory keeps the runtime directory clean and allows flatpak applications to use the overlay by giving access only to Mumble's subdirectory. It also moves the default directory to /run/user/$UID/mumble/ when $XDG_RUNTIME_DIR is not set. Fixes mumble-voip#5951
Moving MumbleSocket and MumbleOverlayPipe to a dedicated subdirectory keeps the runtime directory clean and allows flatpak applications to use the overlay by giving access only to Mumble's subdirectory. It also moves the default directory to /run/user/$UID/mumble/ when $XDG_RUNTIME_DIR is not set. Fixes mumble-voip#5951
Moving MumbleSocket and MumbleOverlayPipe to a dedicated subdirectory keeps the runtime directory clean and allows flatpak applications to use the overlay by giving access only to Mumble's subdirectory. It also moves the default directory to /run/user/$UID/mumble/ when $XDG_RUNTIME_DIR is not set. Fixes mumble-voip#5951
Moving MumbleSocket and MumbleOverlayPipe to a dedicated subdirectory keeps the runtime directory clean and allows flatpak applications to use the overlay by giving access only to Mumble's subdirectory. It also moves the default directory to /run/user/$UID/mumble/ when $XDG_RUNTIME_DIR is not set. Fixes mumble-voip#5951
Moving MumbleSocket and MumbleOverlayPipe to a dedicated subdirectory keeps the runtime directory clean and allows flatpak applications to use the overlay by giving access only to Mumble's subdirectory. It also moves the default directory to /run/user/$UID/mumble/ when $XDG_RUNTIME_DIR is not set. Fixes mumble-voip#5951
Moving MumbleSocket and MumbleOverlayPipe to a dedicated subdirectory keeps the runtime directory clean and allows flatpak applications to use the overlay by giving access only to Mumble's subdirectory. It also moves the default directory to /run/user/$UID/mumble/ when $XDG_RUNTIME_DIR is not set. Fixes mumble-voip#5951
Moving MumbleSocket and MumbleOverlayPipe to a dedicated subdirectory keeps the runtime directory clean and allows flatpak applications to use the overlay by giving access only to Mumble's subdirectory. It also moves the default directory to /run/user/$UID/mumble/ when $XDG_RUNTIME_DIR is not set. Fixes mumble-voip#5951
Moving MumbleSocket and MumbleOverlayPipe to a dedicated subdirectory keeps the runtime directory clean and allows flatpak applications to use the overlay by giving access only to Mumble's subdirectory. It also moves the default directory to /run/user/$UID/mumble/ when $XDG_RUNTIME_DIR is not set. Fixes mumble-voip#5951
Moving MumbleSocket and MumbleOverlayPipe to a dedicated subdirectory keeps the runtime directory clean and allows flatpak applications to use the overlay by giving access only to Mumble's subdirectory. It also moves the default directory to /run/user/$UID/mumble/ when $XDG_RUNTIME_DIR is not set. Fixes mumble-voip#5951
Moving MumbleSocket and MumbleOverlayPipe to a dedicated subdirectory keeps the runtime directory clean and allows flatpak applications to use the overlay by giving access only to Mumble's subdirectory. It also moves the default directory to /run/user/$UID/mumble/ when $XDG_RUNTIME_DIR is not set. Fixes mumble-voip#5951
Moving MumbleSocket and MumbleOverlayPipe to a dedicated subdirectory keeps the runtime directory clean and allows flatpak applications to use the overlay by giving access only to Mumble's subdirectory. It also moves the default directory to /run/user/$UID/mumble/ when $XDG_RUNTIME_DIR is not set. Fixes mumble-voip#5951
Moving MumbleSocket and MumbleOverlayPipe to a dedicated subdirectory keeps the runtime directory clean and allows flatpak applications to use the overlay by giving access only to Mumble's subdirectory. It also moves the default directory to /run/user/$UID/mumble/ when $XDG_RUNTIME_DIR is not set. Fixes mumble-voip#5951
Moving MumbleSocket and MumbleOverlayPipe to a dedicated subdirectory keeps the runtime directory clean and allows flatpak applications to use the overlay by giving access only to Mumble's subdirectory. It also moves the default directory to /run/user/$UID/mumble/ when $XDG_RUNTIME_DIR is not set. Fixes mumble-voip#5951
The issue
Flatpak does not allow to punch a hole in the sandbox for some directories such as
/lib
,/lib32
,/usr
. I tried to copy the required libraries in Steam flatpak's directory in order to load the overlay:I then proceeded by setting the game launch options to:
LD_PRELOAD=/home/user/.local/share/Steam/linux32/libmumbleoverlay.x86.so:/home/user/.local/share/Steam/linux32/libGL.so %command%
However, the game (TF2) still does not show the overlay if launched through flatpak Steam.
Full flatpak log [does not work]
It works as intended if I launch it from shell with the following commands:
Full shell log [works as intended]
Any idea of how I can set the flatpak correctly in order to be able to access the right (system) libraries so that I can have the overlay?
Mumble version
1.4.0 + #5949
Mumble component
Client
OS
Linux
Additional information
Twin flatapk Steam issue: 997
The text was updated successfully, but these errors were encountered: