Tracking upstream in https://gitlab.gnome.org/GNOME/mutter/-/issues/2210
** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #2210
https://gitlab.gnome.org/GNOME/mutter/-/issues/2210
** Also affects: mutter via
https://gitlab.gnome.org/GNOME/mutter/-/issues/2210
Importance:
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
Desktop Bugs, which is subscribed to mutter in Ubuntu.
Comment #16 is surprising. Can anyone else confirm?
** Description changed:
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
I installed 22.04 today on a machine with an AMD GPU. I have
libmutter-10-0 42.0-1ubuntu1 and I still encountered the problem.
Setting MUTTER_DEBUG_USE_KMS_MODIFIERS=0 is still necessary in
42.0-1ubuntu1.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
MUTTER_DEBUG_USE_KMS_MODIFIERS=0
fixes the issue for me too.
I will give a new try without this variable after update 42.0-1ubuntu1 is
released.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
The middle line "libmutter-10-0" is the important one for gnome-shell,
but all three of the packages shown in comment #12 need to keep the same
version number to function correctly.
The package named "mutter" and the "mutter" binary are confusingly not
relevant here. It's not used in Ubuntu and
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
Desktop Bugs, which is subscribed to
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
You don't need to, but we would like to know if that fix removes the
need for the workaround MUTTER_DEBUG_USE_KMS_MODIFIERS=0
If you still need MUTTER_DEBUG_USE_KMS_MODIFIERS=0 after mutter
42.0-1ubuntu1 is released then we should open a new bug in
https://gitlab.gnome.org/GNOME/mutter/-/issues
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
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
Desktop Bugs,
Please wait until you receive mutter version 42.0-1ubuntu1 in updates
and then try adding this to /etc/environment:
MUTTER_DEBUG_DISABLE_TRIPLE_BUFFERING=1
MUTTER_DEBUG_USE_KMS_MODIFIERS=0
and then reboot.
If that fixes the bug then please try each line separately to identify
which one has
I wonder if this fix (coming in 42.rc) is needed?
https://gitlab.gnome.org/GNOME/mutter/-/commit/690b8806d
--
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/1966808
Title:
** Summary changed:
- [amdgpu][radeon] gnome-shell: Failed to lock front buffer on /dev/dri/card1:
drmModeAddFB2WithModifiers failed: Invalid argument
+ [amdgpu][radeon] gnome-shell Wayland sessions fail to start (Failed to lock
front buffer on /dev/dri/card1: drmModeAddFB2WithModifiers failed:
14 matches
Mail list logo
