Steve, IIRC this crash was fixed by *either* the gnome-shell or extension fix. So the original test case would fail only while *neither* of the two fixes were applied.
The gnome-shell fix made the shell API more robust so as to protect itself from crashing in the presence of a buggy extension. The gnome-shell-extension-desktop-icons fix corrects the buggy extension. This is still worthwhile because it fixes a sudden and unnecessary spike of memory and CPU usage from unthrottled timer duplication. That IIRC could still cause instability in the extension/shell based on my memory of testing a year ago. However I've tried stress testing both with and without the fix on focal today and can't see any practical difference in performance. Only technically we shouldn't declare the fix as "released" until the series file is corrected to apply the patch. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1898005 Title: gnome-shell crashed with SIGABRT in st_bin_destroy: assertion failed: (priv->child == NULL) called from DesktopManager::_destroyDesktopIcons() [desktopManager.js:234] Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell-extension-desktop-icons package in Ubuntu: Fix Released Status in gnome-shell source package in Focal: Fix Released Status in gnome-shell-extension-desktop-icons source package in Focal: Incomplete Status in gnome-shell source package in Groovy: Fix Released Status in gnome-shell-extension-desktop-icons source package in Groovy: Fix Released Status in gnome-shell source package in Hirsute: Fix Released Status in gnome-shell-extension-desktop-icons source package in Hirsute: Fix Released Bug description: [Impact] Gnome Shell crashes at random times when the Desktop or home directory is modified, and the desktop-icons extension tries to refresh. https://errors.ubuntu.com/problem/fcc5c581fc0a8c2f8f68314fa383690423a3dc02 [Test Case] Open a nautilus (Files) window and tap Ctrl+H repeatedly. The shell should not crash or freeze. [Where problems could occur] An extension with syntax errors may fail to load leaving the user with reduced shell functionality. A more faulty extension might crash the entire shell after loading, like this bug. [Other Info] See also bug 1898910 --- Sorry, I missed what was happening when this crashed. I'll try to catch it next time. ProblemType: Crash DistroRelease: Ubuntu 20.10 Package: gnome-shell 3.38.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4 Uname: Linux 5.8.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu48 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Sep 30 08:38:45 2020 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=en_CA.UTF-8 LANGUAGE=en_CA:en PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR=<set> RelatedPackageVersions: mutter-common 3.38.0-1ubuntu1 Signal: 6 SourcePackage: gnome-shell StacktraceTop: () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 () at /usr/lib/gnome-shell/libst-1.0.so g_closure_invoke () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-shell crashed with SIGABRT UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1898005/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
