Does this mean I can stop setting MOZ_ENABLE_WAYLAND?
Or is it just enabling the compilation of Wayland sections (which I thought happened a while ago?)When it reaches stable (or the release you use, if you go the Beta or Nightly route), yeah you’ll be able to do so.
I want everyone to move over to Wayland too.
I use my Linux PC for gaming. Last time I tried Steam/Nvidia with Wayland I could only get one game to launch. So hopefully those 2 will work on making Wayland happen for us.
NVIDIA has been notoriously problematic with Wayland from what I heard. When I bought my current rig I made sure AMD was powering the graphics.
Nvidia has included a couple of Wayland fixes in at least their 3 most recent driver updates, so hopefully they are taking this seriously and are committed to getting issues on their end fixed.
I haven’t used Wayland with my Nvidia rig, but it sounds like they still have a ways to go even with the most recent fixes.
deleted by creator
There was some noise a while back where Nvidia were going to do just that by moving the proprietary bits to the card and open sourcing the kernel bits.
What ever happened to that anyway?
deleted by creator
They did open source the kernel module:
https://github.com/NVIDIA/open-gpu-kernel-modules
But it’s just a code dumb. No real history of development.
Sometimes I wonder what the big hold-up was. I remember NVIDIA wanted one type of renderer while the rest working on Wayland went the other way.
I mean, Nvidia has absolutely no interest in Wayland. Any effort they put into supporting it will net them zero benefits. The fact they changed their initial stance and are supporting it at all is actually surprising.
My guess would be that Wayland has finally got to a place where said effort is finally small enough for Nvidia to make with minimal investment – like, one or two developers working on it part time.
Which means OP shouldn’t hold their breath.
Well they do lose some business in the Linux world to their issues and will probably take some time to recover their reputation in the Linux desktop community. I know not everyone hates them and the Linux Desktop community isn’t huge right now, but there is some incentive to show the world you care about your customers
And if Linux Desktop ever gets super popular and easy for everyone but Nvidia, that’s not a necessary risk Nvidia should take. And the catching up later on could be really slow and painful if Nvidia lets themselves get even further behind. GPUs are among the most complicated hardware components to support and develop drivers and other software for.
The Linux systems where Nvidia makes money don’t use Wayland.
As for desktop Linux… I have a feeling it might not be at the top of their priorities right now. To put it delicately.
Agreed. But it seems like since around two years ago Nvidia finally got the memo that Wayland will happen with GBM, and not EGLStreams. So with the recent changelogs fixing many issues I’m optimistic about Wayland on Nvidia.
I upgraded my graphics card to an AMD one because of this. It’s been two weeks for me using Linux for gaming and I love it.
I have always liked Nvidia for years. When I moved to Linux, the Nvidia drivers have been working great on X11. I am currently playing Baldur’s Gate 3 and I have DLSS 2 turned on and get frame rates at 100. Looks great and awesome game. But I know Wayland is the future and want Nvidia to work well with it and Steam. I will get an AMD if I have to but my card is still great and I am not looking for a new one yet.
When I first attempted to give Wayland a try, it just wouldn’t work. Did some troubleshooting but stuck with X11 for the time being.
About a month ago I gave logging into a Wayland session a try on a whim, and it just worked. Everything was fine, only difference was a change is mouse sensitivity.
When you have a HiDPI screen, wayland is a must. X11 just doesn’t have good support for it in my experience.
There’s a lot of other stuff where Wayland improves the experience. Pretty much everything hotplug works to some extend on X, but it’s all stuff that got bolted on later. Hotplugging an input device with a custom keymap? You probably can get it working somewhat reliably by having udev triggers call your xmodmap scripts - or just use a Wayland compositor handling that.
Similar with xrandr - works a lot of the time nowadays, but still a compositor just dealing with that provides a nicer experience.
Plus it stops clients from doing stupid things - changing resolutions, moving windows around or messing up what is focused is also a thing of the past.
I have had the same problem for a long time but I tried it again last friday, on an nvidia card still, games worked after an update or two
I was waiting for Nvidia drivers 545 to try again, but I checked last weekend and Ubuntu still had 535 drivers. I hear Nvidia did a lot of fixes for wayland on the new drivers.
I am on nobara for all that matters
Potentially related, not sure: does anyone know how I can get touchscreen scrolling working in Firefox on a fresh Ubuntu 23.10 install? Currently it’s just selecting text and it’s driving me up the proverbial wall. Googling was unsuccessful.
Try
MOZ_USE_XINPUT2=1 firefox
.Yep, dat werkte, dank! Maf dat dat niet standaard is.
I remembered having this problem and found the page that helped me: https://superuser.com/questions/1151161/enable-touch-scrolling-in-firefox
Much appreciated Bucky, I’ll give that a shot and will report back.
Edit: worked like a charm!
Not sure if Firefox supports that… For what I remember, PostmarketOS, Ubuntu touch and other mobile linux distros actually patch Firefox for allowing that behaviour
Requires login. Any word on when it’s making in stable?
Updated the link, hopefully it works now. Weirdly enough I was sure the original link I shared didn’t require it
When will this hit a stable release?