I run proprietary Nvidia drivers as well and Wayland runs so much better than Xorg now that I’m permanently coming over to Wayland. I’m extremely happy rn with Wayland
I had nothing but issues running Wayland with Nvidia. How strange.
That’s because the drivers are bullshit but not the problem in general. They work well for some very specific cards, not at all for other and in general it’s just random hit or miss.
And then, to make it more fun, not all wayland compositors are born equal either.
Any recommendations? Or knowledge of which cards work best with it? I’m thinking on trying it out again, never tried it on my 3070
The best decision I made was buying an amd card. Drivers are baked into the kernel didn’t have to install shit. Works flawlessly
Oh and I used a 3070 with nobara and had tons of issues. I had less with pop os
Not to be flippant about it, but I just recommend trying it and seeing how it works for you. You can have both Xorg and Wayland installed, you just change out which one you’re using at the login window
Thanks! I may be capable but not necessarily knowledgeable, I had no idea that was an option lol
I thought they’d use the same code as windows to interface the card and the issue was with exposing that in a linux-compatible way?
I keep trying Wayland and an in the middle of an attempt. I use fedora maniacally updated, Nvidia, and plasma shell. I’m about to abort again:
-even configured to directly use Wayland, I see chrome based browsers glitch out on occasion, and when it starts glitching it just keeps on glitching
-plasma panel stops updating multiple times a day, staying frozen including the clock
-sometimes kwin starts, but plasmashell has to run manually, and per above has to be restarted on occasion
-occasionally it just forgets what the monitor resolution is supposed to be and reverts to 1024x768
-the blur translucency effect glitches around mouse cursor
-immersedvr doesn’t support Wayland
On the flip side, xorg problems are: -occasionally kwin can’t grab keyboard for some effects until restarted. This is a well documented bug butt other than it being xorg specific, doesn’t seem to be figured out.
-some things tear in ugly ways, but not nearly as bad as the chrome glitch under Wayland.
Maybe kwin isn’t a great Wayland compositor, maybe Nvidia drivers are still not up to snuff. Ultimately, it’s not viable for me. Further kwin is a huge factor for “why Linux desktop” for me, gnome shell is more limited even than Windows for my workflows.
Definitely think NVidia has got some ways to go on improving Wayland drivers. AMD has its share of issues but they’re a lot less obtrusive than what you’re describing
I had those same issues on my 3080. I switched to AMD and Kwin works great on Wayland.
I wonder. Does KWin still use the old workaround for Nvidia?
I remember gnome refusing to bend to Nvidia over eglstreams.
If Kwin is still using that workaround, even now after Nvidia conceded, maybe that is the problem.
Hyprland nvidia here, running without and issues so far for about a month
I need nightlight mode so x11 until then
The new version of plasma coming out on the 28th has this fixed on wayland. We’re currently on rc2, but fill release will be soon. It may be a bit before your distro has it available however so you’ll have to use a PPA on debian/ubuntu/etc., install manually once it’s available, or compile from source if you’de like it now
deleted by creator
I use i3 and kde on void with an amd gpu, i tried kde wayland and sway (and i check on them every few weeks), but I’ve found them to be buggy and sway in particular to be very difficult. I honestly have no idea why it’s been like this for me, i look forward to the day wayland is truly as good as x11
deleted by creator
For me the switch was simple the only issue I do encounter from time to time is lockscreen related. What’s not working for you?
Prolly the biggest thing is sometimes when i launch sway dmenu completely fails to work, and then on kde there’s little bugs that show up, one that comes to mind is the bar at the top of windows that has the max min and close buttons rendered completely transparent
Maybe you’d have better luck with rofi… There’s also wofi. can’t say much about the kde issues though.
KDE and Wayland works perfectly, at least if you are on 5.27 or even Plasma 6 beta.
On a microsoft surface, just switched back to X11 from Wayland. Multiple applications segfaulting that run fine under X11. Mode switching in kde is miserable under Wayland with it being completely random as to how the resizing is applied if it doesn’t just crash the DE… Works perfectly under X11. Weird power state switching under Wayland causing background tasks to fail. Again works fine under X11.
using terminal can be productive.
I use i3 on a thinkpad p50 with hybrid graphics (Intel + nvidia). Works sort of stable if I force the use of the dedicated card, but I’m getting like 1,5h of battery.
Video acceleration seems to work most of the times, but for a few weeks I have problems with picom freezing my screen, capping fps in games and video. Any ideas? It took me hours to have it running sort of smooth, so I’m hesitant to try out sway and ruin my daily setup
Why are you forcing i3 to use the dedicated GPU?
AFAIK sway doesn’t work with proprietary Nvidia drivers
I’d love to run hybrid graphics with free drivers, don’t get me wrong.
I also love running steam games and video acceleration and with my previous setup it was mostly unstable. My current setup just works, with minor effects like reduced battery times and picom bugs.
I’m just trying to learn the reasoning behind your decision. I ran i3 on multiple devices, the newest one being a t480, and never had any issues with the integrated graphics.
Are you also forcing picom to use the dedicated GPU?
Seems like a waste, unless you’re playing one of those games that runs better on the integrated than on the dedicated.
My setup is 4k on two displays. The Intel GPU can’t handle them on 60Hz I guess. There is a thinkpad dock involved as well, so I think I’m stuck with HDMI and the dedicated gpu. I tried a lot of things :/
My setup is 4k on two displays
on a 9 year old laptop, and you even game on it, God damn dude!
I3 shouldn’t really be impacted AFAIK, but I’d drop picom completely just to save some cycles. It’s not like you have resources to spare on aesthetics.
I like transparent terminals and vsync. That’s my only reason for picom
I too am at nvidia wayland. have fun
I can recommend a hybrid setup. That works well with Wayland as long as you set that one kernel parameter. Otherwise the two GPUs won’t be in sync and you get glitches when using the dedicated one.
Wayland is not ready yet. I’ll wait till its done before jumping over.
I’ll switch when xfce fully supports it, by that time it should be ready.
(this is not meant as a slight against xfce in any way, I appreciate their focus on rock-solid stability)
True but I felt like it’s better to jump now so that I don’t feel bad leaving my wm. If your work/necessary apps do not work properly on Wayland it’s understandable. For me it’s fine. And hyprland is the best wm I’ve used till now.
I waited for so long to buy an external trackpad for my desktop, Wayland on Nvidia is basically what was preventing me from getting it. After about a month or two of stability testing, it’s really great now, so since yesterday I can finally enjoy all the GNOME gestures that I enjoyed for so long on my laptop on my desktop as well!!
what driver and os?
mesa, fedora 39, its been doing this since fedora 36 or 37 whenever I got the laptop a year ago. I didnt try since a few months, but I didnt see any changeglogs mentionning it so I guess its not been adressed (especially since the issue is still open on the amdgpu gitlab)
Are you using the new 550 drivers? They are supposed to include lots of wayland related fixes. I might try it myself once they update it on the arch repo. Last time I tried, my 2060 and 525 drivers just did not go with wayland, at all.
545 right now and the only issues I have is kde panels crashing and horrible screen tearing in games because of my gsync only monitor. I xorg has a toggle for gsync but can’t work around that damn monitor on Wayland for some reason.
deleted by creator
Games are not happy on XWayland when there’s a gsync only monitor at play.
my ONLY gripe with wayland rn is the lack of global hotkey support, which currently breaks Discord/other’s “push to talk” feature unless you install a webserver to control your mic via your compositor’s hotkey system and HTML requests 😭
I suppose push to talk can and should be owned by the desktop and not any particular app, but Id like an interim protocol until then
global discord hotkeys work for me on sway and hyprland for the most part
They must implement their own workaround/protocol for this. On KDE 5 it’s still missing. Hopefully they have something cookin for KDE 6 but since it wouldnt be standards-compliant there’s no guarantee
