Enable --socket=wayland

[kaimast]

Since Signal 5.1 there is experimental support for Wayland (see signalapp/Signal-Desktop#3411).

Can we change the permissions of the flatpak to allow connecting to the Wayland server?

[hfiguiere]

You can try it yourself, but if this is experimental it's probably not a wise idea to enable it for all.

[kaimast]

You still need to enable ozone in the command line. This would just make it a little easier to do so.

[bermeitinger-b]

Does this have any influence into non-wayland sessions?

[Arxcis]

You can try it yourself, but if this is experimental it's probably not a wise idea to enable it for all.

I agree. I think having both --socket=wayland and --socket=x11 enabled at the same time would be confusing, because it is not obvious to a regular user, which one of the sockets Signal is actually using by default, or if it uses both.

As long as wayland is not default, I think we should expect those who want to experiment, to run the override commands manually:

flatpak override --user --socket=wayland org.signal.Signal
flatpak override --user --nosocket=x11   org.signal.Signal

...or use the toggle buttons in Flatseal:

...which would store the overrides in ~/.local/share/flatpak/overrides/org.signal.Signal:

$ cat ~/.local/share/flatpak/overrides/org.signal.Signal 
[Context]
sockets=!x11;wayland;

Once wayland is the default, the best practice would be to set --socket=wayland and --socket=fallback-x11 in https://github.com/flathub/org.signal.Signal/blob/master/org.signal.Signal.json.

[der-eismann]

Is there any progress on this? Just enabling the socket shouldn't have any effect because you still need to set additional flags to run signal on Wayland.