You can sign up to get a daily email of our articles, see the Mailing List page.
We do often include affiliate links to earn us some pennies. See more here.

One day, Wayland will truly take over the Linux world, but it's not quite there yet with plenty still using X11 due to various problems some of which the new Frog Protocols aim to solve.

Announced by misyl, who does various work for Valve (like Gamescope), it certainly sounds like a good idea to give Wayland Protocols a swift kick to get into gear to improve things for users. Writing on their social media post:

Wayland Protocols has long had a problem with new protocols sitting for months, to years at a time for even basic functionality.

This is hugely problematic when some protocols implement very primitive and basic functionality such as frog-fifo-v1, which is needed for VSync to not cause GPU starvation under Wayland and also fix the dreaded application freezing when windows are occluded with FIFO/VSync enabled.

We need to get protocols into end-users hands quicker! The main reason many users are still using X11 is because of missing functionality that we can be shipping today, but is blocked for one reason or another.

You can learn more on the GitHub and see the open Mesa Merge Request to hopefully get the frog-fifo-v1 protocol into upstream Mesa drivers.

Looking at the Merge Request, it's explained that SteamOS (Steam Deck) and Gamescope are already "shipping essentially this functionality" since version 3.5 as it's a "serious and genuine problem".

There's already a little bit of push-back from one developer Simon Ser who mentioned:

I don't think adding support for protocols essentially bypassing the wayland-protocols consensus is a good idea. The bar in wayland-protocols is not that high, and adding support for third-party protocols not representative of the Wayland community isn't a good way forward.

Which had a reply from Valve developer Pierre-Loup Griffais to note:

There is value in rapid iteration that the current development model is missing out on. If this would be better as an ext hosted on the upstream wayland-protocols repo, that seems fine to me as well, but I'm not sure that there needs to be a bar at all for an ext protocol other than being available for whoever wants to use it. On the contrary, reducing friction there would provide invaluable experimental feedback to the upstream development effort, and serve users during those long development cycles.

Interesting times, but it's good that something is being done to hopefully kick things up a notch and improve things, especially when it comes to gaming, for the rest of us.

Article taken from GamingOnLinux.com.
Tags: Misc, Open Source
27 Likes
About the author -
author picture
I am the owner of GamingOnLinux. After discovering Linux back in the days of Mandrake in 2003, I constantly came back to check on the progress of Linux until Ubuntu appeared on the scene and it helped me to really love it. You can reach me easily by emailing GamingOnLinux directly.
See more from me
22 comments
Page: 1/3»
  Go to:

I hope they succeed. Some of these protocols do take too long and way too many arguments on the correct way to do the same thing. Sometimes I get why, and sometimes I do think they should be more willing to just try things out and iterate.
Xpander Sep 24
Great news.

-Global hotkey support
-Copy-paste between wayland and xwayland that doesn't break
-Drag and drop between applications is finnicky and not always working
-Window management with positions, geometry etc are lacking features.

Just to name some. Hopefully things get better faster.
And lots of people use Wayland just fine already. It depends on the needs i guess.


Last edited by Xpander on 24 September 2024 at 9:18 am UTC
Well, I like my protocols cute and green, so this is good news.
kaktuspalme Sep 24
Quoting: Xpander-Global hotkey support
-Copy-paste between wayland and xwayland that doesn't break
-Drag and drop between applications is finnicky and not always working
-Window management with positions, geometry etc are lacking features.

I was thinking I'm the only one experiencing those. Especially drag and drop and copy and paste is one of the things not working reliably. Sometimes drag and drop even freezes the application and I have to kill it. It's hard to know wether it's an application specific problem a Wayland protocol implementation problem (I'm using Plasma) or a problem from the protocol itself.
All I know is, those things worked reliably on X11 and they don't work reliably now.

On my gaming system I don't encounter those problems, but while working I encounter them almost on a daily basis.

Due to scaling working way better on Plasma Wayland than Plasma X11 I kind of have to live with these problems.
Note that Simon Ser, maintainer for Wlroots, has helped maintain the wlr protocols for several years now back when Wlroots was ahead of the curve in terms of Wayland functionality. He's been bringing in protocols from wlr to upstream wayland protocols for a few years now.

KDE also maintains its own bespoke protocols and implemented some of the wlr unstable protocols.

I'm not sure how Frog Protocols is any different except in the way it's presented as protocols anyone can implement. In practice wlr protocols can be implemented by other compositors and KDE did implement them.

(from my perspective as a bystander)

Edit: clicking through some of the links, I can see the value in it. Individual compositor protocols are different than protocols intended for adoption in every compositor. The w-p repository really needs a kick in the ass. I can only hope Frog Protocols will provide that.

Or, as Xaver Hugl puts it:

Quoteone of the big reasons in MRs that have an (at least initially) active author is unresolved discussions about often theoretical issues, while at the same time some real world problems get missed. By experimenting in the real world before committing to a "stable" protocol, a lot of those problems can be avoided.


Last edited by pleasereadthemanual on 24 September 2024 at 10:04 am UTC
anth Sep 24
According to the replies to that announcement work is underway to package this for various distros.
coolitic Sep 24
Valve-associated people having to once again fix FreeDesktop's terrible development.
Linux_Rocks Sep 24
WMan22 Sep 24
If there is anyone who understands testing and rapid iteration, it's Valve. 100% on board with this, but then again I am an end user, not a developer. I also don't like the tendency to say "Xorg is dead" but also "Why do you need [thing only Xorg can do]? We're not working on that." cause while I'm not Xorg fan, understand why it's deprecated, and really appreciate a lot of what Wayland is doing, when a user says "Hey, I need this because ____" the answer is never supposed to be "Well tough shit then." but I've seen Wayland development have that mindset at times.

Frankly, the amount of time it takes the Wayland project developers to agree on certain things is ridiculous (why do we not have application Multi-Window management yet last I checked? That's a really basic thing.) and I'm pretty much in agreement with the things Xpander touched on in this comments section.


Last edited by WMan22 on 24 September 2024 at 7:02 pm UTC
Owltech Sep 24
It sure took a long time to get the patches that allowed users to disable vsync on Wayland. This idea really sounds great.
While you're here, please consider supporting GamingOnLinux on:

Reward Tiers: Patreon. Plain Donations: PayPal.

This ensures all of our main content remains totally free for everyone! Patreon supporters can also remove all adverts and sponsors! Supporting us helps bring good, fresh content. Without your continued support, we simply could not continue!

You can find even more ways to support us on this dedicated page any time. If you already are, thank you!
Login / Register


Or login with...
Sign in with Steam Sign in with Google
Social logins require cookies to stay logged in.