The only flag I had to set was one for Firefox, and that has become enabled by default these days. XWayland solves all of the difficult mess as far as I can tell, including dealing with Electron applications.
I suppose the difficulty of migration depends on how complex your setup, but for most distros, switching to Wayland is no more difficult than selecting it in a dropdown on the login screen and installing a different screen recorder (because those are often written specifically for X.org or Wayland’s APIs, and rarely for both).
I had to set a ton more. Without the ozone flags my electron apps flicker and have this sync problem that appears to eat letters while I type them. Different electron apps use different configuration files, it’s a mess.
I wouldn’t consider my setup to be complex enough for the amount of trouble I had to make the system work under Wayland.
I’m using an Nvidia GPU, I’m sure things would be more streamlined if I had something else.
How strange, with how many of the programs I run I would’ve expected to have the same issues on my end as well. Blaming Nvidia is usually a solid bet, but I didn’t have any of these issues with Ubuntus’s Wayland support on my GTX1080, and Ubuntu tends to be a few years behind on package versions.
I’m unfamiliar with the ozone flags, a cursory Google search says it enables the (optional, for some reason) Wayland backend for Electron stuff, which people with fractional scaling seemingly need to do to get good rendering (because X11 doesn’t really do fractional scaling either so XWayland can’t compensate).
I wonder why Electron would default to X11 when started under a Wayland session.
The only flag I had to set was one for Firefox, and that has become enabled by default these days. XWayland solves all of the difficult mess as far as I can tell, including dealing with Electron applications.
I suppose the difficulty of migration depends on how complex your setup, but for most distros, switching to Wayland is no more difficult than selecting it in a dropdown on the login screen and installing a different screen recorder (because those are often written specifically for X.org or Wayland’s APIs, and rarely for both).
I had to set a ton more. Without the ozone flags my electron apps flicker and have this sync problem that appears to eat letters while I type them. Different electron apps use different configuration files, it’s a mess.
I wouldn’t consider my setup to be complex enough for the amount of trouble I had to make the system work under Wayland.
I’m using an Nvidia GPU, I’m sure things would be more streamlined if I had something else.
How strange, with how many of the programs I run I would’ve expected to have the same issues on my end as well. Blaming Nvidia is usually a solid bet, but I didn’t have any of these issues with Ubuntus’s Wayland support on my GTX1080, and Ubuntu tends to be a few years behind on package versions.
I’m unfamiliar with the ozone flags, a cursory Google search says it enables the (optional, for some reason) Wayland backend for Electron stuff, which people with fractional scaling seemingly need to do to get good rendering (because X11 doesn’t really do fractional scaling either so XWayland can’t compensate).
I wonder why Electron would default to X11 when started under a Wayland session.