gnome-shell crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup_node()

Bug #1765686 reported by Togo28
34
This bug affects 3 people
Affects Status Importance Assigned to Milestone
glib2.0 (Ubuntu)
Fix Released
Undecided
Marco Trevisan (Treviño)
gnome-shell (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

https://errors.ubuntu.com/problem/87e4666825764619cb47f3837f871d88d65dd606

---

It seems to be reproduceable, if I load a wider filearea with different filesystems (ntfs and ext4)

ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: gnome-shell 3.28.1-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
Uname: Linux 4.15.0-15-generic x86_64
ApportVersion: 2.20.9-0ubuntu5
Architecture: amd64
CurrentDesktop: GNOME-Greeter:GNOME
Date: Fri Apr 20 12:36:08 2018
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
GsettingsChanges:

InstallationDate: Installed on 2018-03-23 (27 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180321)
ProcCmdline: /usr/bin/gnome-shell
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=de_DE.UTF-8
 SHELL=/bin/false
SegvAnalysis:
 Segfault happened at: 0x7fd13cdc0430 <g_str_hash>: movsbl (%rdi),%edx
 PC (0x7fd13cdc0430) ok
 source "(%rdi)" (0x000000ca) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-shell
StacktraceTop:
 g_str_hash () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_hash_table_lookup () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 g_main_context_dispatch () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: gnome-shell crashed with SIGSEGV in g_str_hash()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

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

StacktraceTop:
 g_str_hash (v=0xca) at ../../../../glib/ghash.c:1894
 g_hash_table_lookup_node (hash_return=<synthetic pointer>, key=0xca, hash_table=0x7fd11804f800) at ../../../../glib/ghash.c:379
 g_hash_table_lookup (hash_table=0x7fd11804f800, key=0xca) at ../../../../glib/ghash.c:1153
 emit_signal_instance_in_idle_cb (data=0x7fd118012730) at ../../../../gio/gdbusconnection.c:3714
 g_main_dispatch (context=0x564d6d8f95f0) at ../../../../glib/gmain.c:3177

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
Launchpad Janitor (janitor) wrote : Re: gnome-shell crashed with SIGSEGV in g_str_hash()

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

Changed in gnome-shell (Ubuntu):
status: New → Confirmed
summary: - gnome-shell crashed with SIGSEGV in g_str_hash()
+ gnome-shell crashed with SIGSEGV in g_str_hash() from
+ g_hash_table_lookup_node()
information type: Private → Public
Revision history for this message
Daniel van Vugt (vanvugt) wrote :
description: updated
Changed in gnome-shell (Ubuntu):
status: Confirmed → Triaged
Changed in glib (Ubuntu):
status: New → In Progress
assignee: nobody → Marco Trevisan (Treviño) (3v1n0)
affects: glib (Ubuntu) → glib2.0 (Ubuntu)
Changed in glib2.0 (Ubuntu):
status: In Progress → Incomplete
Changed in gnome-shell (Ubuntu):
status: Triaged → Incomplete
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

"Incomplete" makes sense to me because it appears the problem stopped happening after 3.28, and not at all in 3.30. We will need more time to verify that's really true:

https://errors.ubuntu.com/problem/87e4666825764619cb47f3837f871d88d65dd606

and if so then this is "Fix Released" already.

Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in gnome-shell (Ubuntu):
status: Incomplete → Expired
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Zero crashes after 18.10 so consider it fixed.

Changed in glib2.0 (Ubuntu):
status: Incomplete → Fix Released
Changed in gnome-shell (Ubuntu):
status: Expired → Fix Released
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.