CRITICAL gnome-shell error: segfault error 4 in libmozjs-60.so.0.0.0

[jean-christophe manciot]

Ubuntu 18.10
gnome-shell 3.30.1-2ubuntu1
libmozjs-60-0 60.2.3-1

From /var/log/syslog:
...
Oct 29 13:50:40 samsung5-ubuntu gnome-shell[4827]: g_dir_open_with_errno: assertion 'path != NULL' failed
Oct 29 13:50:40 samsung5-ubuntu gnome-shell[4827]: g_filename_to_utf8: assertion 'opsysstring != NULL' failed
Oct 29 13:50:40 samsung5-ubuntu gnome-shell[4827]: JS WARNING: [resource:///org/gnome/shell/ui/status/system.js 268]: reference to undefined property "names"
Oct 29 13:50:40 samsung5-ubuntu gnome-shell[4827]: JS ERROR: TypeError: app.app_info.get_icon(...).names is undefined#012_createSubMenu@resource:///org/gnome/shell/ui/status/system.js:268:33#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22#012_init@resource:///org/gnome/shell/ui/status/system.js:126:9#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22#012_Base.prototype._construct@resource:///org/gnome/gjs/modules/_legacy.js:18:5#012newClass@resource:///org/gnome/gjs/modules/_legacy.js:114:32#012_init@resource:///org/gnome/shell/ui/panel.js:721:24#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22#012_Base.prototype._construct@resource:///org/gnome/gjs/modules/_legacy.js:18:5#012newClass@resource:///org/gnome/gjs/modules/_legacy.js:114:32#012_ensureIndicator@resource:///org/gnome/shell/ui/panel.js:1132:25#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22#012_updateBox@resource:///org/gnome/shell/ui/panel.js:1143:29#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22#012_updatePanel@resource:///org/gnome/shell/ui/panel.js:1053:9#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22#012_init@resource:///org/gnome/shell/ui/panel.js:831:9#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22#012_Base.prototype._construct@resource:///org/gnome/gjs/modules/_legacy.js:18:5#012newClass@resource:///org/gnome/gjs/modules/_legacy.js:114:32#012_initializeUI@resource:///org/gnome/shell/ui/main.js:187:13#012start@resource:///org/gnome/shell/ui/main.js:136:5#012@<main>:1:31
Oct 29 13:50:40 samsung5-ubuntu gnome-shell[4827]: Execution of main.js threw exception: Script <main> threw an exception
Oct 29 13:50:40 samsung5-ubuntu kernel: [ 34.380764] gnome-shell[4827]: segfault at 168 ip 00007ffb177078ae sp 00007ffcb7739a00 error 4 in libmozjs-60.so.0.0.0[7ffb1767b000+709000]
Oct 29 13:50:40 samsung5-ubuntu kernel: [ 34.380769] Code: fe ff ff 49 8b 54 24 40 48 89 95 a8 fe ff ff 48 8d 9d a0 fe ff ff 49 89 5c 24 40 49 8b 94 24 a8 00 00 00 48 8b 92 c8 2a 00 00 <48> 3b 82 68 01 00 00 0f 84 a3 66 00 00 49 8b 45 f8 48 89 85 f0 fe
Oct 29 13:50:40 samsung5-ubuntu gnome-session[4565]: gnome-session-binary[4565]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 11
Oct 29 13:50:40 samsung5-ubuntu gnome-session[4565]: gnome-session-binary[4565]: WARNING: App 'org.gnome.Shell.desktop' respawning too quickly
Oct 29 13:50:40 samsung5-ubuntu gnome-session-binary[4565]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 11
Oct 29 13:50:40 samsung5-ubuntu gnome-session-binary[4565]: Unrecoverable failure in required component org.gnome.Shell.desktop
Oct 29 13:50:40 samsung5-ubuntu gnome-session[4565]: gnome-session-binary[4565]: CRITICAL: We failed, but the fail whale is dead. Sorry....
Oct 29 13:50:40 samsung5-ubuntu gnome-session-binary[4565]: WARNING: App 'org.gnome.Shell.desktop' respawning too quickly
Oct 29 13:50:40 samsung5-ubuntu gnome-session-binary[4565]: CRITICAL: We failed, but the fail whale is dead. Sorry....
Oct 29 13:50:40 samsung5-ubuntu at-spi-bus-launcher[4567]: XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0"
...

I tried to uninstall all gnome-shell-extensions packages, but the behavior is exactly the same.

[jean-christophe manciot (manciot-jeanchristophe)]

On a different Cosmic platform, the symptoms are a little bit different: "traps: gnome-shell general protection error:0 in libglib-2.0.so.0.5800.1"
...
Oct 28 22:00:24 msi-ge60-ubuntu kernel: [ 77.307798] traps: gnome-shell[4865] general protection ip:7f7b32927c00 sp:7fff46026330 error:0 in libglib-2.0.so.0.5800.1[7f7b32907000+7d000]
Oct 28 22:00:25 msi-ge60-ubuntu gnome-session[4202]: gnome-session-binary[4202]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 11
Oct 28 22:00:25 msi-ge60-ubuntu gnome-session[4202]: gnome-session-binary[4202]: WARNING: App 'org.gnome.Shell.desktop' respawning too quickly
Oct 28 22:00:25 msi-ge60-ubuntu kernel: [ 77.469526] rfkill: input handler enabled
Oct 28 22:00:25 msi-ge60-ubuntu gnome-session[4202]: gnome-session-binary[4202]: CRITICAL: We failed, but the fail whale is dead. Sorry....
Oct 28 22:00:25 msi-ge60-ubuntu gnome-session-binary[4202]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 11
Oct 28 22:00:25 msi-ge60-ubuntu gnome-session-binary[4202]: Unrecoverable failure in required component org.gnome.Shell.desktop
Oct 28 22:00:25 msi-ge60-ubuntu pulseaudio[4495]: ICE default IO error handler doing an exit(), pid = 4495, errno = 11
Oct 28 22:00:25 msi-ge60-ubuntu kdeconnectd.desktop[4721]: ICE default IO error handler doing an exit(), pid = 4721, errno = 11
Oct 28 22:00:25 msi-ge60-ubuntu at-spi-bus-launcher[4444]: XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":1"

[Daniel van Vugt (vanvugt)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps:

1. Look in /var/crash for crash files and if found run:
    ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.

2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us.

3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1.

Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself.

[jean-christophe manciot (manciot-jeanchristophe)]

1. When I try "ubuntu-bug crashfile.crash" to send the report, the screen becomes endlessly filled with dots.
2. The last report is 2 years old.
3. - Applying workaround (commenting out line 23 ("'problem_types': ['Bug', 'Package'],") in '/etc/apport/crashdb.conf')
   - rebooting & crashing (no login)
   - rebooting in recovery mode
   - realizing that no new crash file has been generated
   - apt install python-launchpadlib to solve issue from first step
   - ubuntu-bug /var/crash/crashfile.crash

It has been privately reported as "gnome-control-center crashed with SIGABRT".

[jean-christophe manciot (manciot-jeanchristophe)]

Upgrading to disco 19.04 does not solve the issue.

[Launchpad Janitor (janitor)]

[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.]

[Daniel van Vugt (vanvugt)]

> It has been privately reported as "gnome-control-center crashed with SIGABRT".

Can you please tell us the bug ID? I can't seem to find any recent bug by that title.