-
Notifications
You must be signed in to change notification settings - Fork 56
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
Cannot Share Screen in Firefox Flatpak #261
Comments
Firefox screensharing works out-of-the-box with Flatpak. There's no need to do any extra configuration. Do you have this line in your sway config?
|
@SmiX Here's my setup in my sway/config:
And here is my flatpak overrides:
Edit: I moved the systemctl calls to pipewire/xdg services to a script called sway-dbus-portal-setup (they had originally been there) to avoid parallel execution. The script looks like this:
|
Sorry, screen sharing was working before i switched to flatpak but something changed and now it doesn't work when installed without flatpak. I'll debug the normal installation first. |
I was able to get the non-flatpak Firefox installation to work with screen sharing by using the following incantation regarding xdp/pipewire services (sway-dbus-portal-setup script):
However, I am still unable to get the flatpak installation to work with gum test returning
Any guidance on testing/debugging the ability to call the necessary portal from within the flatpak app would be helpful. When I attempt to share on gum test from within flatpak, no events/debug messages show up via |
Okay, while I said I had it working on the non-flatpak version, I guess I somehow broke it or had got it into a working state accidentally and thought my setup script was working. But yeah, overall, it's broken across flatpak and native installs and I'm not sure why. Here's my setup script:
Was able to go through the entirety of the checklist and the environment variables all check out. Some interesting messages from the the status calls:
Definitely riding the struggle bus on this one. I had my setup working for more than a year and I have no idea how I broke it. I remember there being issues with the service start order and maybe having to throw a random restart at the end but don't have access to my original script unfortunately (though it was very similar to the one above). |
You don't need to start/restart anything or override any firefox flatpak config. Just add the line I mentioned to ensure the env vars are set. |
@smlx Unfortunately, I can't even get it working in the non-flatpak version.
Here's my sway:
Here is sway-auth-agent:
Here is sway-dbus-portal-setup:
In my previous messages, I included some logs regarding wireguard / pipewire not being to see xdg-desktop-portal and xdg-desktop-portal reporting 'No skeleton'. Not sure if those are important. The wireplumber/pipewire issue related to not being able to find I am also running linux-hardened, but I've always been running that so I assume that's not the issue. |
Kind of crazy. I tried on my desktop, which uses the exact same config files my laptop and it worked fine for both flatpak and non-flatpak. I have no idea why as the configs are synced via git. Probably something to do with enabled/disabled systemd services. Edit: went through and the services are basically the same in terms of what's enabled. The other main difference is my desktop has Xwayland installed but my laptop does not. However, both systems have firefox running under wayland anyways. |
Okay, so my desktop, that works, has the following output for the xdg-desktop-portal-wlr service:
While my laptop, that doesn't work, has no such output. The only message is |
Okay, installed |
I am running arch linux + sway with firefox under a flatpak. When navigating to the Mozilla gum test and trying to share my screen, I receive the following:
I have included the following environment variables via Flatseal:
I have included the following
Talks
for thesession
via Flatseal:These
Talks
for thesession
were included by default:I have gone through the checklist and get stuck at
This returns
wayland-1
on the host but of course nothing within the flatpak application environment. The following wayland specific environment variables are set inside the flatpak app:Is Firefox screensharing not expected to work via Flatpak? I also have xdg-desktop-portal-gtk running as well but from my understanding this should cause issues.
The text was updated successfully, but these errors were encountered: