Firefox (finally) enables Wayland by default on their builds
Firefox (finally) enables Wayland by default on their builds
phabricator.services.mozilla.com
Login
61 comments
-
-
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.
-
-
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.
-
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.
-
-
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
-
-
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.
-
-
Please educate me
What's wayland?
-
According to https://wiki.archlinux.org/title/wayland
Wayland is a display server protocol. It is aimed to become the successor of the X Window System. You can find a comparison between Wayland and Xorg on Wikipedia.
-
A compositor. Wikipedia
-
-
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.
-
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!
-
-
Try
MOZ_USE_XINPUT2=1 firefox.-
Yep, dat werkte, dank! Maf dat dat niet standaard is.
-
-
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
-
-
Huzzah!
-
When will this hit a stable release?
-
-
Some of those arguments are legit but like half is complaining about wayland being fundamentally different to xorg and obviously you cannot use straight xorg apps on it.
"Linux is inferior because it breaks all my powershell scripts and all my windows only apps. Don't use linux."
-
I mean, to play devil's advocate here - if functionality that you need is all of a sudden swept out from under you then it doesn't matter from an end user perspective if it's not the intended design for Wayland - to the user, Wayland is broken in that regard.
A better equivalent would be if an application you used every day for the last 10 years all of a sudden has an update that kills features you used because that's no longer part of the dev(s) vision. Or headphone jacks on phones. Or whatever that weird thing with Teslas where they disabled a sensor in an OTA update and replaced it with some other solution(?).
Or to modify the example you put, if Windows killed the cmd shell and only left powershell in a Windows Update.
I have an application that I need to use at work which will never fit Wayland's design, short of me either finding a new job, keeping a Windows install around, or using a really old version of Linux around in a VM when X11 has completely disappeared from all distros (which won't really work) - there will be nothing that I can do about it on the Wayland side because it's highly unlikely the devs will update it to be compatible (since it's a shock that they actually even had Linux support in the first place).
As it is, I currently just pop into an X11 session whenever I'm on working hours, it will suck that I can't do that with Fedora come next release when they completely drop X from the repos.
-
-
This is literally comedy lmao.
Most points are just complaining that tools specifically designed for X don't work on Wayland. That's like hanging onto your childhood pants and complaining they don't fit anymore.
-
And one of the first points is how Wayland crash will bring down all running applications - yep, just like on X11! But it's somehow Wayland's fault.
Besides the fact that on Wayland running apps can survive a compositor crash (I think new KDE will have that feature), which I doubt can be done on X11.
-
But many of those are actively used by people. I use screen recording, screen sharing, global menus, key automation and window automation every day. Even if I wanted to use Wayland I couldn't. What exactly is it that you want me to do?
-
-
-
I suppose it explains why people have a bad attitude about Wayland when tools providing useful functionality are described as trojans.
X11 can (..mostly..) have great security by just providing a suitable X Security module to it. It just seems it wasn't considered that big of an issue that anyone bothered. Nokia Maemo/Meego used to rock such a module.
-
-
Wayland does not work properly on NVidia hardware
That's a feature, stop buying hardware from vendors that treat GNU/Linux and *BSD users as second-class citizens and locks them into proprietary drivers.
Wayland is biased toward Linux and breaks BSD
Seems to work just fine on FreeBSD.
Wayland breaks games
Games are developed for X11. And if you run a game on Wayland, performance is subpar due to things like forced vsync. Only recently, some Wayland implementations (like KDE KWin) let you disable that.
Gaming performance is actually better on Wayland.
-
That’s a feature, stop buying hardware from vendors that treat GNU/Linux and *BSD users as second-class citizens and locks them into proprietary drivers.
Nowadays I buy a new graphics card maybe twice a decade. I'm not changing the card for software.
Also, we're all using proprietary hardware. Be serious. If you tried to never use anything proprietary you'd never use anything. You're using like a dozen of them right now.
-
Gaming performance is actually better on Wayland.
*on some games...
Did you read your own source? They covered:
Cyberpunk2077 (slight advantage to Wayland on AMD, slight advantage to X.Org on Nvidia)
DiRT Rally 2.0 ( X.Org is clear winner...)
F1 22 (Slight advantage to Wayland on AMD, clear advantage to X.Org on Nvidia)
GTA V (Clear advantage to X.Org Nvidia only... Since AMD was having driver issues with this game)
Hitman 3 (Slight advantage to Wayland on AMD, clear advantage to X.Org on Nvidia)
Metro Last Light Redux (Slight advantage to Wayland on AMD, clear advantage to X.Org on Nvidia)
Shadow of the Tomb Raider (Slight advantage to Wayland on AMD, clear advantage to X.Org on Nvidia)
Total War: Three Kingdoms (Slight advantage to Wayland on AMD, clear advantage to X.Org on Nvidia)
X-Plane 12 (Slight advantage to Wayland on AMD, clear advantage to X.Org on Nvidia)
Quake 2 RTX (slight advantage to Wayland on AMD, slight advantage to X.Org on Nvidia)Where "slight" is within a few frames... let's call it 0-5 frames... and clear advantage is ~10 frames+...
It's clear that X.org is better overall. It's capable of giving the user more options in hardware with less bullshit.
-
-
61 comments
To be clear, many of us will have already been using Firefox in Wayland mode by default, if our distro enabled it.
E.g. Fedora Workstation has had Firefox in Wayland mode since Fedora 31
And it's thanks to the work of those people that it has finally made it upstream, specially Fedora's Martin Stránský (who has been doing tons of work on Firefox, including making Fedora the first distro to ship Firefox with VA-API enabled by default).
Silly question but does that include Fedora spins like the KDE spin? I think the last time I checked Firefox it still said it was running through XWayland (although that was a while ago)