[Kernel-packages] [Bug 2026887] Re: 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
The changelog needs fixing per comment #12. ** Also affects: linux-oem-5.17 (Ubuntu) Importance: Undecided Status: New ** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy ** Tags added: block-proposed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 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 linux-oem-5.17 package in Ubuntu: New 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
[Kernel-packages] [Bug 2026887] Re: 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
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 amd64GObject introspection data for Mutter ii libmutter-10-0:amd64 42.9-0ubuntu3 amd64window 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
[Kernel-packages] [Bug 2026887] Re: 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
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 -- 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
[Kernel-packages] [Bug 2026887] Re: 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
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. -- 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
[Kernel-packages] [Bug 2026887] Re: 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
Hi Andreas, Will try to check new packages in next days. Thanks for all. -- 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
[Kernel-packages] [Bug 2026887] Re: 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
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 amd64window manager library from the Mutter window manage GNOME SHELL VERSION: dpkg -l | grep gnome-shell ii gnome-shell42.9-0ubuntu2 amd64graphical 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 amd64Signed kernel image generic ii linux-image-5.19.0-46-generic 5.19.0-46.47~22.04.1 amd64Signed kernel image generic ii linux-image-generic-hwe-22.04 5.19.0.46.47~22.04.21 amd64Generic Linux kernel image -- 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
[Kernel-packages] [Bug 2026887] Re: 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
In the test plan, can you also please confirm it keeps working with the current and upcoming HWE kernels for jammy? ** Changed in: mutter (Ubuntu Jammy) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-jammy -- 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
[Kernel-packages] [Bug 2026887] Re: 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
** Also affects: linux-hwe-5.19 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-hwe-5.19 (Ubuntu) Status: New => Fix Released ** Description changed: [ 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. - [ Workaround ] + [ 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. -- 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: In Progress 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
[Kernel-packages] [Bug 2026887] Re: 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
** No longer affects: mutter (Ubuntu Jammy) ** 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 ** Changed in: linux (Ubuntu Jammy) Status: New => Confirmed ** Changed in: mutter (Ubuntu Jammy) Status: New => In Progress ** Changed in: mutter (Ubuntu Jammy) Importance: Undecided => Critical ** Changed in: mutter (Ubuntu Jammy) Assignee: (unassigned) => Daniel van Vugt (vanvugt) ** Changed in: linux-intel-iotg (Ubuntu Jammy) Status: New => Confirmed ** Changed in: linux (Ubuntu Jammy) Status: Confirmed => Won't Fix ** No longer affects: linux-intel-iotg (Ubuntu Jammy) -- 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-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: In Progress 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. [ Workaround ] Add MUTTER_DEBUG_USE_KMS_MODIFIERS=0 to /etc/environment [ 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
[Kernel-packages] [Bug 2026887] Re: 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
I'm setting the importance to Critical per #6 at https://wiki.ubuntu.com/StableReleaseUpdates#Procedure ** Changed in: mutter (Ubuntu Jammy) Importance: High => Critical -- 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-intel-iotg package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Invalid Status in mutter source package in Jammy: In Progress 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. [ Workaround ] Add MUTTER_DEBUG_USE_KMS_MODIFIERS=0 to /etc/environment [ 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
[Kernel-packages] [Bug 2026887] Re: 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
** Description changed: [ 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. [ Workaround ] Add MUTTER_DEBUG_USE_KMS_MODIFIERS=0 to /etc/environment [ 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. -- 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-intel-iotg package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Invalid Status in mutter source package in Jammy: In Progress 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. [ Workaround ] Add MUTTER_DEBUG_USE_KMS_MODIFIERS=0 to /etc/environment [ 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
[Kernel-packages] [Bug 2026887] Re: 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
Fix proposed: https://salsa.debian.org/gnome- team/mutter/-/merge_requests/100 -- 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-intel-iotg package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Invalid Status in mutter source package in Jammy: In Progress 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. [ Workaround ] Add MUTTER_DEBUG_USE_KMS_MODIFIERS=0 to /etc/environment [ 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
[Kernel-packages] [Bug 2026887] Re: 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
** Description changed: - Hi Ubuntu Team, + [ Impact ] - MY ISSUE: - I installed today my PC with Ubuntu IOT Desktop(22.04.2 LTS (Jammy Jellyfish)). - But with updated for all packages and with reboot PC, i have error with starting gdm and access to /dev/dri/card0. + gnome-shell/mutter 42.9 fails to start (black screen) on Intel Alder + Lake systems running older kernels such as 5.15. - ERROR: - iul 11 19:00:10 MY-PC gnome-session[1022]: gnome-session-binary[1022]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed - iul 11 19:00:10 MY-PC gnome-session[1022]: gnome-session-binary[1022]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed - iul 11 19:00:10 MY-PC gnome-session-binary[1022]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed - iul 11 19:00:10 MY-PC gnome-session-binary[1022]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed - iul 11 19:00:11 MY-PC gnome-session-binary[1022]: Entering running state - root@MY-PC:/home/tester# journalctl -b --no-pager | grep gnome- - iul 11 19:00:09 MY-PC systemd[1]: Mounting Mount unit for gnome-3-38-2004, revision 119... - iul 11 19:00:09 MY-PC systemd[1]: Mounted Mount unit for gnome-3-38-2004, revision 119. - iul 11 19:00:10 MY-PC gnome-session[1022]: gnome-session-binary[1022]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed - iul 11 19:00:10 MY-PC gnome-session[1022]: gnome-session-binary[1022]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed - iul 11 19:00:10 MY-PC gnome-session-binary[1022]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed - iul 11 19:00:10 MY-PC gnome-session-binary[1022]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed - iul 11 19:00:10 MY-PC gnome-shell[1040]: Running GNOME Shell (using mutter 42.9) as a Wayland display server - iul 11 19:00:10 MY-PC gnome-shell[1040]: Device '/dev/dri/card0' prefers shadow buffer - iul 11 19:00:10 MY-PC gnome-shell[1040]: Added device '/dev/dri/card0' (i915) using atomic mode setting. - iul 11 19:00:10 MY-PC gnome-shell[1040]: Created gbm renderer for '/dev/dri/card0' - iul 11 19:00:10 MY-PC gnome-shell[1040]: Boot VGA GPU /dev/dri/card0 selected as primary - iul 11 19:00:10 MY-PC /usr/libexec/gdm-wayland-session[1021]: dbus-daemon[1021]: [session uid=128 pid=1021] Activating service name='org.a11y.Bus' requested by ':1.4' (uid=128 pid=1040 comm="/usr/bin/gnome-shell " label="unconfined") - iul 11 19:00:10 MY-PC gnome-shell[1040]: Using public X11 display :1024, (using :1025 for managed services) - iul 11 19:00:10 MY-PC gnome-shell[1040]: Using Wayland display name 'wayland-0' - iul 11 19:00:11 MY-PC gnome-shell[1040]: Unset XDG_SESSION_ID, getCurrentSessionProxy() called outside a user session. Asking logind directly. - iul 11 19:00:11 MY-PC gnome-shell[1040]: Will monitor session c1 - iul 11 19:00:11 MY-PC dbus-daemon[693]: [system] Activating via systemd: service name='org.freedesktop.locale1' unit='dbus-org.freedesktop.locale1.service' requested by ':1.34' (uid=128 pid=1040 comm="/usr/bin/gnome-shell " label="unconfined") - iul 11 19:00:11 MY-PC /usr/libexec/gdm-wayland-session[1021]: dbus-daemon[1021]: [session uid=128 pid=1021] Activating service name='org.freedesktop.impl.portal.PermissionStore' requested by ':1.3' (uid=128 pid=1040 comm="/usr/bin/gnome-shell " label="unconfined") - iul 11 19:00:11 MY-PC dbus-daemon[693]: [system] Activating via systemd: service name='org.freedesktop.GeoClue2' unit='geoclue.service' requested by ':1.34' (uid=128 pid=1040 comm="/usr/bin/gnome-shell " label="unconfined") - iul 11 19:00:11 MY-PC polkitd(authority=local)[725]: Registered Authentication Agent for unix-session:c1 (system bus name :1.34 [/usr/bin/gnome-shell], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) - iul 11 19:00:11 MY-PC dbus-daemon[693]: [system] Activating via systemd: service name='org.freedesktop.PackageKit' unit='packagekit.service' requested by ':1.34' (uid=128 pid=1040 comm="/usr/bin/gnome-shell " label="unconfined") - iul 11 19:00:11 MY-PC gnome-shell[1040]: Extension d...@rastersoft.com already installed in /usr/share/gnome-shell/extensions/d...@rastersoft.com. /usr/share/gnome-shell/extensions/d...@rastersoft.com will not be loaded - iul 11 19:00:11 MY-PC gnome-shell[1040]: Extension ubuntu-appindicat...@ubuntu.com already installed in /usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com. /usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com will not be loaded - iul 11 19:00:11 MY-PC gnome-shell[1040]: Extension ubuntu-d...@ubuntu.com already installed in /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com. /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com will not be
