Thank you for your bug report, the patch was removed on purpose the summary of 
the Ubuntu changes just got copied over without that bit removed
https://launchpad.net/ubuntu/+source/gdm3/3.32.0-1ubuntu2

The issue there seems to be 
'gdm will trigger a kernel oops in the i915 driver'

That's a kernel bug, could you report it using 'ubuntu-bug linux' and
include the logs/details of the oops error?

** Changed in: gdm3 (Ubuntu)
   Importance: Undecided => Low

** Changed in: gdm3 (Ubuntu)
       Status: New => Invalid

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1852113

Title:
  gdm logic for disabling wayland on nvidia is too rigid

Status in gdm3 package in Ubuntu:
  Invalid

Bug description:
  First observation is that the changelog here:

  https://bugs.launchpad.net/ubuntu/+source/gdm3/3.34.1-1ubuntu1

  says that the blacklisting of wayland+nvidia was reverted:

  + Add debian/patches/revert_nvidia_wayland_blacklist.patch:
        - Don't blacklist nvidia for wayland

  But this patch isn't in the sources and the blacklist rule is still
  present.

  If I disable the udev blacklist rule, wayland on nvidia continues to
  work as well as it did in 19.04.

  However, I've been doing a bunch of playing around with hybrid
  configurations, and there is one situation, where there can be a
  problem. If you are using nvidia as your primary graphics device, but
  the Intel one is still visible on the pci bus (not disabled in
  firmware), then gdm will trigger a kernel oops in the i915 driver if
  wayland is not disabled. This didn't happen in 19.04 so it's a
  regression somewhere.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1852113/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to     : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to