gnome-shell crashed with SIGABRT in dump_gjs_stack_on_signal_handler() from __GI_raise() from __GI_abort() from glibtop_error_io_vr() from glibtop_error_io_r() from file_to_buffer() from glibtop_get_cpu_s()

Bug #1753078 reported by shemgp
52
This bug affects 6 people
Affects Status Importance Assigned to Milestone
gnome-shell (Ubuntu)
Invalid
Medium
Unassigned
gnome-shell-extension-system-monitor (Ubuntu)
Confirmed
Medium
Unassigned
libgtop2 (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

https://errors.ubuntu.com/problem/a6be60a75215d699978e07692593d9cb3c403598

---

This error showed up after waking up the computer from sleep.

ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: gnome-shell 3.26.2-0ubuntu3
ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
Uname: Linux 4.15.0-10-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CrashCounter: 1
CurrentDesktop: GNOME
Date: Sat Mar 3 03:18:44 2018
DisplayManager: gdm3
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/gnome-shell
InstallationDate: Installed on 2015-09-28 (886 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
ProcCmdline: /usr/bin/gnome-shell
ProcEnviron:
 LANGUAGE=en_PH:en
 PATH=(custom, user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_PH.UTF-8
 SHELL=/bin/bash
Signal: 6
SourcePackage: gnome-shell
StacktraceTop:
 () at /usr/lib/x86_64-linux-gnu/libgtop-2.0.so.11
 () at /usr/lib/x86_64-linux-gnu/libgtop-2.0.so.11
 () at /usr/lib/x86_64-linux-gnu/libgtop-2.0.so.11
 () at /usr/lib/x86_64-linux-gnu/libgtop-2.0.so.11
 glibtop_get_cpu_l () at /usr/lib/x86_64-linux-gnu/libgtop-2.0.so.11
Title: gnome-shell crashed with SIGABRT
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip docker fuse kismet libvirt libvirtd lp lpadmin lxd mail mythtv netdev plugdev sambashare sbuild scanner sudo video

Revision history for this message
shemgp (shemgp) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51
 __GI_abort () at abort.c:90
 glibtop_error_io_vr (server=server@entry=0x7fbd765f93e0 <_glibtop_global_server>, format=format@entry=0x7fbd763f6305 "open (%s)", error=<optimized out>, args=args@entry=0x7ffd110b1e40) at error.c:103
 glibtop_error_io_r (server=server@entry=0x7fbd765f93e0 <_glibtop_global_server>, format=format@entry=0x7fbd763f6305 "open (%s)") at error.c:157
 file_to_buffer (server=server@entry=0x7fbd765f93e0 <_glibtop_global_server>, buffer=buffer@entry=0x7ffd110b1f60 "", bufsiz=bufsiz@entry=81920, filename=filename@entry=0x7fbd763f56fe "/proc/stat") at glibtop_private.c:130

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in gnome-shell (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

This looks like a new crash nobody has reported before. It also looks like it might be crashing in some kind of CPU-monitoring shell extension.

Please try removing/disabling your non-standard gnome-shell extensions. Please also let us know which system/CPU-monitoring shell extension(s) you are using and where they came from.

summary: - gnome-shell crashed with SIGABRT
+ gnome-shell crashed with SIGABRT in dump_gjs_stack_on_signal_handler()
+ from __GI_raise() from __GI_abort() from glibtop_error_io_vr() from
+ glibtop_error_io_r() from file_to_buffer() from glibtop_get_cpu_s()
information type: Private → Public
Changed in gnome-shell (Ubuntu):
status: New → Incomplete
Revision history for this message
shemgp (shemgp) wrote :

I think the extension that's monitoring the CPU, which I'm using, is this: https://extensions.gnome.org/extension/120/system-monitor/

None extension.gnome.org extension that I'm using is https://github.com/lestcape/Gnome-Global-AppMenu

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Thanks. I think I've found the related packages now. See above.

Changed in libgtop2 (Ubuntu):
importance: Undecided → Medium
Changed in gnome-shell (Ubuntu):
status: Incomplete → New
Changed in gnome-shell-extension-system-monitor (Ubuntu):
importance: Undecided → Medium
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in gnome-shell (Ubuntu):
status: New → Confirmed
Changed in gnome-shell-extension-system-monitor (Ubuntu):
status: New → Confirmed
Changed in libgtop2 (Ubuntu):
status: New → Confirmed
tags: added: rls-bb-incoming
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

I don't think rls-bb-incoming is appropriate here, because this bug is caused by a non-default extension being installed.

Revision history for this message
Jean-Baptiste Lallement (jibel) wrote :

Agreed and after verification I didn't find any occurrence of this crash in errors.u.c

tags: removed: rls-bb-incoming
tags: added: cosmic
description: updated
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Invalid for gnome-shell. This is an extension bug.

Changed in gnome-shell (Ubuntu):
status: Confirmed → Invalid
description: updated
description: updated
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Also tracking in:
https://errors.ubuntu.com/problem/a6be60a75215d699978e07692593d9cb3c403598

with 1591 crash reports on 18.04 systems so far.

Someone please report this bug to the author(s) of gnome-shell-extension-system-monitor.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.