Wayland all the way, 120 hz Freesync monitor with 60 hz second monitor works perfectly on KDE Plasma with AMD. No fussing about with X11 configs or worrying about if the compositor is active or not, it just works.
I can't seem to get Freesync working on KDE Wayland with a single monitor (NixOS with an AMD R9 380). Any tips? I'm using vrrTest to test, and my TV reports when Freesync is enabled.
I'm not having any issue in XFCE on x11/xorg with a 164Hz main screen @2560x1400, and a 60Hz second screen set vertically @1080x1920. Just using the display manager config provided by XFCE.
I use arch btw. My distro doesn't give me anything. I was on x11. Wanted to experiment a bit and now I'm configuring hyprland. Going well for me so far
Wayland is the future. X11's future is dead. Unfortunately there are still some growing pains. Xwayland mostly works but I have issues with it sometimes.
If you don't know install a distro and use what comes with it by default and only worry about digging into the plumbing if something doesn't work for you.
Ideally you let your distro worry about plumbing.
I think Mint is nice if you don't need bleeding edge stuff. You can use Cinnamon which runs x11 but will eventually support Wayland.
I've heard good things about suse which has a rolling release option and supports gnome and KDE under Wayland.
Arch of course is a thing if you don't mind a manual transmission as it were.
Honestly, I have no clue. With DWM I had like 3-4 hrs at max and now I am using DWL for 6-8 hrs.
What is also noticeable, is that closing the lid puts the laptop actually into sleep. Because with DWM it continued using the battery as if it was actually used.
I am not advanced user enough to tell what exactly caused this.
Wayland, because it's faster, more stable, handles multi-monitor better, you can have animations while playing a game, no tearing, no fcking around window managers/compositors or shit, lower memory usage and 1:1 touchpad gestures
you have the same with X11... i have all these feats with my intel and AMD GPU.
So why Wayland then? Better architecture/codebase and more manpower.
And I think it supports multi-gpu better, not sure as nvidia doesn't play well with Wayland, it would be astonish that Optimus works any better.
Try running multiple monitors with different resolutions or gaming... Just in general (no seriously, people who think that gaming on X11 is better than wayland are fcking insane... No tearing, having to disable compositor to get more than 20fps, just works) in X, bet you'll have a great time.
And yes, Nvidia is the only reason why imo anyone should still be using X (if they don't wanna use gnome)
Wayland. Because it's X12. Not a spiritual successor to X11, but an implementation of a subset of X12 by the X11 people. The fact that X11 even works for desktop is a miracle, and only possible due to everyone deploying ass-backwards workarounds to make it work. Now the only changes to Xorg are related to Xwayland.
Both have issues, just that X11 has old issues that rarely someone is workin on, while Wayland has new ones and people are fixing them. So Wayland for me, thank you.
Wayland first, but have both installed so you can fall back to X11 if you need to. If you do have to go back check wayland again after every few updates. X is dying a long-needed death. It started off has a hack decades ago and has just been held together with duct tape ever since. There are some not so great things in wayland with some apps, sometimes issues with context menus or screen recording for example, but they’re getting fixed over time.
I do kind of miss x forwarding over SSH. It was really convenient, there might be something for wayland but I haven’t looked for a while.
I found that Wayland works better in my case: XPS 17 with Nvidia on Ubuntu lts. Less stuttering and overall smoother feeling. The only issue is that the screen doesn't always turns on after suspend, but this is healed with ctrl+f1.
I don't think that's a feature many people actually needed, something like accessability is peobably a better argument but I agree with the fundamental statment
Agree, network transparency is a super power user feature.
And frankly VNC is good enough.
I just found it sad that a really powerful feature was dismissed as "no-one actually wants this" (yes I do) and "just use VNC" (I shouldn't have to) and "just plug a monitor in" (well yeah).
I would have hoped that is have been a protocol extension or something rather than outright dismissed as "doing it wrong".
Don’t tell me I don’t need it, I use it every day to run apps not yet available on arm from another system. I’ve used it for years at work, as well. Just because it’s for something other than fricking gamer’s doesn’t mean it is not needed.
Wayland. It generally works a bit better at this point, and it will only continue improving while X11 falls behind. I occasionally need to switch back to X.org for some legacy screen-casting or remote desktop apps, but even the ones that support Linux as an afterthought are starting to add beta Wayland support.
Wayland, especially with a laptop and/or a multi-monitor setup. It has a proper touchpad support with 1:1 gestures and setting different scaling factors for multiple monitors with different refresh rates is a breeze.
And don't forget Crash-Resilient Wayland Compositing that keep applications alive even tho the "compositor" crash, so it does restart without any data loss and the lockscreen protocol, because on xorg if the lockscreen crash then you view the desktop and you have the device unlocked!
Good point. But I think it would be difficult to configure this bundle within GNOME/KDE. And it's not necessary. Almost everything works fine under Wayland right now.
I run a dual monitor on X11 and never understood why people have issues with it? I'm by no means a Linux expert and I do run in Nvidia, I run different refresh rates. Can someone explain it to me?
I do similar. For laptops and docks, especially if they change setups it can be a pita (though you just need to copy files around).
Also the DE monitor config (ie that you use to login) is logically different to a users x config. So you gotta copy that over to make sure the primary monitor etc is right.
Wayland, because anything I want to do is possible with wlroots compositors like sway. And if you don't need a feature not yet implemented in wayland (e.g. screen tearing), wayland is usually the better experience.
Obviously switching from X11 to a standalone Wayland compositor like sway involves changing out some apps, it's a core component of your system afterall. But xrandr has it's wayland alternatives, rofi has lbonn's fork with wayland support, dmenu has it's equivalent, etc. The X11 tools might work, but usually aren't as good of a experience (e.g. rofi X11 might stay in the foreground while not being able to react to keypresses, rofi-wayland fixes this.).
And I really like to try new things and be at the edge off new technology, so I really wanted to use wayland (And have been using it for years at this point).
Xorg on my desktop. kwin-wayland still has many problems for me, from major things like windows vanishing and screen flickering with my Nvidia card to minor but annoying things like a random system tray pop-up popping up after clearing notifications. Also the force blur kwin script is not working under wayland.
Wayland on my Intel only laptop because it mostly works (apart from the pop-ups)
For most users, it doesn't matter. Just go with whatever your preferred DE uses. I love Hyprland, which uses Wayland, so I use that. I also like bspwm, so I would also use Xorg for that.
Wayland has a few issues still. I have issues with zoom lately, for example. Share screen also has trouble sometimes.
I honestly just stick with X11 because of the high degree of compatibility, and I often already rely on X11-only software anyways like Redshift (I know there's Wayland-supporting alternatives, but I'm picky and don't like switching if I don't feel I need to), also my DE/WM of choice is currently awesomewm and I think I've heard mixed things about using awesomewm on Wayland (or it might not even be compatible at all. I just woke up and I'm struggling to remember lol)
I am not a user of ether one but technically speaking X11 simply has a ton of legacy code to a point of questionable maintainability which is why Wayland exists in the first place
Same here; I'll switch whenever Xfce does. Which, by the way, will probably happen sooner than expected, by the time 4.20 comes out. All the core apps & the development version of the panel already work on Wayland.
Unless you are on NVidia or need X11 specific things (E.g. a lot of the accessability stuff) I would go for Wayland, it still has some issues but so dose X11 and Wayland is simply the new display server from the xorg foundation because X11 was impossible to properly update by now, it has far too much lagacy code and didn't get any new version in ages for that reason.
X11 because Discord is unusable for me on Wayland, and I use it every day.
Edit: I recently switched to a 7800 XT (was using a 3080), and the discord problem was either solved since the last time I tried it, or not being on nvidia helps - no more weird input lag etc. in discord, so I've moved over to Wayland finally.
Either way is fine usually. If you really care about 1:1 trackpad gestures like I do, get Wayland. If you have an nvidia card, get x11. Otherwise it’s probably not something most people will even notice.
When performing a gesture, the animation on screen matches up to the motion of your fingers. Stopping moving your fingers halfway will stop the animation halfway, and moving slowly will slow the animation.
Both of them have issues depending on the setup. X11 has worked flawlessly in my experience. Wayland has worked the same for most.
Personally, Wayland still has some growing pains, especially in regards to Input handling (mouse, keyboard, etc). In X11 it was "trivial" to edit one file and have the settings stick across different WMs (switching from DWM to i3, etc.) There's no standard for this with Wayland since it's up to the compositor to handle these things, meaning you're relearning how to do something as basic as setting pointer speed each time you try a new compositor. This is my only real fair gripe about it currently, as the rest of my complaints are just due to how young a lot of the Wayland-specific tools are - this will improve with time.
Hyprland has an option of forwarding any hotkey to an application, essentially allowing for global hotkeys in all apps, including Discord for which it doesn't work normally.
X11 because KDE cut some features for Wayland (some that will be cut in Plasma 6 X11 too, yay) and some apps just don't support wayland for technical reasons.
Linux gaming has come to the point where many publishers and developers literally add Wine support intentionally and the game consol with the biggest game library of all time (Steam Deck) uses it but we still have people like you... If you want to use Windows you are free to do so but Linux is a great option by now too!
X11 for xdotool. ydotool doesn't support (& can't really support with it's current architecture) retrieving information like the current mouse location, current window, window dimensions & titles. Also, normal (unprivileged) user ydotool use requires udev rules or session scripts and/or running a ydotool daemon & many distros don't yet ship with this Just Working.
X11 for Alt-F2 r to restart Gnome Shell without ending the whole session. This is a useful workaround for a variety of Gnome bugs.
Honestly, I never heard of it before, so I checked to see what it is. I wrote a pretty neat config for my i3wm and to this day am so comfortable with it that I would never change it.
From my understanding after a look, it is pretty much i3wm for Wayland. If my config works well with it, I might give it a shot.
Whichever works best for you. I would recommend Wayland to anyone, but if you run into any problems with it (either bugs with your compositor or protocol limitations), then just use X11.
I use xpra which lets me run persistent seamless windows from my VMs and remote servers. It would probably work okay with xwayland but i might as well keep using X. I understand why people use Wayland though and would recommend it to newcomers.
I've been using Wayland with Nvidia 1080 on one machine, and with 3080 on another for a year. Most of the time it is pretty fine. The issues happens with some applications (mostly written on Java, ocasionaly). But slowly the situation getting much better than earlier.
It dose work with NVidia GPUs too but propriatary software adopts slower to new technologies so the cards with propriatary drivers naturally have more issues and that's sadly still the case in a direct comparison but it's getting better fast
X11, because I haven't figured out how to get Wayland to work with my Nvidia 1070. One day I'll put in the effort, or finally upgrade my card. But for now it's fine