It just works. Why are you still on x11?

Still no tearing control in OpenGL.

I'm not on X11

I want to run my 144hz monitor at 120hz so YouTube videos don't stutter when they aren't fullscreen (because VRR would engage) but you cannot set custom refresh rates.
Not a problem on X11 or Windows, impossible on Gayland.

>>106118451
X11 is a protocol that xlibre implements just as much as xorg does.

It's like saying you're not on Wayland and posting the hyprland logo.

>>106118413 (OP)
I *need* SimpleScreenRecorder

it most certatinly does not just work if you want to game. otherwise i guess

I get artifacts on Plasma Wayland (using an nvidia GPU).
But I refuse to use X11 (no HDR).
I am fucked

>>106118453
>custom refresh rates
xrandr once bricked a monitor, was my fault but unexpected, basically you can set a refresh rate above the recommend one and it will apply it, on old monitors it bricks them.

>>106118453
Edit edid to add 120hz modeline
Load custom edid on boot
Not that complicated, there are multiple guides out there

>>106118413 (OP)
I switched to Wayland because a horrific bug on X11 and Nvidia, haven't switched back since Wayland just werks fine

>>106118568
It was nice, I switched to OBS which is a whole ass suite but does the job very nicely

it didn't just work for me, I get a lot of artifacts on my secondary monitor to the point where it's useless

>>106118451
X11 is the protocol, retard
>>106118413 (OP)
X11/X.org works

>Mffw I want to use X11 but AMD broke support for 9 months by now
And people say there is no conspiracy

linux is when you have 10 protocols, 50 implementations and none of them work

I was against wayland for a while but I'm using dwl (wayland dwm clone) on a 4k TV with 1.8x DPI scaling and everything looks perfect. Even the best DEs would sometimes screw that up in X11.

>>106120875
>amd
Intel chads win again

>>106120858
I look like this

Why is this board so jam packed full of fucking bait

>>106121142
ban evasion is too easy nowadays, that's why.

>>106118413 (OP)
Because it doesn't work.

Wayland is shit.
0. It's kiosk trooned to desktop (so we start from a rot foundation).
1. It's async oop in C with implicit sync (ALL implementations have exploitable LPEs because of this)
2. It increases attack surface (communication is a workaround through dbus+portals+pipewire)
3. It has no security model (even xorg has one)
4. It has no protocol to ensure its "isolation" (which is simply not doing X). So it's trivial to bypass the "isolation".
5. It can suffer a DoS from moving the cursor too fast.
6. It obliterates portability among the same OS. As every compositor is comparable to a different OS.
7. Policy over mechanism.
8. The core protocols are as capable, if not less, as the curses library (reason why everyone is doing their own extensions for bare minimum capabilities).
9. Literally everyone else (windows, mac, plan9, android) has a better display server. In fact, it's hard to find such a demented attempt even among hobby OSes.
10. Mesa is adding workarounds to its code for wayland. So, not satisfied in being shit, it shit on others.
11. It's brings versioning incompatibility problem (one of the reasons for Linux to have so few ports for it) to desktop level.
12. There's no "wayland" (since the raw protocols are useless). So basically you port for kde, gnome or wlroots (a port for one, does not ensure it will work on the others. Additionally, you need to consider portals too. A port for wlroots won't necessarily work on wlroots if it were expecting a specific portal).

For the past two weeks or so, I've had two computers at my desk. One is my normal Arch/Xorg/Xmonad setup, the other is Bazzite/Wayland/KDE going to a friend.

Previously knew nothing about flatpaks. Never used Wayland, or KDE, or any of the wine helper tools. All of it is different to me.

>>106119115
>does not just work if you want to game
That hasn't been my experience. At first I couldn't get a Dualsense controller to work with PCSX2.
But apart from that issue, I didn't have to do any further hardware configuring, troubleshooting, etc. That's messing around with games using Steam, Lutris, and a few emulators.

>>106120875
>use X11 but AMD broke support
What are you talking about? Both of the computers I mentioned above are AMD/AMD.

>>106121268
>3. It has no security model (even xorg has one)
lol. any app can see any other's app's window. discord can see what's in your browser window, x11 is that retarded for security

I don't know, I just use whatever came with Debian. I'm sorry.

>>106121632
any app can see another app's key presses*, let's not get ahead of ourselves
also if you have a malicious app that takes advantage of that you already fucked up

>>106118451
>xlibre

Um, sweaty? Why are you using a windowing manager that Hitler himself would have approved of?

Fuck Wayland, I almost go back to windows because of it. No more troubleshooting since I started using X11. I don't even know shit about how it works or even what it does. All I know is fuck Wayland

>>106118413 (OP)
I get weird green graphical artifacting in Qt apps, if you tell me how to fix it I'll go back to Wayland

>>106121099
i wish we could cuddle OwO

>waybloat

i dont use a compositor

>>106118413 (OP)
Bricked my system on KDE

>>106122374
Its problem is that it's too lightweight aka "you deal with my headaches instead"

>>106118413 (OP)
>doesn't let me use global hotkey shortcuts in OBS without websocket fuckery
>doesn't let me use global hotkey shortcuts in most recording applications in general
Wayland is shit

>>106120875
what do you mean by this?
i use RX6600 with X.org, cinnamon and arch

>>106121632
>lol. any app can see any other's app's window. discord can see what's in your browser window, x11 is that retarded for security
Explain why this is bad for somebody who wants to record their screen with global hotkeys.

>>106121709
that only makes it better

>>106118413 (OP)
I need easystroke, can you port it already ?

>>106121632
> what is xephyr
> what is use xnamespaces
wayland it's not only bad it's literally boycott. it repeats the same problem that held linux ports for so long, versioning. now at software level and at a much worse intensity. has only three possible ends: it dies, linux dies, linux becomes gnome os only.

>>106118413 (OP)
It fucking doesn't, fractional scaling is properly fucked in my system, text is blurry (Nvidia GPU btw)

test

>>106118453
And you cant? I have a 240 hrz monitor and sometimes I had to go down to 120 hrz because some retrogames wont fps limit with mangohud, so this is the next easy way to do it. Im using Arch Wayland kde

>>106118423
use case?

>>106118451
okay lunduke...

>>106118413 (OP)
>It just works.
It doesn't.

>Why are you still on x11?
Because it actually fucking works.

>>106123065
>cinnamon
is my baginer too can't just kde it doesn't stick with me.. used to use dwm and hyprland, but I always just come home to cinnamon

https://youtu.be/4m3Y2VPqGAM?t=130

Wayland is a failed project.
X.org is mature, stable and needs no shilling campaign for adoption. You do the initial setup and then you forget about it.

>>106118413 (OP)
>insane input lag when playing games
yeah, nah

>>106121632
Any application on wayland can see any other application on wayland as well since every wayland compositor has a private compositor protocol that allow recording the screen without permission. This private protocol has no security.

>>106121632
X11 fixed this over 20 years ago with XACE. Try again retard. X11 got mandatory access control before android did.