Small progress trying to trace the root cause today:
I don't yet see gnome-shell doing anything wrong. It is reacting to an
infinite flood of workspace 'window-removed' signals. That signal can
only come from one function in mutter, and during the infinite flood I
see 'on_all_workspaces' is toggling between 0 and 1:
(gdb) bt
#0 meta_workspace_remove_window
(workspace=0x55a010a2d1d0, window=0x55a01135ce20)
at ../src/core/workspace.c:421
#1 0x00007fb5a3d5c40c in set_workspace_state
(window=0x55a01135ce20, on_all_workspaces=0, workspace=0x55a00eac8ea0)
at ../src/core/window.c:4635
#2 0x00007fb5a3d5f9b9 in meta_window_update_monitor
(window=window@entry=0x55a01135ce20,
flags=flags@entry=META_WINDOW_UPDATE_MONITOR_FLAGS_NONE) at
../src/core/window.c:3746
#3 0x00007fb5a3d5fcc6 in meta_window_move_resize_internal
(window=0x55a01135ce20, flags=(META_MOVE_RESIZE_MOVE_ACTION |
META_MOVE_RESIZE_RESIZE_ACTION), gravity=META_GRAVITY_NORTH_WEST,
frame_rect=...)
at ../src/core/window.c:3945
#4 0x00007fb5a49d3f60 in g_list_foreach ()
at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5 0x00007fb5a3d32d39 in move_resize
(display=<optimised out>, windows=0x55a00eb224e0 = {...})
at ../src/core/display.c:4044
#6 0x00007fb5a3d32c7e in window_queue_run_later_func
(user_data=<optimised out>) at ../src/core/display.c:4070
#7 0x00007fb5a3d24ff3 in invoke_later_idle (data=0x55a011660c00)
at ../src/compositor/meta-later.c:199
I'm not saying gnome-shell isn't to blame, just that I've only worked
back to mutter so far.
--
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/1976204
Title:
Screen freeze if a 4K monitor is added to a 4K laptop while DING is
active
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1976204/+subscriptions
--
desktop-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
