gnome-shell 42.9 Wayland sessions fail to start on Intel 12th gen or later if running 5.15/5.17 kernels (Failed to lock front buffer on /dev/dri/cardN: drmModeAddFB2WithModifiers failed: Invalid argument)

[Ionut Nechita]

[ Impact ]

gnome-shell/mutter 42.9 fails to start (black screen) on Intel Alder Lake systems running older kernels such as 5.15.

[ Test Plan ]

Try to log into gnome-shell. Verify there is a picture on the screen.

[ Where problems could occur ]

The offending code change relates to Intel-specific chip IDs so the change is limited to Intel systems. Although affected Intel systems worked perfectly before the change so we don't expect any problems in reverting the change. In theory the worst case is limited to more problems like that described in Impact above.

[ Workarounds ]

Add MUTTER_DEBUG_USE_KMS_MODIFIERS=0 to /etc/environment

or upgrade to a newer kernel:
sudo apt install linux-generic-hwe-22.04

[ Other Info ]

The log messages relating to this bug are:
iul 11 19:00:11 MY-PC gnome-shell[1040]: Failed to lock front buffer on /dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument
iul 11 19:00:11 MY-PC gnome-shell[1040]: Failed to lock front buffer on /dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument
iul 11 19:00:11 MY-PC gnome-shell[1040]: Failed to lock front buffer on /dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument
iul 11 19:00:11 MY-PC gnome-shell[1040]: Failed to lock front buffer on /dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument
...

For kinetic: The bug never existed in mutter 43.0 (it was introduced in 43.2) and was already fixed in the kernel anyway.

For lunar and later: The bug was already fixed in the kernel. You would only ever encounter it in theory if you downgrade the kernel.

[Daniel van Vugt (vanvugt)]

Thanks for the bug report. It appears the kernel '5.15.0-1034-intel-iotg' is too old for the integrated GPU of 'i7-1260P'.

Did you install that kernel manually? Or perhaps install some IOT image instead of Ubuntu Desktop? I would have expected a fresh install of Ubuntu Desktop 22.04.2 to come with a newer kernel:

  https://ubuntu.com/download/desktop

so please install that instead.

[Launchpad Janitor (janitor)]

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

[Daniel van Vugt (vanvugt)]

Nevermind. This bug is affecting regular Ubuntu Desktop too, for those running the original 22.04 release. It shouldn't happen if you're using 22.04.2 though because that has a new enough kernel to support the hardware, in theory.

[Daniel van Vugt (vanvugt)]

Suggested workarounds:

* Add MUTTER_DEBUG_USE_KMS_MODIFIERS=0 to /etc/environment

* sudo apt install linux-generic-hwe-22.04

[Daniel van Vugt (vanvugt)]

It's a regression introduced in mutter 42.9 by Intel:

https://gitlab.gnome.org/GNOME/mutter/-/commit/1fd96e30f5f8a61d70d51f9012112e01818161a7

Although they would probably argue it's not a regression so long as you have a new enough kernel. Since we don't always have a new enough kernel in jammy we probably need to revert that commit.

[Daniel van Vugt (vanvugt)]

Fix proposed: https://salsa.debian.org/gnome-team/mutter/-/merge_requests/100

[Jeremy Bícha (jbicha)]

I'm setting the importance to Critical per #6 at https://wiki.ubuntu.com/StableReleaseUpdates#Procedure

[Andreas Hasenack (ahasenack)]

In the test plan, can you also please confirm it keeps working with the current and upcoming HWE kernels for jammy?

[Andreas Hasenack (ahasenack)]

Hello Ionut, or anyone else affected,

Accepted mutter into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mutter/42.9-0ubuntu3 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, what testing has been performed on the package and change the tag from verification-needed-jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-jammy. 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.

[Ionut Nechita (ionut-n2001)]

Hi Daniel,

I reinstalled today my ADL-P PC with Ubuntu Desktop 22.04.02.
And this is not reproduced with -generic kernel.

I have this: 5.19.0-46-generic #47~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Wed Jun 21 15:35:31 UTC 2 x86_64 x86_64 x86_64 GNU/Linux
And no error with this.

LIBMUTTER VERSION:
dpkg -l | grep libmutter
ii libmutter-10-0:amd64 42.9-0ubuntu1 amd64 window manager library from the Mutter window manage

GNOME SHELL VERSION:
dpkg -l | grep gnome-shell
ii gnome-shell 42.9-0ubuntu2 amd64 graphical shell for the GNOME desktop

KERNEL VERSION:
dpkg -l | grep linux-image
ii linux-image-5.19.0-32-generic 5.19.0-32.33~22.04.1 amd64 Signed kernel image generic
ii linux-image-5.19.0-46-generic 5.19.0-46.47~22.04.1 amd64 Signed kernel image generic
ii linux-image-generic-hwe-22.04 5.19.0.46.47~22.04.21 amd64 Generic Linux kernel image

[Ionut Nechita (ionut-n2001)]

Hi Andreas,

Will try to check new packages in next days.
Thanks for all.

[Daniel van Vugt (vanvugt)]

I think "This was a regression introduced by Intel in 42.9!" should be removed from the changelog. It's not something I wrote in the patch or in the merge proposal.

[Matthias Doerbecker (matthiasd)]

Hello Andreas,

I saw the same error on a 13th Gen Intel(R) Core(TM) i7-1370PE using the IOT release of jammy desktop.

I can confirm that installing mutter from jammy-proposed fixed the issue on my system.

$ uname -a
Linux amr-rplp-01 5.15.0-1034-intel-iotg #39-Ubuntu SMP Thu Jun 22 20:56:05 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 22.04.2 LTS
Release: 22.04
Codename: jammy

Now I have this mutter release:

$ apt list -a mutter
Listing... Done
mutter/jammy-proposed,now 42.9-0ubuntu3 amd64 [installed]
mutter/jammy-updates 42.9-0ubuntu1 amd64
mutter/jammy 42.0-3ubuntu2 amd64

[Ionut Nechita (ionut-n2001)]

Hi Andreas,

I reinstalled today my PC with Ubuntu Desktop IOT.
And i use latest packages from proposed repository.

This issue is now resolved.

My PC now running this:

Kernel version: 5.15.0-1035-intel-iotg #40-Ubuntu SMP Fri Jul 14 08:03:36 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Mutter version:
dpkg -l | grep mutter
ii gir1.2-mutter-10:amd64 42.9-0ubuntu3 amd64 GObject introspection data for Mutter
ii libmutter-10-0:amd64 42.9-0ubuntu3 amd64 window manager library from the Mutter window manager
ii mutter-common 42.9-0ubuntu3 all shared files for the Mutter window manager

Thank you Daniel for your support.

A good day.

[Daniel van Vugt (vanvugt)]

^^^
Jammy verification done in comment #14.

But I'm blocking proposed because the changelog needs fixing per comment #12, and agreed within the desktop team.

[Launchpad Janitor (janitor)]

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

[Steve Langasek (vorlon)]

Hello Ionut, or anyone else affected,

Accepted mutter into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mutter/42.9-0ubuntu4 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, what testing has been performed on the package and change the tag from verification-needed-jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-jammy. 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.

[Unnikrishnan (unni10286)]

Test environment

OS: Ubuntu 22.04.02
kernel: 5.15.0-76
Processor: 12th Gen Intel(R) Core(TM) i7-1270P
mutter-common: 42.9-0ubuntu1

Problem: Stuck at a black screen after entering hard disk encryption password. Not getting any login screen for entering username/password

Tried proposed fix by installing 42.9-0ubuntu4 from Jammy-proposed

Rebooted machine

Now login screen is loaded after entering hard disk encryption password

[Ionut Nechita (ionut-n2001)]

Hi Steve Langasek,

I reinstalled today my PC with Ubuntu Desktop IOT.
And i use latest packages from proposed repository.

This issue is now resolved.

My PC now running this:

Kernel version: 5.15.0-1035-intel-iotg #40-Ubuntu SMP Fri Jul 14 08:03:36 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Mutter version:
dpkg -l | grep mutter
ii gir1.2-mutter-10:amd64 42.9-0ubuntu4 amd64 GObject introspection data for Mutter
ii libmutter-10-0:amd64 42.9-0ubuntu4 amd64 window manager library from the Mutter window manager
ii mutter-common 42.9-0ubuntu4 all shared files for the Mutter window manager

Thank you Daniel and Unnikrishnan for your support.

A good day.

[Łukasz Zemczak (sil2100)]

The verification of the Stable Release Update for mutter has completed successfully and the package is now being 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.

[Launchpad Janitor (janitor)]

This bug was fixed in the package mutter - 42.9-0ubuntu4

---------------
mutter (42.9-0ubuntu4) jammy; urgency=medium

  * Add Revert-data-udev-Don-t-disable-KMS-modifiers-on-newer-i91.patch
    to fix rendering failures on older kernels (5.15) when run on newer
    hardware (Intel Alder Lake). (LP: #2026887)

mutter (42.9-0ubuntu2) jammy; urgency=medium

  * Add clutter-frame-clock-Avoid-rapidly-toggling-dynamic-max-re.patch to
    avoid cursor stutter (LP: #2023766)
  * Add backends-x11-Return-zero-Hz-instead-of-nan-Hz-for-incompl.patch
    so that incomplete graphics mode definitions are reported as having a
    refresh rate of 0 Hz instead of -nan Hz. This also fixes the behaviour
    of the 'Revert Settings' button (LP: #2020782)

 -- Daniel van Vugt <email address hidden> Thu, 13 Jul 2023 08:15:36 -0400