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.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-intel-iotg in Ubuntu.
https://bugs.launchpad.net/bugs/2026887
Title:
gnome-shell 42.9 Wayland sessions fail to start on Intel Alder Lake
running 5.15 kernels (Failed to lock front buffer on /dev/dri/cardN:
drmModeAddFB2WithModifiers failed: Invalid argument)
Status in linux package in Ubuntu:
Fix Released
Status in linux-hwe-5.19 package in Ubuntu:
Fix Released
Status in linux-intel-iotg package in Ubuntu:
Confirmed
Status in mutter package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Won't Fix
Status in mutter source package in Jammy:
Fix Committed
Status in mutter source package in Kinetic:
Invalid
Status in mutter source package in Lunar:
Invalid
Status in mutter source package in Mantic:
Invalid
Bug description:
[ 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.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2026887/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
