Also see https://forums.linuxmint.com/viewtopic.php?p=2385186#p2385186
Nemo already supports Wayland thanks to the Fedora Cinnamon maintainer leigh123linux.
Also see https://forums.linuxmint.com/viewtopic.php?p=2385186#p2385186
Nemo already supports Wayland thanks to the Fedora Cinnamon maintainer leigh123linux.
This seems very shortsighted of the Linux Mint development team. XOrg is basically being held together with duct tape and barely even maintainable anymore. In fact, most former X11 and XOrg developers don’t want to anymore. The reason XOrg was “So stable” waas because it wasn’t changed very much since 2012; changing any core feature bascially broke many DEs. Wayland certainly isn’t perfect, but it’s all we’ve got right now. Unless the Linux Mint team wants to maintain XOrg by themselves and cut themselves off from the rest of the Linux world, they are going to need a solution for Wayland soon.
The main issue for me using Wayland on my desktop was Nvidia GPU support, but that has seemed to have vastly improved over the past year, and I’m currently using KDE Plasma on Wayland with almost no problems, and actually less problems than XOrg.
And afaik, KDE Plasma doesn’t have a timeline for removing XOrg support, but GNOME basically does.
Yep, that’s the only problem I have left. Now it seems to be happening only on Xorg and not Wayland. Funny how things have changed.
That’s quite an exaggeration of the situation.
Xorg shows every sign of being available in Ubuntu 24.04 LTS, which will be the next base of Linux Mint 22.x. What is less clear is whether this will be the same for Ubuntu 26.04 LTS, and Mint may need to have Cinnamon working with Wayland by then.
I’m happily using Wayland in my KDE Plasma installation. The remaining issues (for me & my hardware) are minor, and it should be marvellous in Plasma 6.
The wording on that doesn’t seem quite right. I though that kwin and mutter both predate wlroots. Saying they refused to integrate an entirely separate compositor into their existing compositor is just weird.
On another topic, is KWinFT even still going. I heard that a lot of the improvements they made were put back into upstream kwin, but after that it seemed to all go down hill. I heard the main developer was being sponsored by valve to work on it for a while, but then lost that funding. The main dev of KWinFT mentioned it in his blog here.
Seems like him, Valve and the rest of the kde team just had differing opinions on how things should be done which caused them all to go their own way. He also mentions at the end of that blog that he got a job in the industry working on audio products, so I imagine the scarce commits he has made over the last year are related to his new employment.
I just spent all of yesterday banging my head against the wall trying to get it to work at all. I have a desktop with an amd cpu 5800X and dedicated nvidia gpu rtx 3080. When I would login to the wayland session, everything would be black and one of my monitors had that 2005 trailing mouse effect. I created a new user (which I highly recommend) and saw that I was able to login to a wayland session no problem. I nuked the .config directory (not really I just renamed it), but from here I was able to login to the wayland session without the black screen and weird mouse effects.
It was honestly pretty smooth and a lot of thinks worked really well. I fired up risk of rain 2 through steam and it played just fine. I wasn’t having any issues with multiple monitors or screen tearing in the first place, so I’m one of those people in which the main benefits of wayland don’t really apply. Unfortunately this means that the experience felt like death by a thousand paper cuts. I have been keeping a list of my plasma wayland experience over the years. I’d tried to organize most of them by how I felt about them as well as whether it seemed like an nvidia issue or kde issue or something else.
Showstoppers
Nvidia settings app as well as others such as green with envy straight up do not work with wayland. You can’t so much as control the fan speed which you would think has nothing to do with the display protocol. [Nvidia]
Remote desktop apps don’t seem to support wayland. Mutter has Gnome remote desktop built in, but that doesn’t help anyone else. KDE is working on rdp integration though. Sunshine / Moonlight doesn’t work when no monitors plugged in on wayland, but does on X11. [Wayland / KDE]
On the Fence
Mouse gestures don’t work. (Not trackpad gestures, mouse gestures. This is because khotkeys is unmaintained and most functionality had been moved away over the years). [Wayland / KDE]
No virtual keyboard is as feature complete as onboard. The only supported virtual keyboard in the plasma wayland session is maliit which can’t be easily themed, resized, moved, does not contain function keys, etc. [Wayland / Lack of Apps]
Annoying
Mouse is inconsistent between native wayland, xwayland, sddm, and flatpak apps. As in work works fine for native wayland, xwayland is clipped at the bottom. (Not sure if this one still applies, I forgot to test for it) [Maybe KDE / GTK]
Too many apps that have wayland support still launch in xwayland. There are work arounds though. This mostly effects electron and chromium apps, but there are config files you can create.[Electron / Chromium / JAVA]
Java, old electron, wine, xwayland apps can have weird scaling issues.[Apps that may never be compatible with wayland]
Apps still seem to be weird in various places when it comes to showing their icon. [KDE / Wayland]
Dragging a window by its title bar inappropriately resizes the window. (Solved this by nuking the .local folder. More specifically I believe it was the kscreen folder that needed to be deleted) [KDE]
Native wayland gtk apps that export their menu’s don’t work with global menu on wayland. XWayland apps work just fine. (This bug here: https://bugs.kde.org/show_bug.cgi?id=424485) (Seems to need work on the Plasma and GTK side. Not sure how that will go if it depends on anything from Gnome) [KDE / GTK]
Various weird graphical glitches probably related to nvidia. Weird trailing effect in blurred windows. Various shadows and outlines around the cursor or panel that don’t show up on X11. [KDE / Nvidia]
Massive memory leak in spectacle screen recording. (This bug here: https://bugs.kde.org/show_bug.cgi?id=469005) [KDE]
With multiple monitors. A copy of the mouse will sometimes get left behind on the other display. It works correctly if you slowly move the mouse from one screen to another, but not if you do it quickly. [KDE / Nvidia]
Yeah, so things under show stoppers
are things I can’t move to plasma wayland without.
The things under on the fence
are things that I really don’t want to leave X11 without, but I could do so if necessary.
Lastly, there is a long list of annoyances that don’t really effect anything, but are just, well ya know, annoying!
Hope this helps for other plasma + wayland + nvidia users.
After almost 3 weeks, the panel image froze again… Needed to log out and back in to fix the panel.
That’s Nvidia for you. I don’t control the fan speed, but I heard GreenWithEnvy is unmaitained atm, so IDK if that’s why.
I managed to get a work around for Sunshine / Moonlight to work on Wayland atm. I haven’t tested it super thoroughly yet though.
Sorry about your issues; I hope they get fixed soon!
It not just greenwithenvy though. Even the official nvidia settings app doesn’t do anything on Wayland, but yeah thats Nvidia.
I would be interested in what you have come up with. I would like to be able to keep streaming the desktop even when the monitors are off. In order to do that I need either RDP or sunshine + moonlight if I want to be able to do it in a usable fashion.
I bet if someone ones will do such titanic job as writing a proper documentation for X11 with many example in a style like a Go’s official documentation.
There will be rapidly increase of the interest in X11.
As the main complain about X11 from the developers side I heard and encountered myself - decades of the complex, complicated code with a terrible documentation and very few educational materials and examples.
personal idea is code get more complexer overtime this was with x11 but with wayland also will be. is like you studied gasoline car in in the 50’s, and step backintoo the car business in 2023 its a world of difference
and as electrical like the new wayland is another concept to start with until it evolves further
Wayland by default
We’re going to make a very strong push for Wayland to be the default session type for Plasma 6. The X11 session will still be there of course, and distros will be free to override this and continue defaulting to X11 if they feel like it suits them better. But we want Wayland to be our official recommendation.
To get there, we went over our “Wayland showstoppers” wiki page with a fine-toothed comb to refine what we really consider a showstopper. We decided that a lot of them are really more like annoyances rather than showstoppers, because X11 has plenty of annoyances of a similar severity too! The true showstoppers are down to five, plus a couple of NVIDIA issues that need further investigation. Many of these issues are in progress with a clear path towards resolution, so I do expect us to be able to achieve the goal!
I’v read at some latest posts in Adventures that they basically won’t really spend any time on fixing bugs related to X11 KDE code…So it’s double-edged misunderstanding.
They’ll basically freeze anything related, as far as i understood.
but seems that this is now the new reality around Xorg… it will not get much new feature development and will be fix issue state basically ?
No, what KDE means - KDE code related to X11 (like kwin_x11
)…Which generates crapload of bugs even now, it’s far from being perfect already…
Self-fulfilling prophecy
That’s the plan…
Hurray! lets let die off X11 xorg… by simply forcing wayland!
Nah they should go to hell until i see screensavers in Wayland - i’ll use dwm
or TTY!
yes my plan also i will go all TTY… get rid of X all together
only mentioned the article as users start posting that kde will drop X11 session in plasma 6 (also it may technically is partly true depending on your opinion
nox / now - become the resistance!
https://lock.cmpxchg8b.com/spreadsheet.html
even spreadsheets…