Closed Bug 1665817 Opened 4 years ago Closed 4 months ago

[Flatpak] Enable native Wayland

Categories

(Core :: Widget: Gtk, task)

80 Branch
Desktop
Linux
task

Tracking

()

RESOLVED DUPLICATE of bug 1870966

People

(Reporter: theevilskeleton, Unassigned)

References

(Blocks 1 open bug)

Details

Attachments

(1 file, 2 obsolete files)

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Firefox/78.0

Actual results:

When using Wayland, Firefox will open in an Xwayland window instead of a pure/native Wayland window. Other programs opened in an Xwayland window will still be able to see Firefox, thus still making it a security/privacy issue to Wayland users.

Expected results:

It should be opened in a native Wayland window.

I made a post about enabling native Wayland in Firefox Flatpak: https://www.reddit.com/r/LinuxCafe/duplicates/isdmmp/tip_use_firefox_flatpak_in_native_wayland_no/

Here's a merge request in the LibreWolf repository (fork of Firefox) about natively enabling Wayland: https://gitlab.com/librewolf-community/browser/linux/-/merge_requests/11/diffs

Basically, the only lines you have to add are:

 	        "--socket=wayland",
	        "--env=MOZ_ENABLE_WAYLAND=1",

(remove the comma in the second line if it's the last line.)

Bugbug thinks this bug should belong to this component, but please revert this change in case of error.

Component: Untriaged → Widget: Gtk
Product: Firefox → Core
Summary: [Flatpak] Add Wayland → [Flatpak] Enable native Wayland

I could create a merge request. I don't really mind

Status: UNCONFIRMED → NEW
Type: enhancement → task
Depends on: wayland-nightly
Ever confirmed: true
OS: Unspecified → Linux
Hardware: Unspecified → Desktop

Is there any progress on this? Seems like such an obvious change to make...

(In reply to ajtbecool from comment #3)

Is there any progress on this? Seems like such an obvious change to make...

Firefox is a FOSS project, so it relies on the community. If the change is obvious to you, then we would've appreciated it if you would submit a patch.

It seems like a bad idea to make this change in the firefox flatpak before it's done in the default build (hence the dependency on bug 1543600).

Attachment #9210720 - Attachment is obsolete: true

(In reply to Julien Cristau [:jcristau] from comment #6)

It seems like a bad idea to make this change in the firefox flatpak before it's done in the default build (hence the dependency on bug 1543600).

Sure. I'll just keep it opened until a member decides to merge it.

Attachment #9211986 - Attachment description: WIP: Bug 1665817 - Enable Wayland env in Flatpak → Bug 1665817 - Enable Wayland env in Flatpak
Attachment #9211995 - Attachment description: WIP: Bug 1665817 - Enable Wayland in Flatpak → Bug 1665817 - Enable Wayland in Flatpak
Attachment #9211986 - Attachment is obsolete: true

Probably, fallback-x11 instead of x11 for the socket option should be used then to not give unnecessary access to x11 on wayland capable systems?
For infos on option see:
https://docs.flatpak.org/en/latest/sandbox-permissions.html#standard-permissions
and
https://docs.flatpak.org/en/latest/flatpak-command-reference.html#flatpak-override
under option socket for override command

Blocks: wayland
Status: NEW → RESOLVED
Closed: 4 months ago
Duplicate of bug: 1870966
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: