3 ms·

Well "Wayland no worky" for me, it breaks keyboard input in Firefox on Ubuntu, so I'd say a pretty basic use case. Not the time to switch for me, sorry.

linmob 3y ago
Which release? Ubuntu has had a bad habit of not setting the proper environment variables for Firefox in the past - for X (not setting MOZ_USE_XINPUT2=1) and wayland (MOZ_ENABLE_WAYLAND=1), massively degrading the user experience in Firefox, e.g., for touchscreen users. With Firefox 121 and forward, the latter variable does not need to be set anymore. To sum it up: Your subpar experience wasn't the fault of Wayland or Mozilla, your distribution is to blame for this (as making the combination of software shipped work well together for the user is the job a good distribution does). That said, even without setting the environment up correctly, I never had a keyboard input issue - so it could be snap... Canonical to blame, again - maybe. (Need I say I no longer use Ubuntu and will move my parents to a different distribution once I find the time?)
linmob 3y ago
Which release? Ubuntu has had a bad habit of not setting the proper environment variables for Firefox in the past - for X (not setting MOZ_USE_XINPUT2=1) and wayland (MOZ_ENABLE_WAYLAND=1), massively degrading the user experience in Firefox, e.g., for touchscreen users. With Firefox 121 and forward, the latter variable does not need to be set anymore. To sum it up: Your subpar experience wasn't the fault of Wayland or Mozilla, your distribution is to blame for this (as making the combination of software shipped work well together for the user is the job a good distribution does). That said, even without setting the environment up correctly, I never had a keyboard input issue - so it could be snap... Canonical to blame, again - maybe. (Need I say I no longer use Ubuntu, despite it being my main distro since 4.10. My parents are still on the LTS train, I will move them to a different distribution once I find the time.)

linmob 3y ago

Which release? Ubuntu has had a bad habit of not setting the proper environment variables for Firefox in the past - for X (not setting MOZ_USE_XINPUT2=1) and wayland (MOZ_ENABLE_WAYLAND=1), massively degrading the user experience in Firefox, e.g., for touchscreen users. With Firefox 121 and forward, the latter variable does not need to be set anymore. To sum it up: Your subpar experience wasn't the fault of Wayland or Mozilla, your distribution is to blame for this (as making the combination of software shipped work well together for the user is the job a good distribution does). That said, even without setting the environment up correctly, I never had a keyboard input issue - so it could be snap... Canonical to blame, again - maybe. (Need I say I no longer use Ubuntu and will move my parents to a different distribution once I find the time?)

linmob 3y ago

Which release? Ubuntu has had a bad habit of not setting the proper environment variables for Firefox in the past - for X (not setting MOZ_USE_XINPUT2=1) and wayland (MOZ_ENABLE_WAYLAND=1), massively degrading the user experience in Firefox, e.g., for touchscreen users. With Firefox 121 and forward, the latter variable does not need to be set anymore. To sum it up: Your subpar experience wasn't the fault of Wayland or Mozilla, your distribution is to blame for this (as making the combination of software shipped work well together for the user is the job a good distribution does). That said, even without setting the environment up correctly, I never had a keyboard input issue - so it could be snap... Canonical to blame, again - maybe. (Need I say I no longer use Ubuntu, despite it being my main distro since 4.10. My parents are still on the LTS train, I will move them to a different distribution once I find the time.)