gnome-shell crashed with SIGABRT in __GI_raise()

Bug #1896440 reported by corrado venturini
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-shell (Ubuntu)
Incomplete
Medium
Unassigned

Bug Description

doing nothing, just firefox open.

corrado@corrado-n7-gg-0918:~$ inxi -Fxx
System: Host: corrado-n7-gg-0918 Kernel: 5.8.0-18-generic x86_64 bits: 64 compiler: N/A Desktop: N/A wm: gnome-shell
           dm: GDM3 Distro: Ubuntu 20.10 (Groovy Gorilla)
Machine: Type: Laptop System: Dell product: Inspiron 3793 v: N/A serial: <superuser/root required> Chassis: type: 10
           serial: <superuser/root required>
           Mobo: Dell model: 0C1PF2 v: A00 serial: <superuser/root required> UEFI: Dell v: 1.5.0 date: 12/17/2019
Battery: ID-1: BAT0 charge: 22.4 Wh condition: 37.1/42.0 Wh (88%) volts: 11.6/11.4 model: SWD-ATL3.618 DELL WJPC403
           serial: 6595 status: Discharging
CPU: Info: Quad Core model: Intel Core i5-1035G1 bits: 64 type: MT MCP arch: Ice Lake rev: 5 L2 cache: 6144 KiB
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 19046
           Speed: 1955 MHz min/max: 400/3600 MHz Core speeds (MHz): 1: 2931 2: 2788 3: 2444 4: 822 5: 2356 6: 3050 7: 3601
           8: 564
Graphics: Device-1: Intel Iris Plus Graphics G1 vendor: Dell driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:8a56
           Device-2: Realtek Integrated_Webcam_HD type: USB driver: uvcvideo bus ID: 1-6:3 chip ID: 0bda:5520
           Display: x11 server: X.Org 1.20.8 compositor: gnome-shell driver: modesetting unloaded: fbdev,vesa
           resolution: 1920x1080~60Hz s-dpi: 96
           OpenGL: renderer: Mesa Intel UHD Graphics (ICL GT1) v: 4.6 Mesa 20.1.7 direct render: Yes
Audio: Device-1: Intel Smart Sound Audio vendor: Dell driver: snd_hda_intel v: kernel bus ID: 00:1f.3 chip ID: 8086:34c8
           Sound Server: ALSA v: k5.8.0-18-generic
Network: Device-1: Realtek RTL810xE PCI Express Fast Ethernet vendor: Dell driver: r8169 v: kernel port: 3000
           bus ID: 01:00.0 chip ID: 10ec:8136
           IF: enp1s0 state: down mac: 98:e7:43:59:19:19
           Device-2: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter vendor: Dell driver: ath10k_pci v: kernel
           port: 3000 bus ID: 02:00.0 chip ID: 168c:0042
           IF: wlp2s0 state: up mac: d8:12:65:b8:21:b9
           Device-3: Qualcomm Atheros type: USB driver: btusb bus ID: 1-10:4 chip ID: 0cf3:e009
Drives: Local Storage: total: 476.94 GiB used: 8.05 GiB (1.7%)
           ID-1: /dev/nvme0n1 vendor: Toshiba model: KBG40ZNS512G NVMe KIOXIA 512GB size: 476.94 GiB speed: 31.6 Gb/s lanes: 4
           serial: 201PD3JEPTML
Partition: ID-1: / size: 31.25 GiB used: 8.00 GiB (25.6%) fs: ext4 dev: /dev/nvme0n1p7
Swap: ID-1: swap-1 type: partition size: 8.00 GiB used: 0 KiB (0.0%) priority: -2 dev: /dev/nvme0n1p2
Sensors: System Temperatures: cpu: 56.0 C mobo: N/A
           Fan Speeds (RPM): cpu: 0
Info: Processes: 250 Uptime: 1h 57m Memory: 7.55 GiB used: 1.50 GiB (19.8%) Init: systemd v: 246 runlevel: 5 Compilers:
           gcc: N/A Packages: 1827 apt: 1821 snap: 6 Shell: Bash v: 5.0.17 running in: gnome-terminal inxi: 3.1.06
corrado@corrado-n7-gg-0918:~$

ProblemType: Crash
DistroRelease: Ubuntu 20.10
Package: gnome-shell 3.37.91-1ubuntu1
ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
Uname: Linux 5.8.0-18-generic x86_64
ApportVersion: 2.20.11-0ubuntu45
Architecture: amd64
CasperMD5CheckResult: skip
CrashCounter: 1
CurrentDesktop: ubuntu:GNOME
Date: Mon Sep 21 08:40:37 2020
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
InstallationDate: Installed on 2020-09-18 (2 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200918.1)
ProcCmdline: /usr/bin/gnome-shell
RelatedPackageVersions: mutter-common 3.37.91-1ubuntu1
Signal: 6
SourcePackage: gnome-shell
StacktraceTop:
 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:49
 __GI_abort () at abort.c:79
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /usr/lib/gnome-shell/libst-1.0.so
Title: gnome-shell crashed with SIGABRT in __GI_raise()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
separator:

Revision history for this message
corrado venturini (corradoventu) wrote :
information type: Private → Public
tags: removed: need-amd64-retrace
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Thanks for the bug report. This looks like an assertion failure in libst-1.0.so but retracing has failed so we can't see exactly what happened.

Next time the problem happens, please:

1. Wait at least 5 seconds and then reboot.

2. Run this command in a terminal:

   journalctl -b-1 > prevboot.txt

   and then attach the resulting text file here.

Also, in case the same crash has already occurred multiple times, please try these instructions: https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment

Changed in gnome-shell (Ubuntu):
status: New → Incomplete
tags: added: need-amd64-retrace
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:49
 __GI_abort () at abort.c:79
 ?? () from /tmp/apport_sandbox_jvswt3b7/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.6600.0
 g_assertion_message_expr () from /tmp/apport_sandbox_jvswt3b7/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.6600.0
 st_bin_destroy () from /tmp/apport_sandbox_jvswt3b7/usr/lib/gnome-shell/libst-1.0.so

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 :

Looks like either bug 1898005 or bug 1898910.

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.