[nvidia] Fail to launch gnome-shell (Wayland) on Ubuntu with EGLDevice backend

The bigger problem (than any missing commits) is that Ubuntu builds of mutter don't support EGLStreams:

mutter-3.30.1

 prefix: /usr/local
 source code location: .
 compiler: gcc

 Startup notification: yes
 libcanberra: yes
 libwacom: yes
 gudev yes
 Introspection: yes
 Session management: yes
 Wayland: yes
 Wayland EGLStream: no <----------
 Native (KMS) backend: yes
 EGLDevice: yes
 Remote desktop: no

I think the missing build-dep isn't even in main. I can only find it in https://github.com/NVIDIA/egl-wayland but would love to be proven wrong.

This is a problem on Ubuntu even when building upstream mutter with the "missing" commits. The required file wayland-eglstream-protocols.pc and friends is still missing from the Ubuntu distro.

... so even when you do get EGLDevice working, you don't have EGLStreams and so will be stuck with software rendering.

I think on aarch64 mutter is compiled with EGLDevice backend enabled. I have opened this bug NVIDIA Tegra SoC.

Yes, Ubuntu builds with EGLDevice support always enabled. But you can't explicitly select the "Wayland EGLStream" option - that's automatically detected.

Okay. Looks like this is the case for mutter-3.30.1. In the current version in bionic mutter-3.28.3, I don't see "Wayland EGLStream: ${have_wayland_eglstream}" option in configure.

Status changed to 'Confirmed' because the bug affects multiple users.

Sorry, it seems my concerns about EGLStreams are quite different and not blocking your concerns about EGLDevice. Now restoring the original bug title.

Since this bug is fixed in Ubuntu 18.10 onward I'm going to mark it as fixed and we can nominate 18.04 to get the fix later.

As I understand it, we presently have:

mutter in 18.04:
  * EGLDevice compiled but not working (this bug)
  * EGLStreams not compiled

mutter in 18.10:
  * EGLDevice compiled and working
  * EGLStreams not compiled

mutter in 19.04:
  * EGLDevice compiled and working
  * EGLStreams not compiled (work in progress outside of this bug, starting with https://launchpad.net/ubuntu/disco/+queue?queue_state=0&queue_text=)

mutter from upstream git that I built locally:
  * EGLDevice compiled and working
  * EGLStreams compiled and apparently still not working (will investigate this further as the other issues get resolved).

It appears the backport has already been done upstream. Both the missing commits are already in the gnome-3-28 branch of mutter, scheduled for inclusion in mutter version 3.28.4 (whenever that may be).

I have also verified that mutter version 3.28.3 fails, and the gnome-3-28 branch (721de281) works (with Nvidia driver 410).

This all means we should now wait for an official tag 3.28.4 from upstream and get that into bionic eventually.

Fact is stranger than fiction. I failed to consider that maybe EGLStreams was working in mutter 3.28 and it got broken later on. Actually there were TWO separate regressions (separate to this bug) this year. So here are corrections to comment #8 after a more detailed analysis:

mutter 3.28.3 in 18.04:
  * EGLDevice configured, compiled, but not working (this bug)
  * EGLStreams not configurable, always built, but also not working (this bug)

mutter 3.28.4 (prerelease):
  * EGLDevice compiled and working
  * EGLStreams not configurable, always built, and working**

mutter 3.30.2 in 18.10 & 19.04:
  * EGLDevice compiled and working
  * EGLStreams' new build deps are missing so not configured, but compiled in anyway by accident because the new build deps were weak, and it's working**

mutter 3.32 (prerelease) from upstream git:
  * EGLDevice compiled and working
  * EGLStreams' new build deps are missing so not configured, and not compiled any more thanks to a recent "fix" 417c00b8fa. We can get the missing build deps either with libnvidia-egl-wayland-dev (soon-to-be in 19.04), or do some kind of revert of 417c00b8fa (because the new build deps are pretty weak and probably shouldn't have been implemented that way in mutter 3.30+).

** EGLStreams working means Wayland clients get full Nvidia acceleration but I thought it was broken for a while because that also includes 100% CPU use by [kworker/u16:3+events_unbound]. Possible driver bug?

Tagging rls-bb-notfixing after team meeting discussion, that's a bit change and wayland is not the default desktop in bionic. That can change/be reconsidered if it's customer escalated or such though

More notes about EGLStreams support:

- mutter 3.28.4 works, but not perfectly. Some clients (e.g. glmark2-wayland) don't resize properly. That bug appears to be fixed in mutter 3.30+. I don't yet know what commit fixed it.

- mutter 3.32 in future Ubuntu 19.04 won't work at all till we get this package into main: https://launchpad.net/ubuntu/+source/egl-wayland and then mutter rebuilt.

- mutter 3.30 in Ubuntu 18.10 and 19.04 work well enough right now except for the below caveats...

- GLX clients are still software rendered in all releases, which should be fixed by releasing egl-wayland into 19.04 and then rebuilding Xwayland with the new build dependency.

- There is very high CPU usage in the kernel when using EGLStreams and nvidia-drm.modeset=1 -> bug 1808108 (NVIDIA please investigate).

In regard to caveats above:
There is no mention of specific Nvidia series, is it presumed that XXXm devices should work now in 18.10 & 19.04?
(- I've never seem any Nvidia m series work in wayland..

Additionally what about the newer 10XX mobile devices?
(- I've none to try.

Doug, hardware model numbers don't matter here. Only software version numbers.

Maybe I'm missing the point of this bug, if so sorry about that.
The bug seems to be basically about being able to log into a wayland session while using nvidia drivers. Though the description has changed a time or two.

So question could be simply rephrased - Does the fix released imply that nvidia should be working on 19.04 on all nvidia devices?

It's stated above that -
"mutter 3.30.2 in 18.10 & 19.04:
  * EGLDevice compiled and working
  * EGLStreams' new build deps are missing so not configured, but compiled in anyway by accident because the new build deps were weak, and it's working**"

 "** EGLStreams working means Wayland clients get full Nvidia acceleration but I thought it was broken for a while because that also includes 100% CPU use by [kworker/u16:3+events_unbound]. Possible driver bug? "

What I mentioned is that no m series nvidia i've tested gets nvidia support in a wayland session.
(- when logging into wayland one is automatically switched to Intel

Doug,

This bug was a request to get two missing commits into Ubuntu. They are already in some versions of Ubuntu so:

> Since this bug is fixed in Ubuntu 18.10 onward I'm going to mark it as fixed and we can nominate 18.04 to get the fix later.

This bug is Fix Released in 18.10 onward, but not 18.04 yet. "Fix Released" is still the correct status since that tracks the current Ubuntu release.

That all said, there are still problems with Wayland support in the Nvidia driver outlined above so we don't yet recommend it for anyone, even in 19.04, and even though this bug is fixed.

Please log your own new bug to describe any problems you have rather than adding comments here. This bug is for the original reporter only.

Not really "in progress". Generally though, all that bionic needs here is mutter version 3.28.4.

Although bug 1811900 suggests it is in progress.

Thanks for uploading the fix for this bug report to -proposed. However, when reviewing the package in -proposed and the details of this bug report I noticed that the bug description is missing information required for the SRU process. You can find full details at http://wiki.ubuntu.com/StableReleaseUpdates#Procedure but essentially this bug is missing some of the following: a statement of impact, a test case and details regarding the regression potential. Thanks in advance!

Hello Yogish, or anyone else affected,

Accepted mutter into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mutter/3.28.3+git20190124-0ubuntu18.04.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Hello Yogish, or anyone else affected,

Accepted mutter into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mutter/3.28.3+git20190124-0ubuntu18.04.2 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Does it mean that gdm will show an option to start Gnome on Wayland when using Nvidia binary drivers?

No, not directly, but kind of :)

The option to start a Wayland session is enabled by adding:

  nvidia-drm.modeset=1

to your kernel command line.

Secondly, mutter's Wayland backend needs to be found to WORK with it. If it doesn't work (this bug), then mutter will hide the Wayland option before you ever see the login screen.

So you should:

  1. Add nvidia-drm.modeset=1 to your kernel command line; and
  2. Either wait for this bug to be fixed in 18.04 or just use a later Ubuntu release which doesn't have this bug.

Since this bug was optional and not planned to get fixed ("rls-bb-notfixing"), it's not a blocking issue. But it does appear we get the fix for free.

The verification of the Stable Release Update for mutter has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

This bug was fixed in the package mutter - 3.28.3+git20190124-0ubuntu18.04.2

---------------
mutter (3.28.3+git20190124-0ubuntu18.04.2) bionic; urgency=medium

  * control: Add Breaks on budgie-desktop verions broken by this upload.
    budgie-desktop needs a fix in 10.4+git20171031.10.g9f71bb8-1.2ubuntu1.2
    for compatibility with this mutter.

mutter (3.28.3+git20190124-0ubuntu18.04.1) bionic; urgency=medium

  * New upstream git snapshot based on 3.28.3 plus commits up to 4af8d9d47
    (LP: #1811900)
    - Fix crash in dual monitor setup and gdm activation (LP: #1790525,
      LP: #1795774)
    - Make possible to launch gnome-shell in wayland using nvidia and EGLDevice
      backend (LP: #1805444)
  * debian/libmutter-2-0.symbols: Add new symbols
  * d/p/gpu-kms-Don-t-crash-if-drmModeGetResources-returns-N.patch,
    d/p/native-gpu-Handle-drmModeSetCrtc-failing-gracefully.patch,
    d/p/monitor-manager-Filter-out-low-screen-resolutions.patch,
    d/p/window-wayland-Always-update-monitor-for-non-user-ops.patch,
    d/p/window-Don-t-refuse-to-move-focus-to-the-grab-window.patch,
    d/p/window-Explicitly-exclude-unmanaging-window-from-focus-ag.patch,
    d/p/monitor-Use-current-monitor-mode-to-check-whether-active.patch,
    d/p/core-Return-1-if-meta_window_get_monitor-is-called-on-an-.patch,
    d/p/renderer-native-Fallback-to-non-planar-API-if-gbm_bo_get_.patch,
    d/p/clutter-x11-Implement-keycode-lookup-from-keysyms-on-virt.patch,
    d/p/clutter-Do-not-latch-modifiers-on-modifier-keys.patch:
    - Removed as applied upstream
  * d/p/clutter-Fix-offscreen-effect-painting-of-clones.patch:
    - Fix offscreen-effect painting of clones in zoom mode (LP: #1767648,
      LP: #1779615)

 -- Iain Lane <email address hidden> Wed, 17 Apr 2019 11:35:51 +0100