[Bug 1976204] Re: System freeze
If your log still gets flooded with messages then there's a good chance that's the reason why gnome-shell is not responding. Only the "stack trace" info is usually irrelevant. If you get a freeze without a flood of log messages then we should put mutter in debug mode via /etc/environment: MUTTER_DEBUG=kms and then see what messages get logged at the time of the freeze. -- 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 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1976204/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1976204] Re: System freeze
Sorry, connect type-c monitor directly without docking can also reproduce this issue. -- 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: System freeze To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1976204/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1976204] Re: System freeze
Also the flood of log messages seen in comment #2 is tracked in bug 1908429. -- 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: System freeze To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1976204/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1976204] Re: System freeze
Since you mention DA310 and WD19TB, I am reminded of bug 1960865 and bug 1970495. -- 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: System freeze To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1976204/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1976204] Re: System freeze
Since Javascript stack traces are hardly ever related to freezes, and particularly if there are multiple of them, I've removed mention of the stack traces. ** Summary changed: - system freeze and gnome-shell reports multiple stack trace + System freeze -- 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: System freeze To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1976204/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1976204] Re: system freeze and gnome-shell reports multiple stack trace
** Description changed: [Summary] The system will run into freeze if I connect the external monitor through DP/HDMI with dongle DA310 or Docking WD19TB [Steps to reproduce] 1. Attact DA310 or WD19TB to DUT 2. Cold Boot into OS 3. Plug the DP/HDMI cable to DA310 or WD19TB 4. Check the external monitor has signal 5. Click keyboard or move mouse to check system can work well [Expected result] System won't be freeze with external monitor. [Actual result] - System will be freeze. + Screen will freeze, but ssh can still reach out DUT. Keyboard and mouse + don't work during the screen freeze. It can be recovered after unplug the external monitor sometime. [gnome-shell stack trace] - 五 27 22:12:31 ubuntu-XPS-9320 gnome-shell[1998]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). - 五 27 22:12:31 ubuntu-XPS-9320 gnome-shell[1998]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e). - 五 27 22:12:31 ubuntu-XPS-9320 gnome-shell[1998]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c). - 五 27 22:12:31 ubuntu-XPS-9320 gnome-shell[1998]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed - 五 27 22:12:55 ubuntu-XPS-9320 sudo[2916]: ubuntu : TTY=pts/2 ; PWD=/home/ubuntu ; USER=root ; COMMAND=/usr/bin/dmesg - 五 27 22:12:55 ubuntu-XPS-9320 sudo[2916]: pam_unix(sudo:session): session opened for user root(uid=0) by ubuntu(uid=1001) - 五 27 22:12:55 ubuntu-XPS-9320 sudo[2916]: pam_unix(sudo:session): session closed for user root - 五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. - 五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: == Stack trace for context 0x56156f8f04a0 == - 五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: == Stack trace for context 0x56156f8f04a0 == - 五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: The offending signal was window-added on MetaWorkspace 0x56156f916640. - 五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. - 五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: The offending signal was window-added on MetaWorkspace 0x56156f916640. - 五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. + 五 27 22:12:31 ubuntu-XPS-9320 gnome-shell[1998]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). + 五 27 22:12:31 ubuntu-XPS-9320 gnome-shell[1998]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e). + 五 27 22:12:31 ubuntu-XPS-9320 gnome-shell[1998]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c). + 五 27 22:12:31 ubuntu-XPS-9320 gnome-shell[1998]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed + 五 27 22:12:55 ubuntu-XPS-9320 sudo[2916]: ubuntu : TTY=pts/2 ; PWD=/home/ubuntu ; USER=root ; COMMAND=/usr/bin/dmesg + 五 27 22:12:55 ubuntu-XPS-9320 sudo[2916]: pam_unix(sudo:session): session opened for user root(uid=0) by ubuntu(uid=1001) + 五 27 22:12:55 ubuntu-XPS-9320 sudo[2916]: pam_unix(sudo:session): session closed for user root + 五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. + 五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: == Stack trace for context 0x56156f8f04a0 == + 五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: == Stack trace for context 0x56156f8f04a0 == + 五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: The offending signal was window-added on MetaWorkspace 0x56156f916640.
[Bug 1976204] Re: system freeze and gnome-shell reports multiple stack trace
I add commit mentioned in #13 to build mutter packages. https://launchpad.net/~kchsieh/+archive/ubuntu/verification/ It doesn't help the issue. -- 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: system freeze and gnome-shell reports multiple stack trace To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1976204/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1976204] Re: system freeze and gnome-shell reports multiple stack trace
Some updates here: The shell isn't really hanging... The fact is that the input/output GLib Sources that the shell adds to the main context are starving and never processed because we add thousands of timeouts and `Meta.Later` sources as per a `window-removed` signal that is triggered thousand times (source is actually `[gnome-shell] this._queueCheckWorkspaces`). This leads to CPU being 100% spending time in processing such sources (https://usercontent.irccloud-cdn.com/file/v1ZGs5f6/image.png) thousands of GSources being added: https://i.imgur.com/QUuuZA1.png And these are added via https://usercontent.irccloud- cdn.com/file/V4jfRY94/with%20laters%20added%20at that sends the window- removed signal (https://i.imgur.com/PNBn6Cv.png). Now, it seems possible that the fixes part of 42.2 in https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2413 fix this case. But we still need to test that. -- 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: system freeze and gnome-shell reports multiple stack trace To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1976204/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1976204] Re: system freeze and gnome-shell reports multiple stack trace
** Also affects: mutter (Ubuntu) Importance: Undecided Status: New -- 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/1976204 Title: system freeze and gnome-shell reports multiple stack trace To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1976204/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1976204] Re: system freeze and gnome-shell reports multiple stack trace
I use `thread apply all bt full` to capture the gdb debug message and use `journalctl -b 0 /usr/bin/gnome-shell` to capture journal log. ** Attachment added: "gnome-shell-stack-trace-202206062108.tar.gz" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1976204/+attachment/5595073/+files/gnome-shell-stack-trace-202206062108.tar.gz -- 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/1976204 Title: system freeze and gnome-shell reports multiple stack trace To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1976204/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1976204] Re: system freeze and gnome-shell reports multiple stack trace
So, attaching with gdb should happen when it's hanging, assuming that's the case I still don't see the result for `bt full` (or better `thread apply all bt full`), so that we can try to figure out where the process is hanging. As per the JS stack the one I see in logs is: 六 06 16:11:11 ubuntu-XPS-13-9310 gnome-shell[1071]: == Stack trace for context 0x5557c18144b0 == 六 06 16:11:11 ubuntu-XPS-13-9310 gnome-shell[1071]: #0 7fffd9616ef0 I resource:///org/gnome/shell/ui/workspace.js:820 (e45d6bfdbf0 @ 274) 六 06 16:11:11 ubuntu-XPS-13-9310 gnome-shell[1071]: #1 7fffd9616f80 I resource:///org/gnome/shell/ui/workspace.js:1409 (47907707d80 @ 264) 六 06 16:11:11 ubuntu-XPS-13-9310 gnome-shell[1071]: #2 7fffd9616ff0 I resource:///org/gnome/shell/ui/workspace.js:1274 (47907707830 @ 465) 六 06 16:11:11 ubuntu-XPS-13-9310 gnome-shell[1071]: #3 7fffd9617030 I resource:///org/gnome/shell/ui/workspace.js:1298 (479077079c0 @ 45) 六 06 16:11:11 ubuntu-XPS-13-9310 gnome-shell[1071]: #4 7fffd9617080 I self-hosted:1181 (3a3c201b0a10 @ 454) -- 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/1976204 Title: system freeze and gnome-shell reports multiple stack trace To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1976204/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1976204] Re: system freeze and gnome-shell reports multiple stack trace
Hi @3v1n0, [steps] 1. Install gnome-shell-dbgsym_42.1-0ubuntu0.1_amd64.ddeb, libglib2.0-dev-bin-dbgsym_2.72.1-1_amd64.ddeb, libmutter-test-10-dbgsym_42.1-0ubuntu1_amd64.ddeb, libglib2.0-0-dbgsym_2.72.1-1_amd64.ddeb, libglib2.0-tests-dbgsym_2.72.1-1_amd64.ddeb, mutter-10-tests-dbgsym_42.1-0ubuntu1_amd64.ddeb, libglib2.0-bin-dbgsym_2.72.1-1_amd64.ddeb, libmutter-10-0-dbgsym_42.1-0ubuntu1_amd64.ddeb and mutter-dbgsym_42.1-0ubuntu1_amd64.ddeb 2. Plug external monitor 3. Execute `sudo gdb -p $(pidof /usr/bin/gnome-shell) /usr/bin/gnome-shell` 4. Ctrl+C and `bt` 5. `call (void) gjs_dumpstack()` [journal log] 六 06 16:23:27 ubuntu-XPS-13-9310 gnome-shell[1071]: The offending callback was SourceFunc(). 六 06 16:23:27 ubuntu-XPS-13-9310 gnome-shell[1071]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter a ctor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked . ** Attachment added: "20220606-gnome-shell.log.tar.gz" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1976204/+attachment/5595044/+files/20220606-gnome-shell.log.tar.gz -- 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/1976204 Title: system freeze and gnome-shell reports multiple stack trace To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1976204/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1976204] Re: system freeze and gnome-shell reports multiple stack trace
It would be relevant to understand where gnome-shell freezes. So please once you've installed the debug symbols of gnome-shell, mutter and glib do: sudo gdb -p $(pidof /usr/bin/gnome-shell) /usr/bin/gnome-shell Then there Ctrl+C and `bt`. Also do: `call (void) gjs_dumpstack()` And you should find where the shell is hanging on JS side reading the shell journal. -- 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/1976204 Title: system freeze and gnome-shell reports multiple stack trace To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1976204/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1976204] Re: system freeze and gnome-shell reports multiple stack trace
** Also affects: gnome-shell-extension-desktop-icons-ng (Ubuntu) Importance: Undecided Status: New -- 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/1976204 Title: system freeze and gnome-shell reports multiple stack trace To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1976204/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1976204] Re: system freeze and gnome-shell reports multiple stack trace
If I remove gnome-shell-extension-desktop-icons-ng, I can't reproduce this issue. Also I can't reproduce this issue under x-session. -- 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/1976204 Title: system freeze and gnome-shell reports multiple stack trace To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1976204/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1976204] Re: system freeze and gnome-shell reports multiple stack trace
apport information ** Tags added: apport-collected jammy wayland-session ** Description changed: [Summary] The system will run into freeze if I connect the external monitor through DP/HDMI with dongle DA310 or Docking WD19TB [Steps to reproduce] 1. Attact DA310 or WD19TB to DUT 2. Cold Boot into OS 3. Plug the DP/HDMI cable to DA310 or WD19TB 4. Check the external monitor has signal 5. Click keyboard or move mouse to check system can work well [Expected result] System won't be freeze with external monitor. [Actual result] System will be freeze. It can be recovered after unplug the external monitor sometime. [gnome-shell stack trace] 五 27 22:12:31 ubuntu-XPS-9320 gnome-shell[1998]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). 五 27 22:12:31 ubuntu-XPS-9320 gnome-shell[1998]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e). 五 27 22:12:31 ubuntu-XPS-9320 gnome-shell[1998]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c). 五 27 22:12:31 ubuntu-XPS-9320 gnome-shell[1998]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed 五 27 22:12:55 ubuntu-XPS-9320 sudo[2916]: ubuntu : TTY=pts/2 ; PWD=/home/ubuntu ; USER=root ; COMMAND=/usr/bin/dmesg 五 27 22:12:55 ubuntu-XPS-9320 sudo[2916]: pam_unix(sudo:session): session opened for user root(uid=0) by ubuntu(uid=1001) 五 27 22:12:55 ubuntu-XPS-9320 sudo[2916]: pam_unix(sudo:session): session closed for user root 五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. 五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: == Stack trace for context 0x56156f8f04a0 == 五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: == Stack trace for context 0x56156f8f04a0 == 五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: The offending signal was window-added on MetaWorkspace 0x56156f916640. 五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. 五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: The offending signal was window-added on MetaWorkspace 0x56156f916640. 五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. - This system is using OLED (3456x2160) panel, and I can't reproduce this - issue on FHD panel. + This system is using OLED (3456x2160) panel, and I can't reproduce this issue on FHD panel. + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu82.1 + Architecture: amd64 + CasperMD5CheckResult: pass + CurrentDesktop: ubuntu:GNOME + DisplayManager: gdm3 + DistroRelease: Ubuntu 22.04 + InstallationDate: Installed on 2022-03-17 (75 days ago) + InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313) + Package: gnome-shell 42.1-0ubuntu0.1 + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 5.15.0-35.36-generic 5.15.35 + RelatedPackageVersions: mutter-common 42.0-3ubuntu2 + Tags: jammy wayland-session + Uname: Linux 5.15.0-35-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1976204/+attachment/5594174/+files/Dependencies.txt -- 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/1976204 Title: system freeze and gnome-shell reports multiple stack trace To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1976204/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1976204] Re: system freeze and gnome-shell reports multiple stack trace
** Attachment added: "syslog.log.tar.gz" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1976204/+attachment/5593680/+files/syslog.log.tar.gz -- 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/1976204 Title: system freeze and gnome-shell reports multiple stack trace To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1976204/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1976204] Re: system freeze and gnome-shell reports multiple stack trace
** Tags added: oem-priority originate-from-1967530 somerville ** Changed in: oem-priority Status: New => Confirmed ** Changed in: oem-priority Importance: Undecided => Critical ** Changed in: oem-priority Assignee: (unassigned) => Andy Chi (andch) -- 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/1976204 Title: system freeze and gnome-shell reports multiple stack trace To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1976204/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1976204] Re: system freeze and gnome-shell reports multiple stack trace
** Tags added: jellyfish-edge-staging -- 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/1976204 Title: system freeze and gnome-shell reports multiple stack trace To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1976204/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs