[Bug 1966808] Re: [radeon] gnome-shell Wayland sessions fail to start on legacy Radeon systems (Failed to lock front buffer on /dev/dri/cardN: drmModeAddFB2WithModifiers failed: Invalid argument)
Also confirmed in my system now with update - no workaround required in /etc/environment now. Thank you! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966808 Title: [radeon] gnome-shell Wayland sessions fail to start on legacy Radeon systems (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/mutter/+bug/1966808/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966808] Re: [amdgpu][radeon] gnome-shell Wayland sessions fail to start (Failed to lock front buffer on /dev/dri/card1: drmModeAddFB2WithModifiers failed: Invalid argument)
I just tried commenting out MUTTER_DEBUG_USE_KMS_MODIFIERS=0 and get the original problem again, so the issue is still happening without the workaround. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966808 Title: [amdgpu][radeon] gnome-shell Wayland sessions fail to start (Failed to lock front buffer on /dev/dri/card1: drmModeAddFB2WithModifiers failed: Invalid argument) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1966808/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966808] Re: [amdgpu][radeon] gnome-shell Wayland sessions fail to start (Failed to lock front buffer on /dev/dri/card1: drmModeAddFB2WithModifiers failed: Invalid argument)
I also *just* installed mutter, as it seems there was a package that provides a mutter binary, that seems to have a similar version (42~beta-1ubuntu): $ mutter --version mutter 42.beta -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966808 Title: [amdgpu][radeon] gnome-shell Wayland sessions fail to start (Failed to lock front buffer on /dev/dri/card1: drmModeAddFB2WithModifiers failed: Invalid argument) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1966808/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966808] Re: [amdgpu][radeon] gnome-shell Wayland sessions fail to start (Failed to lock front buffer on /dev/dri/card1: drmModeAddFB2WithModifiers failed: Invalid argument)
Noted, thank you. I'll check after 42.0-1ubuntu1 is released. I am a bit unsure of this though, this is what I currently see: $# dpkg -l|grep -i mutter ii gir1.2-mutter-10:amd6442~beta-1ubuntu2 amd64GObject introspection data for Mutter ii libmutter-10-0:amd64 42~beta-1ubuntu2 amd64window manager library from the Mutter window manager ii mutter-common 42~beta-1ubuntu2 all shared files for the Mutter window manager Out of these, should I be looking at the mutter-common (or libmutter?) version to change to 42.0-1ubuntu1? Thanks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966808 Title: [amdgpu][radeon] gnome-shell Wayland sessions fail to start (Failed to lock front buffer on /dev/dri/card1: drmModeAddFB2WithModifiers failed: Invalid argument) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1966808/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966808] Re: [amdgpu][radeon] gnome-shell Wayland sessions fail to start (Failed to lock front buffer on /dev/dri/card1: drmModeAddFB2WithModifiers failed: Invalid argument)
Thank you for the quick investigation into this. Once the patch you listed: https://gitlab.gnome.org/GNOME/mutter/-/commit/690b8806d is available, would I have to comment out the KMS_MODIFIERS line for completeness? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966808 Title: [amdgpu][radeon] gnome-shell Wayland sessions fail to start (Failed to lock front buffer on /dev/dri/card1: drmModeAddFB2WithModifiers failed: Invalid argument) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1966808/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966808] Re: [amdgpu][radeon] gnome-shell Wayland sessions fail to start (Failed to lock front buffer on /dev/dri/card1: drmModeAddFB2WithModifiers failed: Invalid argument)
MUTTER_DEBUG_USE_KMS_MODIFIERS=0 fixes the issue. gdm3 also works now. ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => New ** Changed in: mutter (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966808 Title: [amdgpu][radeon] gnome-shell Wayland sessions fail to start (Failed to lock front buffer on /dev/dri/card1: drmModeAddFB2WithModifiers failed: Invalid argument) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1966808/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966808] [NEW] Wayland crashes on Jammy (was fine on Impish)
Public bug reported: Wayland started crashing for me on upgrade to Jammy, which I'm aware is currently in alpha. gdm was crashing, and changing to lightdm addressed this issue. If I select 'Ubuntu on Xorg' - I can login without problems. If I select Wayland instead, I just get a black screen, and I have to kill gnome-session from a virtual console. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42~beta-1ubuntu3 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Mar 28 15:23:51 2022 DisplayManager: lightdm InstallationDate: Installed on 2022-03-19 (9 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220318) RelatedPackageVersions: mutter-common 42~beta-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966808 Title: Wayland crashes on Jammy (was fine on Impish) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1966808/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814938] Re: drm.edid_firmware fails to load firmware where crypsetup-initramfs is installed
Running into the same problem. I have 2 ACR Model 768 27 inch monitors - one of them somehow got its EDID corrupted recently. Ideally, I'd like to write the good EDID into the monitor with the corrupted EDID, but barring that (edid-rw didn't work for me - IO error), I'd like to boot the system with a good EDID. I have two systems - one of which it works perfectly on, the other not so much. Good system: Ubuntu 21.10 - only had to add good edid to /usr/lib/firmware/edid/acer_monitor.bin and update the grub conf accordingly - everything works. Bad system: Ubuntu 20.04 based system. Steps tried: - added good edid to /usr/lib/firmware/edid/acer_monitor.bin - updated initramfs using script above as reference In the good system: cat /sys/class/drm/card*/edid shows the updated edid for the card, while for the bad system, I don't see an edid override. cat /proc/cmdline confirms the edid override is in place. e.g. for 20.04 based system (bad): # cat /proc/cmdline BOOT_IMAGE=/boot/vmlinuz-5.13.0-30-generic root=UUID=f896afab-6f99-4478-a402-9d612972a5b5 ro drm.edid_firmware=DP1:ed id/acer_monitor.bin quiet splash vt.handoff=7 # lsinitramfs /boot/initrd.img|grep edid usr/lib/firmware/edid usr/lib/firmware/edid/acer_monitor.bin # cat /sys/class/drm/card0-DP-1/edid ... no overridden EDID ... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814938 Title: drm.edid_firmware fails to load firmware where crypsetup-initramfs is installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1814938/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
