This Week In Security: Docker Auth, Windows Tools, And A Very Full Patch Tuesday

CVE-2026-34040 lets attackers bypass some Docker authentication plugins by allowing an empty request body. Present since 2024, this bug was caused by a previous fix to the auth workflow. In the 202…

Hackaday
X.Org Is Still Alive and Just Fixed Five New Security Flaws

X.Org still receives security fixes in 2026, with five newly disclosed vulnerabilities patched in X.Org Server 21.1.22 and XWayland 24.1.10.

Linuxiac

Generally speaking, #Xwayland should be avoided for gaming where possible (which still isn't always possible, especially until Steam fix their overlay). The high latency people experience after switching from #X11 to #Wayland does not come from Wayland itself, but the indirection of this legacy compatibility layer. Don't take my word for it, this was measured in detail by David Justo this year:

https://davidjusto.com/articles/m2p-latency/

Building an Input Latency Meter (Because ‘Wayland Feels Off’ Isn’t a Metric)

A repeatable way to measure end‑to‑end input latency: Arduino HID input + phototransistor sensor to time screen luminance changes, comparing Wayland, X11, XWayland, and Windows.

David Ramiro Justo

There currently are two recent #Phoronix articles that are shared widely, comparing #KDE KWin 6.6 vs #Gnome Mutter 50 in terms of game performance (one for AMD, one for Nvidia). What it lacks to me is a disclosure whether this is comparing the pure #Wayland compositor performance or more specifically their #Xwayland integrations. At least for the Windows games I will have to assume it is the latter (as Proton does not yet _default_ to Wayland).

#Linux #LinuxGaming #Nvidia #AMD

@cks Allegiance to ultimate evil can explain a lot of design choices out there. Incrementally piling stuff atop stuff probably covers most of the rest.

As a longtime #fvwm user I was hoping maybe #xwayland would let fvwm drive the display, but fallback positions are either ignoring Wayland entirely as long as I can or looking for which of its solutions will torque me off least.

I just realized I run my #wayland setup with #sway with disabled #xwayland since like a month, and I don’t miss anything. One, two years ago I tried that already and it broke GIMP and Zotero. Both got updates and work with native Wayland nowadays. I’m satisfied :)

@thelinuxcast this post from https://who-t.blogspot.com/2016/01/xorg-project-vs-xorg-foundation.html is old, but explain the different things that X.org can mean (the foundation, the project) and how they relate to #Wayland (and other things around GPU drivers).

Maybe @whot should re-publish it yearly. 😄

Sadly the post does not mention that #Xorg (without a Dot after the X!) is something different (it's the older and once widespread of two popular X-Servers the X.org project publishes these days; the other one is #Xwayland).

X.Org the project vs X.Org the Foundation

In light of recent general confusion between X.Org the technical project and X.Org the Foundation here's a little overview. X.Org the proj...

I've got a weird issue with #XWayland. It's not a total deal-breaker, but it's just a bit annoying...

(I'm running KDE Plasma 6.3.6 on Debian Trixie (stable))

My laptop display (left) is set to 1.85x scaling. My 1080p display (right) is set to 1x.

If I don't turn on the option to manually scale XWayland applications ("Legacy applications (X11): Scaled by the system"), the X11 applications I use look SMALLER than normal on my main (right) screen. Left screen too, IIRC.

If I DO turn on that option ("Scaled by the system"), then the applications look great on the main (1x) screen, but they're of course a blurry mess on the left (1.85x) screen.

I thought the setting meant that the applications would be smaller than normal (unscaled) on the left screen, but they're actually tiny on both screens.

Any ideas?

#Linux #Wayland #X11 #AskFedi #HiveMind