Wayland has a bright future ahead: The move from Xorg to Wayland had a rough start, but things have improved, and there is an exciting roadmap for the future.
-
I might switch to wayland when xfce starts to have decent support for it. I'm not a ride or die Xorg fan, I just want to keep using the DE I'm used to.
Same currently using xfce with opensuse
-
This post did not contain any content.
In this current state it's currently only in a few des (kde and gnome has it stable) and windows manager(wayfire and Sway and qtile has it stable) but maybe in the future it will be most des
-
I'm not familiar with Bazzite. Did you get those drivers from Nvidia's website? That's my only issue with Debian 13 right now. Everything else is working as expected. Also the reason I had to get the drivers from the website is somehow I couldn't enable some stuff (like amd-pstate) on the default Bookworm kernel and had to use a backported one.
No, they're included with, and updated by, the OS. But they are the proprietary ones that are available on Nvidia's website.
-
Issue is already closed though and might have more to do with xwayland itself it seems. Also fwiw, i just tested steam on niri with xwayland-satellite a few weeks ago and it worked just fine.
issue closed != issue resolved though. it worked "a few" weeks ago and now it doesn't. other people in fedi and one in that issue have the same problem too.
-
What issues do half of your X11 apps? Ive never had an issue with an X11 app running through Xwayland, although I also dont have many X11 apps left.
mostly windows going blank or straight up refusing to launch
-
if one goes out of their way to use a system without xwayland, that's on them not Wayland lol
but i do have xwayland. please read my comment again.
-
at which part did they set the house on fire?
yeah really confused about that reply too. is using anything other than Gnome on Wayland "setting the house on fire"?
-
"I set my house on fire damn why did my house burn down its the builders fault."
xwayland-satellite is the recommended way to run X11 apps, which are unfortunately still many, on niri. is that "setting my house on fire"? really confused here.
-
No, they're included with, and updated by, the OS. But they are the proprietary ones that are available on Nvidia's website.
I'll try again this weekend. But that's the only thing I've changed before being unable to log in a wayland sessions. Hope it works though.
-
until you start using it and screenrecords dont work, multimonitor setups work once and then fail forever...
systemd,wayland, unity, ubuntuOne and all that stupid shit can right f off.How can I fix the multi monitor thing?? Whenever I connect my TV screen everything freezes unless I unplug one of my desktop monitors.
-
Sorry but pipewire is shit and it works with Wayland (didn't see anything Wayland uses pulseaudio) and I believe Wayland still not ready for use, It's unstable for me because pipewire crackling like fire
Pipewire works fine on my Intel 5960x, Intel N3700, Intel 9900k, Intel 9700, AMD 4800HS and even my Intel ES Erying system. No pops or crackles from any inputs or outputs.
I've not tried with a dedicated sound card, just the onboard on all these systems.
Running KDE on one system along with Hyprland on another two with the remainder as headless systems.
You sure this issue isn't somehow related to your hardware or something else?
-
until you start using it and screenrecords dont work, multimonitor setups work once and then fail forever...
systemd,wayland, unity, ubuntuOne and all that stupid shit can right f off.I've never had a problem with multi monitor (knock on wood). I had to get around screen recording in the past, but I thought that was ironed out. I'll check that out today.
The only hiccups I've run into so far is that the KDE color picker (the dedicated widget and the screenshot tool) is off by one shade. I grab #222222 and it gets #212121. I got around that by using Flameshot. And that's more on KDE's end afaik.
The other hiccup is constant alerts asking for input permissions when I use something like an autohotkey or autoclicker.
I'm not saying its perfect yet. I'm saying they've busted ass getting it to where it is in such a short amount of time. Its incredibly usable to me for how young Wayland is.
-
Pipewire works fine on my Intel 5960x, Intel N3700, Intel 9900k, Intel 9700, AMD 4800HS and even my Intel ES Erying system. No pops or crackles from any inputs or outputs.
I've not tried with a dedicated sound card, just the onboard on all these systems.
Running KDE on one system along with Hyprland on another two with the remainder as headless systems.
You sure this issue isn't somehow related to your hardware or something else?
No, pulseaudio working fine but pipewire isn't, it's a spare old PC HP COMPAQ 6005 pro SFF with AMD Phenom II X4 B97 ram 8GB ddr3 and its sound card SBx00 AZALIA Intel HDA
Pipewire crackling while pulseaudio working without problems -
Get your shit together.
I make perfect sense to people who actually read what I said. PipeWire issues aren’t imaginary.
-
issue closed != issue resolved though. it worked "a few" weeks ago and now it doesn't. other people in fedi and one in that issue have the same problem too.
Fair enough. I wasn't aware you actually had that problem yourself, i thought you just looked it up to prove a point lol. I do think it's a weird decision that niri doesn't just have xwayland built-in. Even river has native xwayland support, which is much more focused on minimalism. I haven't used niri all that much because so far haven't really been able to get used to scrolling. I think i still prefer dynamic tilers with a layout system. I should probably try booting up a game in niri to see if i can replicate it.
-
I'm not familiar with Bazzite. Did you get those drivers from Nvidia's website? That's my only issue with Debian 13 right now. Everything else is working as expected. Also the reason I had to get the drivers from the website is somehow I couldn't enable some stuff (like amd-pstate) on the default Bookworm kernel and had to use a backported one.
I'd definitely recommend against using drivers downloaded from a website, on general principles.
custom kernels don't work with the drivers from apt
Check if there's a dkms version - I know that's the way it's set up on Arch, if using a non-standard kernel you install the kernel headers, and dkms lets you build just the module for your kernel.
-
I thought "Meta" was AltGr and Super is the "windows key".
I never heard of AltGr reffered to as "Meta", except maybe in the sense of "Emacs modifier" which might be bound to it. Super is definitely the key between LCTL and LALT though
-
I have a shitload of bug/weird behavior with Wayland, I hope it gets better but for me it is not there yet.
Like what? (Curious)
-
I make perfect sense to people who actually read what I said. PipeWire issues aren’t imaginary.
I understood you and had the same issue. I solved it by using an Apple USBC to mini jack audio device instead of onboard. Not ideal. Not sure if it’s still a problem though
-
Exactly my point. The issues people consider ”solved” with wayland today will be solved in production in 3-5 years.
People are still running RHEL 7, and Wayland in RHEL 9 isn’t that polished. In 4-5 years when RHEL 10 lands, it might start to be usable. Oh right, then we need another few years for vendors to port garbage software that’s absolutely mission critical and barely works on Xorg, sure as fuck won’t work in xwayland. I’m betting several large RHEL-clients will either remain on RHEL8 far past EOL or just switch to alternative distros.
Basically, Xorg might be dead, but in some (paying commercial) contexts, Wayland won’t be a viable option within the next 5-10 years.
Well, we're currently in the process of porting apps away from Windows Server 2012 and CentOS 7.
What you're describing is just how the industry works, not specific to Wayland.
