Hi Daniel,
Thank you for your reply
Before checking your solution I tested again to be sure the issue still exists
and it seems that the issue has been fixed. Since the bug submission there were
a few updates that might have fixed it directly or indirectly:
* a kernel update
* a thunderbolt (do
Public bug reported:
When I connect the external monitor the image is shown on the external
display but it freezes (on both displays); after I unplug the external
display the following errors are logged (not sure it is related to the
freeze):
Jul 5 09:19:39 xps gnome-shell[10252]: meta_display_g
*** This bug is a duplicate of bug 1979244 ***
https://bugs.launchpad.net/bugs/1979244
Hi Jeremy! Is there any workaround for this issue? I have a laptop that
is not starting the gmd session anymore and on with gdm3 reconfigure I
get the same broken package error.
--
You received this bug no
Setting MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0 also works for me (XPS 9500).
Furthermore, it fixes also the Night Light feature.
Thank you Daniel!
--
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/
Thank you Daniel!
I have added the bug information here:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1978534
--
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/1967274
Tit
Public bug reported:
Screen wont wake up using mouse or keyboard. The only way to wake it up
is to use CTRL+ALT+F1.
The behavior is similar to the one for this bug:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1967274
The following is the log while this situation occurs:
Jun 14 10:30:1
I am using kernel v5.15.0-37 but I am still affected by this bug on my
XPS 15 (9500). Installed mutter is 42.1.
Also, the Night Light is not working (I saw some references in this
thread about this feature).
Is there anything else I must update on my system to have it working
properly?
Thanks!
Hi,
I have encountered the same issue after upgrading to Ubuntu 22.04.
For me the fix was to reinstall the `gstreamer1.0-pipewire` package.
`sudo apt reinstall gstreamer1.0-pipewire`
Regards
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscr
OMFG, being an Ubuntu (patched Nautilus that is) user for more than 9
years I thought this was a bug with 17.10 and patiently waited for a fix
... can't agree more with "complete idiots"
This is not a huge, complex and hard to maintain feature that you just
decide it is too difficult to support. I
