You got it, @Girtablulu. Updating now.

Apparently wayland-protocols >= 1.17 is required for Wayland support to be enabled, do we drop Wayland for now or update Wayland first?

In D5367#85879, @JoshStrobl wrote:

I'd prefer we update wayland-protocols first. If you want to provide a patch for this, that'd work for me. Otherwise, I can look into updating it this weekend to unblock this patch. Would prefer we don't regress in Wayland support, even if Wayland support for Solus still remains pretty much non-existent.

I attempted to patch the versioning file to force it to allow 1.16, but it looks like it actually uses features from 1.17. Guess it'll need a wayland-protocols update after all. I'll leave it to you.

I have updated wayland-protocols to 1.17 https://dev.getsol.us/D5611

In D5367#93161, @DataDrake wrote:

Any word on this not that wayland-protocols was updated?

wayland-protocols is still at 1.16, the differential commented here was closed by Josh. Still waiting on an update to the package.

Kitty is now at 0.14.3. This diff can be closed.

You can just abandon this.