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.
** Changed in: mutter (Ubuntu)
Importance: Undecided => High
** Changed in: mutter (Ubuntu)
Assignee: (unassigned) => Daniel van Vugt (vanvugt)
** Also affects: linux (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: mutter (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: linux-intel-iotg (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Kinetic)
Importance: Undecided
Status: New
** Also affects: mutter (Ubuntu Kinetic)
Importance: Undecided
Status: New
** Also affects: linux-intel-iotg (Ubuntu Kinetic)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Mantic)
Importance: Undecided
Status: Fix Released
** Also affects: mutter (Ubuntu Mantic)
Importance: High
Assignee: Daniel van Vugt (vanvugt)
Status: Confirmed
** Also affects: linux-intel-iotg (Ubuntu Mantic)
Importance: Medium
Status: Confirmed
** Also affects: linux (Ubuntu Lunar)
Importance: Undecided
Status: New
** Also affects: mutter (Ubuntu Lunar)
Importance: Undecided
Status: New
** Also affects: linux-intel-iotg (Ubuntu Lunar)
Importance: Undecided
Status: New
** No longer affects: linux (Ubuntu Jammy)
** No longer affects: linux (Ubuntu Kinetic)
** No longer affects: linux (Ubuntu Lunar)
** No longer affects: linux (Ubuntu Mantic)
** No longer affects: linux-intel-iotg (Ubuntu Jammy)
** No longer affects: linux-intel-iotg (Ubuntu Kinetic)
** No longer affects: linux-intel-iotg (Ubuntu Lunar)
** No longer affects: linux-intel-iotg (Ubuntu Mantic)
** Changed in: mutter (Ubuntu Jammy)
Status: New => Confirmed
** Changed in: mutter (Ubuntu Jammy)
Importance: Undecided => High
** Changed in: mutter (Ubuntu Jammy)
Assignee: (unassigned) => Daniel van Vugt (vanvugt)
** Changed in: mutter (Ubuntu Kinetic)
Status: New => Invalid
** Changed in: mutter (Ubuntu Lunar)
Status: New => Invalid
** Changed in: mutter (Ubuntu Mantic)
Status: Confirmed => Invalid
** Changed in: mutter (Ubuntu Mantic)
Assignee: Daniel van Vugt (vanvugt) => (unassigned)
** Changed in: mutter (Ubuntu Mantic)
Importance: High => Undecided
** Changed in: mutter (Ubuntu Jammy)
Status: Confirmed => In Progress
** Summary changed:
- [Intel Alder Lake] gnome-shell Wayland sessions fail to start on 5.15 kernels
(Failed to lock front buffer on /dev/dri/cardN: drmModeAddFB2WithModifiers
failed: Invalid argument)
+ 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)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter 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)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2026887/+subscriptions
--
desktop-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
