wayland SUCKS (for me)
| wayland sucks in general and anyone insisting on it deserves to be waterboarded until they stop breaking things that work perfectly fine without their input
| after years of use. i don't miss wayland.
it had it's moments where it was better then X. then they updated it.
no idea what's been going on with the wayland dev team for the last few years but i hope they get mental help.
| what even is debian lts, trixie?
| Why are you surprised that LTS distros, who's target audience are institutions where upgrade migrations warrant a lengthy support window, don't have the latest and greatest of KDE and Wayland? I'm not trying to be harsh here, but I'd bet everything on your reasons here not being backed up by objective truths, debian is not the amazing base uninformed sycophants would have you believe; not to trash it entirely but the vast majority of supposed pros I've seen claimed are just wrong.
| Also, frozen package versions, added support difficulty in backporting fixes, and other LTS woes aside... just because a distro offers one DE or another doesn't mean the same amount of effort is being put into maintaining it. If you want the best KDE experience consider at least using a distro where achieving this is a considered a high/higher priority.
| I use wayland for about a year now on my desktops. It improved much, but yes its still is not as reliable/stable as x11. Especially not on devices with older GPU (namely 4th gen intel).
For deployment at my work (me admistering above 300 diverse Client PCs running with KDE Neon) I remove wayland option from sddm.
For older devices I'd even recommend not to use KDE (which I love) but trinity Desktop instead (Q4OS is a good debianoid distro).
| X just works, wayland doesnt. End of story.
| >X
>works
heh
| >common x issues
>nvidia shat the bed again
>the user copypasted a xrandr command and broke their opwn setup
>common wayland issues
>less protocols than a ps3 has games
>the opening post of this fucking thread
i bet you use arch
| Take note that nvidia doesnt shit the bed with wayland. There is no bed at all.
| I can agree with you in one aspect at least, speaking from my experience with other distros anyway, wayland sucks... for VMs if you aren't using 3D acceleration. I'm pretty sure, but not 100%, that this is universally the case due to ?non-existent 2D acceleration? in wayland.
| >>1076062
>>1076059
i just want to listen to a youtube playlist while i play minecraft in a discord vc with my friends
but then brave keeps giving me that "Aw, snap!" error code 11 thing
and then vesktop crashes too and burns kwin while closing all of my apps along with it
and then the entire screen freezes but audio keeps working so i hear my player die
i turn it off and on again but the monitor just keeps saying "hdmi1: inactive" for the next 2 hrs
i'm a bit tired g/u/rls
| Have you tried to determine what the issue more precisely is i.e., checking logs via journalctl after rebooting?
While you should consider a live usb of something with more updated packages to confirm the same issue occurs regardless, it's not unlikely your problem could be just an older kernel, particularly with nouveau as historically it's been less than perfect, so while recent developments may have improved this enough for you an old kernel will be missing some amount of that.
| Sounds like years out of date KDE plasma, when Wayland wasn't the default. And the issue with old intel has been fixed since plasma 6 or something, which was released almost 2 years ago.
| I uhh, kinda hate it when people get mad and say Wayland doesn't work because they use an ancient version of it and experience bugs already patched like last year
It's unfinished software if you use an old version expect shit to be broken ?????!?!!!!!??
| >>1076336
>And the issue with old intel has been fixed since plasma 6
Yeah, as I said it improved much and I use a very recent version on my machine. The thing is, if you want a recent version you may use a rolling release distro like arch/kde neon. Unfortunately they sometimes break things again from time to time. The dependencies between kernel, wayland and desktop components are too complex to prevent them and support for old hardware is (understandably) not highest priority.
| The isolation from non-kde gui apps through flatpak improved a lot in keeping them uptodate while not bricking the kde core system (and wayland).
However, experience this improvements is still more satisfying compared to windows systems (yeah unfortunately I stil have to work with them too), where every improvement (and surprisingly they do!) comes with the really ugly price of giving up even more control of your system/data/sovereignty.
| My old computer refuses to work with Wayland half the time, so I totally agree, too many issues. I do really like a lot of stuff it does so sucks I can't use it. And almost every new update something breaks somewhere, it's a miracle I don't need to reconfigure anything after a Wayland update. I just use X11 and Xfce now.
| >>1076344 just looked it up and Debian 12 switched to Wayland default in June 2023 and used plasma 5 still? so you've got me there
Not a good decision in my estimation, but KDE switched to Wayland with plasma 6 (Feb last year) and maybe it's just me but I don't expect perfect stability from a newly released DE
Admittedly I use tumbleweed so I expect issues with a rolling release and rollbacks are like two commands and a reboot so maybe I'm biased
| The one major regression I remember was a Nvidia driver issue that caused xWayland windows to flash which did make me switch to x11 until that got fixed but Wayland had a feature that'd fix it but the Nvidia driver just didn't have support for it yet
Refresh
| my setup is default KDE (which comes with wayland and noveau OOTB now) and debian LTS
i was really expecting a modicum of stability with this generic vanilla setup and i just did not get that with how many times brave and kwin and vesktop crashed
is LMDE any better? (w/ x11 ofc)