-
Notifications
You must be signed in to change notification settings - Fork 13
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
Adding a switch for Wayland #22
Comments
I came here from that same issue. Wayland works perfectly fine for me when running this command: flatpak run com.vscodium.codium --enable-features=UseOzonePlatform,WaylandWindowDecorations --ozone-platform=wayland, but it is annoying using the terminal every time and if you disable X11 in flatseal, even if you enable fallback X11, no window will pop up. It seems like the only work that needs to be done for Wayland is to have it come enabled by default (with Wayland window decorations). |
@larina3315 & @sr66139p I'm currently working to support wayland on a clean way |
Well @larina3315 & @sr66139p I found that the latest build of codium doesn't complain about the |
I forgot to mention this before, but the latest version of the VSCodium Flatpak works perfectly in my Wayland session since the last update, and I made sure everything is Flatseal was set to default. Title bars (both native and custom), cursors, and everything everything else works. Thanks for the good work @noonsleeper |
You are welcome! 😄 |
VSCodium do not work on my Fedora Silverblue Wayland, but X11 works fine. |
Continuing from flathub/com.vscodium.codium#295
I would like to discuss the details of implementing support for Wayland here.
The text was updated successfully, but these errors were encountered: