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 se
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/19
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.
h
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
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, w
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 s
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, a
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 wi
