It is indirectly mentioned in Trello:
This list does not include all the issues related to Nvidia+Wayland or nvidia-drm.modeset=1. Those are tracked in a different list instead and are not planned for this cycle.
After a little checking it seems that the issue I’m referring to may solely be caused by the Ubuntu repo build of nvidia-driver-430 or how that build’s packages install.
(- So maybe I should un-dupe from it…
In a nutshell -
I purge nvidia* and autoremove the rest.
reboot
Add the graphics driver ppa, remove Ubuntu’s restricted repo, update sources
Install nvidia-driver-430 from the ppa, reboot.
All works fine
Both the repo and ppa have the apparently same 4.30.26 driver source, install the same 66 named packages, why different behaviour, don’t know.
It’s always possible multiple builds of the same source yield different results because of different environments. For that reason some projects uniquely identify each build separately to the software version.
Also, if this is a bug then please comment in a bug.
"We are looking forward to being able to move over to Wayland as soon as we can, and I think that [the release of] GNOME 4 could be the right time to do that.
TR: What release of Ubuntu would you forecast shipping Wayland as the default?
Cooke: I can tell you it won’t be for 20.04. We’re too close to the release now. We’re only one cycle away from the release. The cycle before the LTS release is a final fit-and-finish. We should be going into that cycle, which starts in October this year, with these decisions already made. So we haven’t got time, in six months, to debug and fully test a change to the display server.
In order to try and get it in for the next LTS—Ubuntu 22.04—we will be moving pretty quickly to get Wayland as the default again and shake the rest of the bugs out. So I think we’ll see it move in 20.10, and then we’ll have to see how that goes, and then we’ll make a decision from there. "
https://www.techrepublic.com/article/ubuntu-what-does-the-future-look-like-post-unity/
I’d be worried about waiting for GNOME 4. My understanding (although it may have changed) is that there is a chance that will support ONLY Wayland - no X11 support - except Xwayland compatibility for apps.
I didn’t intend to say that we’d wait for GNOME 4 before changing.
We’ll discuss again in 20.10 regardless of GNOME version.
That is already the case.
1 Like
At least Mark Shuttleworth wants to embrace Wayland early: https://www.markshuttleworth.com/archives/551/comment-page-61
Ten years after this confession Ubuntu remains the one distro to cripple Wayland deliberately by disabling the remote desktop support in the compositor. Maybe for security reasons but who knows. There is just an early review available by the security team. They cannot be bothered by stuff like that.
2 Likes
It’s fair to have different opinions but it’s not nice to be passive aggressive, it certainly doesn’t further your goal.
3 Likes
This is a rather basic feature that is quite broken in Wayland: tiling.
https://gitlab.gnome.org/GNOME/mutter/issues/620
It seems weird to me that it hasn’t got more attention, it’s really quite broken and it’s really rather basic.
1 Like
10 posts were split to a new topic: Wayland not working with NVIDIA
Folks, please flag support requests so this discussion thread can properly run it’s course.
Another annoying thing in Wayland right now is touchpad scrolling in Chromium. Chromium native Wayland support is not done, so it uses XWayland, and there’s a regression in Chromium so under XWayland it doesn’t use xinput2 like it does under Xorg which leads to the old mouse wheel emulation scrolling. (Reportly Fedora patches their Chromium package to revert this change.)
Chromium bug: https://bugs.chromium.org/p/chromium/issues/detail?id=712737
Ubuntu bug: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1811219
1 Like
With wayland blacklisting nvidia, nvidia hybrid(optimus) users can still avail themselves the option to have nvidia drivers installed and check out a wayland session if desired. Can be done in 2 ways after enabling nvidia kms
(- nvidia_drm modeset=1 in a mod.probe.d file or nvidia-drm.modeset=1 kernel parameter
- Switch to lightdm (probably the preferred dm for nvidia drivers.
2.Stay with gdm3 and edit or comment out the obvious line in /lib/udev/rules.d/61-gdm.rules
Then after reboot logging into a wayland session will use the Intel device even if the prime profile is set to nvidia.
1 Like
Thanks for pointing that out @mc3man.
The use of /lib/udev/rules.d/61-gdm.rules is an upstream design choice which I tried to avoid but lost. So if you want to enable Wayland for Nvidia you will need to comment out that line.
The reason why we don’t comment that line out by default (any more) is because doing so creates a bigger problem for many users. So edit at your own risk. At least we don’t need to carry any patches in that area now.
1 Like
Just wanted to say a brief thanks to the Ubuntu Desktop team for uploading a Synaptic package manager that works with Wayland! Woot!!
No more logging out of my Wayland session, just to run Synaptic. Appreciate it. 
1 Like
sudo synaptic
would have helped a lot. But yeah, it’s easier to just click at the icon 
I suspect it’s this upstream change in mutter 3.34 you have to thank for sudo support of Xwayland apps: https://gitlab.gnome.org/GNOME/mutter/commit/a8984a81c2e
That was Ubuntu bug 1652282.
3 Likes
Perhaps the wrong forum (old now) but just came across this topic via a search engine and imho thank god x-org and not Wayland is being used in 20.04. Did not have very good experiences with my nVidia card and doing “updates” which included kernel updates, would break my 18.04 every time! Ridiculous. Not impressed. Again, thanks to the guys from Timeshift!