News for hackers. Stuff that matters.

A comment on X.org Security Advisory: multiple security issues X.Org X server and Xwayland. Parent comment

Re:X.org Security Advisory: multiple security issues X.Org X... by mikkupikku on Sunday November 02, 2025 @03:49PM (#45793302)
Using a compositor fixes screen tearing, no need to use Wayland for that.
[ Parent | on HN ]
Re:X.org Security Advisory: multiple security issues X.Org X... by marmight on Sunday November 02, 2025 @04:55PM (#45793779)
Even a compositor is unnecessary to fix screen tearing these days: https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests...
[ Parent | on HN ]
Re:X.org Security Advisory: multiple security issues X.Org X... by phkahler on Friday November 07, 2025 @10:57AM (#45847704)
>> Using a compositor fixes screen tearing, no need to use Wayland for that.

Right, and that abandons the whole X drawing API in favor of passing around client drawn bitmaps. That was one of the big points of Wayland too - X has a whole bunch of stuff that no modern apps use anyway so lets throw it out and build up a better version of the capabilities we need.

If we abandon the X drawing API and half an OS included (memory management) and use KMS, all that's left is the features that are security holes.

[ Parent | on HN ]