zen-kernel VS wlroots

Linux is configurable. If you don't want it to freeze up, configure it so it wont https://github.com/zen-kernel/zen-kernel

What do you mean fingers in the pie? And for liquorix the four people are only the ones involved in the packaging, you'll notice that they just include one huge monolithic patch here https://github.com/damentz/liquorix-package/tree/6.1/master/linux-liquorix/debian/patches/zen and to see what is inside that and whose fingers are in there you need to look into https://github.com/zen-kernel/zen-kernel and you have exactly the same situation as with xanmod with your 13k contributors.

It seems like the zen kernel "doesn't use" the same version as the upstream kernel (default). I think for now it is still on 6.0.12: https://github.com/zen-kernel/zen-kernel

Find the source here.

Officially supported kernels Community support on forum and bug reporting is available for officially supported kernels. Stable — Vanilla Linux kernel and modules, with a few patches applied. https://www.kernel.org/ || linux Hardened — A security-focused Linux kernel applying a set of hardening patches to mitigate kernel and userspace exploits. It also enables more upstream kernel hardening features than linux. https://github.com/anthraxx/linux-hardened || linux-hardened Longterm — Long-term support (LTS) Linux kernel and modules. https://www.kernel.org/ || linux-lts Zen Kernel — Result of a collaborative effort of kernel hackers to provide the best Linux kernel possible for everyday systems. Some more details can be found on https://liquorix.net (which provides kernel binaries based on Zen for Debian). https://github.com/zen-kernel/zen-kernel || linux-zen

linux5.18-zen $: cd patches patches $: wget https://github.com/zen-kernel/zen-kernel/releases/download/v5.18.11-zen1/v5.18.11-zen1.patch.xz patches $: xz -d v5.18.11-zen1.patch.xz

@OP So yeah on Linux we don't have NVE which i'm kinda glad about for various reasons. But we have gamemode (sorry for the ArchWiki entry on it) and custom kernels like Zen. If you opt to install the Zen Kernel ALWAYS keep a regular Kernel as backup, just in case.

I was afraid that disabling dm-crypt workqueues caused it: https://github.com/zen-kernel/zen-kernel/issues/282

>barrier has been unmaintained for a long time.

As if not having new features added for 2 years makes it stop working? barrier is perfectly fine on normal linux desktop installs. I actually use synergy 1.x personally which has been "unmaintained" for much, much longer. Except synergy 1.x will compile and run on anything from windows 98 to ubuntu 5 to debian 12. You can't get a waynergy or inputleap to compile on an OS more than 2 years old. And even then, as you say, it's crapshoot if the particular wayland will have libei; many like sway are actively hostile to it and never will: https://github.com/swaywm/wlroots/issues/2378

It looks like they actually patched it to filter those modes out, so presumably it worked out of the box and was considered undesirable: https://github.com/swaywm/wlroots/issues/3038

I haven't experienced any of those. The video game performance hit may be due to vsync, but I don't play games so I haven't noticed.

You can however use tinywl. It is an example Wayland compositor that can't do more than displaying one application.

Sway/wlroots has implemented this, but I can't find any discussion for KDE.

wlroots is archived on github. Is it abandoned? Just saying, that only means they moved git hosts :-D

A lot of compositors are based no the wlroots lirbary. So they are still sharing the development effort and have a common base, its just in the form of a library rather than a display server.

gamescope use wlroots