-
Notifications
You must be signed in to change notification settings - Fork 37
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
Use fallback x11 #183
Comments
I think that is a good idea. Right now Gnome software shows the slack flatpak as unsafe because of this. Users should be trained to not ignore safety issues for convenience, so I would prioritize this. |
Not so easy. I just tried that. Setting |
Huh, that is weird. On Fedora with wayland, just disabling the x11 socket worked for me It is possible to explicitly tell electron apps to use wayland with command line flags, using --enable-features=UseOzonePlatform --ozone-platform=wayland . It may be possible to have the .desktop file run a shell script that checks for available sockets |
This has worked for me for many months, for what it's worth - either using the wayland socket alone, or wayland plus fallback-x11. Using wayland plus x11 doesn't quite work, since Slack seems to prefer x11 in that case. |
We will move to a fallback-x11 configuration once Slack's electron version is modern enough to not have major bugs with the wayland implementation. |
Current regressions that block this as of Slack 4.41.96 (Electron 33) under GNOME 47:
|
On Fedora 39 Workstation (GNOME 45 on Wayland) with This is the command I used:
Just FYI for those who want to run Slack on Wayland |
@justin13888 FYI the startup script for Slack already has these flags available, you just need to enable the Wayland socket: Any time you start Slack afterwards will be using Wayland. |
This package seems to support wayland, could you update to the the more recent permission introduced in flatpak 1.0?
As far as I understand, this should favor wayland when that is available, which should be all the major distros at this point
https://github.com/flatpak/flatpak/blob/main/NEWS
The text was updated successfully, but these errors were encountered: