This bug was fixed in the package mutter - 45.0-2ubuntu1
---
mutter (45.0-2ubuntu1) mantic; urgency=medium
* Merge with Debian. Remaining changes:
- Add x11-Add-support-for-fractional-scaling-using-Randr.patch
- Add window-Add-ability-to-override-the-edge-constraints.patch
https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1441#note_1851306
** Changed in: mutter (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
--
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/2035016
Title:
one of 3 monitors "frozen" when a window moves there
To manage notifications about this bug go to:
I managed to finally reproduce this by accident:
1. Set up 3 monitors.
2. Fullscreen a window on one of them.
3. The monitor with the fullscreen window accidentally lost HDMI
connection. When plugged back in it was frozen.
** Changed in: mutter (Ubuntu)
Status: Incomplete => In
Here's another journal from the boot after the one before, with the same
settings as before (I've set MUTTER_DEBUG_TRIPLE_BUFFERING=never but not
yet rebooted).
My primary display should have multiple hangs in the last couple of
minutes here. I unwisely fullscreened a YouTube video in Firefox,
I was distracted by https://gitlab.gnome.org/GNOME/mutter/-/issues/3035
so I haven't had time to test this as much...
** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #3035
https://gitlab.gnome.org/GNOME/mutter/-/issues/3035
--
You received this bug notification because you are a
Interesting, thats 3 monitors on an Intel GPU. I can't see any errors
that would lead to a freeze, but the second last CRTC to be used there
(CRTC 182) does seem to have been using fullscreen direct scanout on its
last frame. It also looks like mutter is intending to display the cursor
on that
** Attachment added: "journal from a single-display hang with
gnome-shell/(lib)mutter 45.0-1ubuntu1, Alder Lake-P, two external displays
through an MST hub, with MUTTER_DEBUG=kms MUTTER_DEBUG_KMS_THREAD_TYPE=user"
** Attachment added: "journal from a single-display hang with
gnome-shell/(lib)mutter 45.0-1ubuntu1, Alder Lake-P, two external displays
through an MST hub"
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2035016/+attachment/5702587/+files/journal-redacted.txt
** Attachment removed:
Everyone please also try this in /etc/environment by itself:
MUTTER_DEBUG_KMS_THREAD_TYPE=user
and then reboot.
--
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/2035016
Title:
Although I might be assuming too much because if the bug happened 2
seconds before the log in comment #26 then there's nothing about it
being logged. That's normal for freezes. In that case we need to enable
full debug mode in /etc/environment:
MUTTER_DEBUG=kms
reboot and then next time a
Both of those logs contain the same warning from the kernel graphics
code:
WARNING: CPU: 12 PID: 148 at drivers/gpu/drm/drm_mode_object.c:45
drm_mode_object_add+0x99/0xa0 [drm]
whose call trace seems to be related to DisplayPort, MST (multi-stream
transport) and hotplugging.
We should assume
And it happened again after I unplugged and plugged my usb-c->display
port cable . looks like this time there's more useful information in the
logs.
** Attachment added: "journal.txt after unplug/plug the display port cable with
mutter (45.0-1ubuntu1)"
with latest mutter+gnome-shell (single GPU), this still happens. log
attached.
** Attachment added: "journal.txt from current boot 2 seconds after the problem
occured with mutter (45.0-1ubuntu1)"
I have experienced this (or something very like this) a few times on my
t14 amd gen 3, which does not have dual GPUs. I only updated to
libmutter 45 this morning though.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in
Before we proceed, please ensure your system has been updated to
libmutter >= 45.0 because I haven't personally been able to reproduce
any freezes like this for a few weeks (using the latest upstream code
which is now in 45.0).
--
You received this bug notification because you are a member of
"Fullscreen" sounds like an important factor. Indeed to monitors without
a panel, simply maximizing a window makes it fullscreen. Another
potentially important factor is whether your machine has dual GPUs. This
information helps me to narrow down where to look.
** Tags added: triple-buffering
The updated gnome-shell & mutter are out of proposed.
--
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/2035016
Title:
one of 3 monitors "frozen" when a window moves there
To manage
It's very easy to reproduce for me, it happens very quickly every time
when I put a fullscreen window on the second monitor. I can probably get
a some logs later...
But perhaps wait until the updated mutter & gnome-shell are out of
Proposed?
--
You received this bug notification because you are
Each time the problem happens please immediately run:
journalctl -b0 > journal.txt
and attach the resulting text file here.
--
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/2035016
Hmm, actually I think some issues still remain. I will file a bug of my
own later to try to provide more data.
--
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/2035016
Title:
one of
We believe this issue is fixed or significantly improved with GNOME
Shell 45.0, Mutter 45.0, and glib 2.78.0-2 which should land in mantic
soon. Please file a new bug if you are still experiencing problems after
upgrading to these new versions and restarting your computer.
** Package changed:
Still happens when I have only MUTTER_DEBUG_KMS_THREAD_TYPE=user.
TRIPLE_BUFFERING=never seems to be the only workaround.
Hope we can get a new snapshot in Mantic soon then!
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
I think there are fixes in both mutter 45.0 main and upstream in the
triple buffering branch (not yet in mantic) that might help with this.
Certainly when I spent a whole day stress testing them with multiple
monitors on Friday I could no longer reproduce any freeze.
--
You received this bug
I have been running with MUTTER_DEBUG_TRIPLE_BUFFERING=never as my only
debug option since last I wrote and haven't been able to reproduce it.
So I'll try the KMS_THREAD_TYPE now.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
Actually please try MUTTER_DEBUG_KMS_THREAD_TYPE=user instead of all the
above.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/2035016
Title:
one of 3 monitors "frozen" when a
MUTTER_DEBUG_DISABLE_TRIPLE_BUFFERING is deprecated and is replaced by:
MUTTER_DEBUG_TRIPLE_BUFFERING=never
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/2035016
Title:
I got it again now with
$HOME/.config/environment.d/debug.conf :
MUTTER_DEBUG_DISABLE_TRIPLE_BUFFERING=1
MUTTER_DEBUG_FORCE_KMS_MODE=simple
Of course, all the triple buffering patches are still there. Haven't
tried vanilla mutter/gnome-shell yet.
--
You received this bug notification because
Assuming the problem is a low level graphics freeze it may be related to this
issue in progress:
https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1441#note_1806246
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in
The log in comment #6 suggests the cause is in gnome-shell's window
management:
JS ERROR: TypeError: this.actor is null
_syncEnabled@resource:///org/gnome/shell/ui/windowManager.js:145:25
onStopped@resource:///org/gnome/shell/ui/windowManager.js:157:35
Now this happened again with MUTTER_DEBUG_FORCE_KMS_MODE=simple set.
I'm going to try to disable extensions instead...
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/2035016
This happened to me with both Nvidia and AMD graphics.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/2035016
Title:
one of 3 monitors "frozen" when a window moves there
To
> Please try adding this to /etc/environment as a workaround:
> MUTTER_DEBUG_FORCE_KMS_MODE=simple
this seem to help. and it also helps for having the mouse pointer in
firefox working again (I filled
https://bugzilla.mozilla.org/show_bug.cgi?id=1852519 for that)
Does that have any negative
** Attachment added: "journal.txt from current boot 2 seconds after the problem
occured"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2035016/+attachment/5699911/+files/journal.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
@Daniel, what exactly do you need from the journal? I don't want to post
the full output here. it contains some private user sessions services
output which I don't want to share.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
Also next time the problem happens please immediately run:
journalctl -b0 > journal.txt
and attach the resulting text file here.
** Changed in: gnome-shell (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
Please try adding this to /etc/environment as a workaround:
MUTTER_DEBUG_FORCE_KMS_MODE=simple
and then reboot.
** Tags added: amdgpu
** Tags added: multimonitor
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnome-shell (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
38 matches
Mail list logo
