Recently installed the latest Zorin release as I kinda just want to get stuff done instead of updating Arch every day. That backfired and now my main display freezes about a minute after my desktop loads using Wayland. X11 GNOME sessions appear to work fine (as fine as X11 can be).
Tried like 10 different driver versions, currently on 560. I have DRM KMS enabled, I have PreserveVideoMemoryAllocations enabled.
Nvidia GTX 1060 6GB
Ryzen 5 2600
Zorin OS 17.2 (Based on Ubuntu 24.04 I believe?)
I am entirely out of ideas on what this could be and I've never experienced it on any other distro. I'm reluctant to distrohop again because I've loved everything else about this release.
Arch is cutting edge and yes, it will need frequent updates due to that.
Zorin OS is built to be stable - reliably working on most user components.
I, personally, have witnessed this to a large degree across a very wide range of distros except for those which are cutting edge rolling releases.
This likely is due to the latest releases having the most direct patches toward getting Nvidia and Wayland to play nicely with eachother, though in reality, it's not related to fixing Wayland - it is patching Xwayland. This utilizes X11 for things that need it.
What this means is that it is actually X11 on which things are working with Wayland kept in the background.
If you wish to use Zorin OS, I would recommend reverting to X11 to avoid the Xwayland fiasco.
I highly recommend avoiding the 560 driver from Nvidia at this time.
I've been daily driving Wayland on other distributions for over a year now and never experienced these issues. Generally I find Wayland to be a much better desktop experience when not having these issues, especially with my display setup.
I don't at all want to sound rude but I came here with the intention of fixing a Wayland configuration problem, if I wanted to use X11 I would already be doing so.
As far as this issue goes, I've used these same versions of GNOME and Nvidia drivers (535 - 560) on other distributions for months and never once encountered this specific problem. Is there any configurations Zorin makes by default that could affect it?
It does not sound rude to me, at all. It makes sense.
You have a goal in mind and it is that which you wish solved.
Sadly, this is not something we can point you toward a configuration file and neatly fix.
And a lot of this comes down to a long chain of changes in GnuLinux that have been happening for a decade that were not resisted strongly enough.
Asking for your patience; I will outline it as centered and swiftly as I can:
GnuLinux experienced the introduction of SystemD which integrates components. This means that users have much greater difficulty managing package dependencies.
How this relates to you: You cannot easily grab necessary patches from the repositories of rolling releases and move them to Zorin OS due to these integrated dependencies, like Glibc.
Wayland has been getting strong support from IBM and other Linux funding enterprises. The result of this was that Wayland, which has sat in development and limbo for over a decade (pretty much hitting one stall after another due to its designed implementation) was forced to the top priority. And... the tricky part is that what is broken cannot be fixed - not with how the fundamental foundation of Wayland is built. The only way to get it working was to patch it with XWayland, which actually uses X11 protocol, not Wayland, allowing applications and processes to run properly, keeping Wayland in the background and only utilized for processes and applications that do work on it. So you end up with a mix of X11 and Wayland both running. Which... utterly defeats the intended purpose of Wayland to cut out the middle man. Now, you have Two middle men. -shrug-
What this means for you: Unless you can patch XWayland, which see abvoe in regards to dependency issues; it means we are resigned to either digging deep into the code as individuals and essentially building our own distro or using a distro that has support patched in by teams of developers.
Or... using X11. You have actually been using it anyway for a lot of processes, without knowing that you were. So, it might not be so bad.
I realize this is not what you were seeking. I cannot fix that... I can only hope that this encourages you to take away from this a renewed sense of staying vocal in your GnuLinux communities, providing feedback and bug reports to developers and generally supporting User Aligned interests for the GnuLinux Desktop to help mitigate complexities like this one.
No there are not. Many users can have trouble with certain Nvidia drivers or certain kernels. I had no trouble with the 560 when testing it, but a large number of our users did.
These reports have weight, even if not everyone is affected by the bug report.
Can I ask what Distro's that were? Because there is a Thing with Nvidia and Wayland: Explicit Sync. This should make the Nvidia Experience on Wayland better. But You need Explicit Sync in the Nvidia Driver (from 555 on) and in the DE (on Gnome it is from 46.1 and on Plasma from 6.1).
Zorin runs with Gnome 43. So, you can't use this Process. And so, it would be better when You use X11/Xorg on Zorin because the Progess hasn't arrived Zorin yet. It is a LTS Distro. And on these Progress needs Time.
That could actually have something to do with it. I've mainly been using Arch based distros running GNOME 46/47 recently which may have made a difference. Though I do remember Wayland working perfectly fine under Ubuntu 22.04 using whichever drivers were latest at the time (525 or 535 possibly?). Just found it strange how suddenly my displays are freezing which I've never encountered on any distro or version before
I found wayland on my Solus Distro on Plasma 6 like wading through treacle. Extremely laggy and I had trouble doing anything like switching back to x11. There is a bug open about it on KDE.
Well, that would explain it. These are cutting Edge.
Did you changed it on Ubuntu active to Wayland or did You used the default Configuration? I'm not entirely sure but maybe Ubuntu 22.04 runs by default on X11 when using a Nvidia Card. As far as I know, they want change Wayland as default for Nvidia with Version 24.10.
Well, when Your Nvidia Setup with this drivers work on Ubuntu 22.04 in Wayland without Problems ... I think, you had Luck with the Ghost in the Machine I guess. And You really used Ubuntu 22 and not 24, yes?
Okay ... Well, I can't say why or how, but when it worked well, You are a lucky Man or Woman I guess. Maybe Your specific Hardware Combination plus Driver's was fitting well. Maybe You should try it in the Lottery, hahaha!
This gets complicated very quickly.
The connection between monitor and system matters. Differences in cables can having shocking results.
What applications are run - and how they are run matters.
What colors (I kid you not) are used in styling matters. (Some colors take more effort to draw than others).
