>>110034715
yserver doesn't have this issue.

>>110034715
plain X hasn't been battle-tested for years, it's time to move on

File: elite.jpg (80 KB, 460x740)

80 KB JPG

XORG XORG XORG YSERVER PLAIN X BATTLE TESTED GYAAAAAHHH

>>110034719
This is underselling it. Not only does it not have the CVE issues, it also doesn't have these retarded driver ABI issues BY DESIGN since it just uses Vulkan.
>a /g/eet was half way through complaining about this being and llm reply because of "not only..also", but "it" just stopped ;)

>>110034715
tearing doesn't really exist on amd does it ? I have radeon (not amd) and it virtually doesn't exist. I have no config. mpv does tear free in full screen by default. browsing www is tear free. how is it still an issue?

>>110034896
Must have been running xfce

>>110034896
it does it exist because of the option you have to turn off as a workaround until they release a fixed version lol.
add this to your config, and you will immediately see tearing again:

Section "OutputClass"
  Identifier "AMDgpu"
  MatchDriver "amdgpu"
  Driver "amdgpu"
  Option "TearFree" "off"
EndSection

>>110037133 (me)
*doesn't exist

>>110034715
>day 4
>upstream fix not even merged yet
>arch package with no backported fix
this is sad desu.
did everyone move to wayland behind our backs or smth?
and how did void manage to backport a fix before arch?

File: waiting.png (62 KB, 2198x182)

62 KB PNG

>>110038157
It looks like zero Arch developers run xorg, since they don't appear to be feeling any pressure to fix the broken package, and will be waiting for upstream to merge the needed fixes AND cut a new release.