>>109362869
I had a ton of issues with Wayland and couldn't use my Razer pro gaming mouse on my MSI Nvidia laptop, so I installed x11 since it has more compatability, even if it is less secured, I just used Firewall to keep things from moving around without permission.

labwc isn't too bad. Its a spiritual successor to OpenBox and works roughly the same. Its pretty barebones but works with various panels and app launchers like rofi and xfce4-panel.

>>109362869
You sound like a faggot but labwc is what you're looking for.

There's literally nothing wrong with KDE. I don't know what proprietary (e.g. noVideo) shit people are running that gives them so many issues.

>>109362869
What desktop environment are you running on X11? I'm sure some anon's will have suggestions if they understand your preferences.

>>109362893
I made the transition from X11 to Wayland earlier this month, and it was considerably easier in my experience.
I initially attempted to use Sway, which despite looking good, felt sluggish to use (I'm not sure if this is a specific to Sway or stems from i3 which I've never tried on X11). Before giving up on the transition I experimented with DWL, which worked perfectly. I've had zero problems with getting my system ported or adjusting to native Wayland tools. My favourite improvement is how bloody smooth the compositor is - I don't think I've experienced a single bit of screen tearing (which I never fully resolved on X11).

>>109362869
unsubscribe

>>109363453
Denied.

>>109362869
Xfce and Cinnamon are getting stable Wayland support "Soon" (TM)

>>109363446
> What desktop environment are you running on X11? I'm sure some anon's will have suggestions if they understand your preferences.
Currently using MATE, i liked xfce4, I'd run KDE if I had more RAM.

I'd think labwc is probably the only viable option for me, I could use suggestions for panels and other thingamajigs that might be needed.

I heard GNOME Flashback might be an option but I don't want to touch anything modern GNOME desktop environment with a 10 feet pole

>>109363446
>What desktop environment are you running on X11? I'm sure some anon's will have suggestions if they understand your preferences.
>I made the transition from X11 to Wayland earlier this month, and it was considerably easier in my experience.
>I initially attempted to use Sway, which despite looking good, felt sluggish to use
Wayland will almost always have more input lag than x11, even in nearly identical setups. It usually lags about a frame behind x11.

>>109362893
What kind of mouse doesn't work on Wayland? Do you need some custom xf86-input driver for it?

>>109363744
The dank material shell seems popular lately:
https://danklinux.com/

Not tried it though.

File: xanalogtv.jpg (228 KB, 1280x720)

228 KB JPG

I tried wayland and worked fine for me on debian stable and KDE, xscreensaver is the only thing keeping me on x11 for now.

>>109365688
Why do you need a screensaver? DPMS has made that obsolete for years now.

>>109362869
>Aside of KDE and GNOME which I refuse to run
get a job

There is also wayfire.

>>109363780
You are just making shit up.

>>109365699
because it looks nice

>>109365888
Absolutely not, Wayland forces a frame of lag. You see, a window itself cannot submit new content to the compositor until it is finished drawing, as such all window updates happen on the next frame.

On xorg, a window could update during drawing, meaning you could get near instant visual updates.

On xorg you can optionally enable a compositor to force the same behavior as Wayland, but on Wayland this behavior can only be disabled in fullscreen windows.

>>109365976
Modern gpus basically don't work properly with x11, since the early 2010's running without a compositor results in terrible fucked up tearing even if you try to wait for vsync. The only solution is enabling TearFree which adds a frame of latency just like a compositor. Its a fucked up situation.

Also, nobody will see this post. This subject is hard censored. Nobody ever acknowledges it.

>>109365902
What are you, a child? Just put on some fullscreen video if you want to look at it that badly.

>>109362869
Lxqt with kwin might be a good choice, given that kwin is the most mature Wayland compositor and you don't like plasma

>>109366034
i just don't care about tearing outside of video and games

>>109362869
I run sway (i3 for wayland) with a single line in my config that makes all windows float by default. It's really that easy bro.

for_window [class="^.*"] floating enable

and on hyprland

hl.window_rule({
    match = { class = ".*" },
    float = true
})

File: dc prefetch.jpg (1.21 MB, 1328x1494)

1.21 MB JPG

>>109366320
Its not the normal kind of tearing though. Its a very particular and unique kind. Classic tearing is randomized across the entire screen. The kind of tearing I am talking about always happens at the exact same location on the screen. And it also happens in games and video. Vsync on x11 works by waiting for vertical retract before doing a bitblt, modern gpus completely break this, because they have agreesive prefetch into a large fifo buffer of over 1MB in size.

Here is an image showing the tearing on my 9070XT. The top program is an SDL application with vsync enabled. The bottom is an x11 application which was filling the entire screen black and white in a loop with a 0.5 ms delay

>>109362869
I can't tell the difference between kwin and labwc
the only difference is that xfce only works with labwc, lxqt works with both

>>109362893
Ironically the security changes are what make Wayland unacceptable to me. I fuck around in live memory too often, and expect processes to be able to freely hook or talk back and forth. [spoiler]I'm also insulted on a visceral level at the notion of having to take additional steps to have something as bread and butter as remembering window sizes/placements between application launches.[/spoiler]

>>109365888
he does this in several threads, he's already admitted to be running on like 10 year old hardware on an iGPU lol