I’ve been on Wayland for the past two years exclusively (Nvidia).
I thought it was okay for the most part but then I had to switch to an X session recently. The experience felt about the same. Out of curiosity, I played a couple of games and realized they worked much better. Steam doesn’t go nuts either.
Made me think maybe people aren’t actually adopting it that aggressively despite the constant coverage in the community. And that maybe I should just go back.
deleted by creator
I tried for a bit and it was great, no complaints. However, I was having issues getting NixOS set up as quickly as I would like, so I went back to Pop!_OS. I’m looking forward to the next release of Pop, which will have full Wayland by default.
I’ve been running wayland on popOS for a year now. Works great. It’s already installed, you just have to into a file and either delete a line or change false to true. Takes about 2 minutes.
I have used it for almost 3 years, no serious issues here.
Mid 2022, when i swapped my nvidia card to an AMD one. Instantly switched to Wayland (KDE Plasma) and stayed there.
I’ve been using Hyprland for about 2 years. I did have some issues with screen sharing (teams, discord) and some steam games (non native, with proton) need some extra launch parameters, but they all work now. Over time I was able to fix all the little issues. For me Hyprland is a daily driver, but I like to tinker. I can see how this is not for everyone.
May I ask how you solved the screen sharing problems? Also do you use keybinds for apps such as discord? When I tried Hyprland none of them were working.
Hey, sorry for the late reply.
I remember installing
xdg-desktop-portal-hyprlandinstead ofxdg-desktop-portal, and in myhyprlandconfig I have:exec-once = dbus-update-activation-environment --systemd WAYLAND_DISPLAY XDG_CURRENT_DESKTOP exec-once = systemctl --user import-environment WAYLAND_DISPLAY XDG_CURRENT_DESKTOPI can’t remember everything I tried… I didn’t keep track. I’ve been using this setup for close to 3 years now…
I know that for Ferdium I used the extra params
--ozone-platform=wayland --enable-features=UseOzonePlatform, but I think it doesn’t need them anymore (I use it for Teams and other chat apps with screensharing).For Discord I use Webcord, which works just fine, also with screen sharing, I didn’t have to do anything.
When it comes to key bindings, here’s my working setup:
# binds $mainMod = SUPER $lock = playerctl --player=mpd,firefox,mpv -a pause ; ~/.config/hypr/scripts/swaylock bind = $mainMod, Q, killactive, bind = $mainMod SHIFT, Q, exit, bind = $mainMod, X, exec, $lock # lock bind = $mainMod, RETURN, exec, alacritty bind = $mainMod SHIFT, RETURN, exec, alacritty -t scratchpad --class scratchpad bind = $mainMod, E, exec, nemo bind = $mainMod, W, exec, firefox bind = $mainMod, R, exec, rofi -show drun --allow-images bind = $mainMod SHIFT, E, exec, wofi-emoji bind = $mainMod, P, pseudo, # dwindle bind = $mainMod SHIFT, Space, togglefloating, bind = $mainMod, F, fullscreen, 1 # maximize window bind = $mainMod SHIFT, F, fullscreen, 0 # fullscreen bind = $mainMod, S, exec, grim -g "$(slurp)" - | wl-copy # screenshot selection to clipboard bind = $mainMod SHIFT, S, exec, grim -g "$(slurp)" - | swappy -f - # screenshot selection and open in swappy bind = $mainMod SHIFT, R, exec, wf-recorder -a -g "$(slurp)" -f "${HOME}/$(date +%Y-%m-%d_%H-%m-%s).mkv" -c h264_vaapi -d /dev/dri/renderD128 &>/dev/null # screenrecord bind = ,XF86AudioMute, exec, pactl set-sink-mute @DEFAULT_SINK@ toggle binde = ,XF86AudioLowerVolume, exec, pactl set-sink-volume @DEFAULT_SINK@ -2% binde = ,XF86AudioRaiseVolume, exec, pactl set-sink-volume @DEFAULT_SINK@ +2% bind = ,XF86AudioMicMute, exec, pactl set-source-mute @DEFAULT_SOURCE@ toggle binde = ,XF86MonBrightnessUp, exec, light -A 5 binde = ,XF86MonBrightnessDown, exec, light -U 5 # resize windows binde = $mainMod, left, resizeactive, -40 0 binde = $mainMod, right, resizeactive, 40 0 binde = $mainMod, up, resizeactive, 0 -40 binde = $mainMod, down, resizeactive, 0 40 # move focus bind = $mainMod, h, movefocus, l bind = $mainMod, l, movefocus, r bind = $mainMod, k, movefocus, u bind = $mainMod, j, movefocus, d # move windows bind = $mainMod SHIFT, h, movewindow, l bind = $mainMod SHIFT, l, movewindow, r bind = $mainMod SHIFT, k, movewindow, u bind = $mainMod SHIFT, j, movewindow, d # switch workspaces bind = $mainMod, 1, workspace, 1 bind = $mainMod, 2, workspace, 2 bind = $mainMod, 3, workspace, 3 bind = $mainMod, 4, workspace, 4 bind = $mainMod, 5, workspace, 5 bind = $mainMod, 6, workspace, 6 bind = $mainMod, 7, workspace, 7 bind = $mainMod, 8, workspace, 8 bind = $mainMod, 9, workspace, 9 bind = $mainMod, 0, workspace, 10 # move windows to workspace without switching (silent) bind = $mainMod SHIFT, 1, movetoworkspacesilent, 1 bind = $mainMod SHIFT, 2, movetoworkspacesilent, 2 bind = $mainMod SHIFT, 3, movetoworkspacesilent, 3 bind = $mainMod SHIFT, 4, movetoworkspacesilent, 4 bind = $mainMod SHIFT, 5, movetoworkspacesilent, 5 bind = $mainMod SHIFT, 6, movetoworkspacesilent, 6 bind = $mainMod SHIFT, 7, movetoworkspacesilent, 7 bind = $mainMod SHIFT, 8, movetoworkspacesilent, 8 bind = $mainMod SHIFT, 9, movetoworkspacesilent, 9 bind = $mainMod SHIFT, 0, movetoworkspacesilent, 10 # move/resize windows with LMB/RMB bindm = $mainMod, mouse:272, movewindow bindm = $mainMod, mouse:273, resizewindow # scroll through existing workspaces bind = $mainMod, mouse_down, workspace, e+1 bind = $mainMod, mouse_up, workspace, e-1 # switch workspace with mouse back/fw buttons bind = $mainMod, mouse:276, workspace, m+1 bind = $mainMod, mouse:275, workspace, m-1 bind = $mainMod SHIFT,up,focusmonitor,u bind = $mainMod SHIFT,down,focusmonitor,d binde = $mainMod, TAB, workspace, previous
I switched my laptop to Wayland about three years ago. AMD graphics, normal DPI 60Hz screen, doesn’t really do more than run a web browser.
My gaming desktop needed more of those troublesome edge cases hammered out - freesync in xwayland, app DPI scaling in xwayland, etc. I only switched it last year.
Been daily driving sway for over 5 years now. There were a few problems along the way. I used to have JWM and then XFCE as a back up in case wayland fails. I really only need to go into them when there’s a need for screen sharing. But then, I mostly live in terminal and browser. Low graphic games I play seems okay. The most demanding one I played is probably Starcraft 2 and it plays well even on my crappy 7 years old laptop with intel graphics.
I used Wayland for a couple years on AMD hardware and it was fine; I didn’t really have any issues. Since acquiring a laptop with an Nvidia card as a gift about a year agi (it was a hand-me-down), I switched to X11 because it is still more stable for Nvidia. I will be switching back to Wayland (with Nvidia) when Fedora 40 releases. Hopefully the support for explicit sync patch will be available by that time, but if not I won’t be heavily affected, as I am not playing games currently. I expect that patch to fix the black frame insertion during VRR that people have been complaining about, at which point Nvidia will be viable (for me) on Wayland.
I’ve been on the Wayland train for quite some time now, it’s only really had issues with Nvidia because Nvidia refuses to adapt their graphics driver for it. We have to rely on the Wayland and XWayland projects to fix the incompatibilities that Nvidia is too lazy to fix themselves (like not supporting implicit sync). Luckily AMD is on top of things and has worked very well with Wayland for years now, so those with AMD hardware are better off.
EDIT: Here’s a link to a Lemmy post about the explicit sync patch. Looks like Nvidia drivers plan to support it in the May 15th patch, so about a month after Fedora 40 releases.
Probably like 3+ years on the laptop (Intel), approaching 1 year on the desktop (AMD).
Wayland + NVIDIA is still a disaster and a very inferior experience compared to the AMD side. I would stick with Xorg if I had NVIDIA too.
Only on Intel or AMD do you get a Wayland experience that makes you go “wow I can’t wait for Xorg to be dead for good”. I had a very, very noticeable improvement even years ago on Wayland when it comes to triple monitor performance, VRR and vsync in general. Now that screen capture and stuff is mostly figured out, it works perfectly for me.
At this point my only issues with Wayland are related to features that haven’t been implemented yet, not bugs or performance issues. And I’m more than willing to workaround the limitations and take the benefits.
I’ve been patiently following development and waiting to switch for 10 years, first exploring Wayland with the EGLStream patch for Weston on my GTX 580. Even back then you could feel the difference, but obviously it was also unusable other than demos.
When? Since Ubuntu made it the default for non Nvidia PCs
i’ll probably jump the next time i change window managers or distros… i havent a reason to currently
Yes. Since 2013 or so, if I remember correctly. Gnome 3.10.
No, I see no benefits
No.
When it’s a drop-in replacement for X.
Switched over to wayland about 4-5 years ago, have run into a couple of problems dealing with theming, fractional scaling and of course nvidia, but on the whole my experience has been without major issues.
