gnome-shell crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a() from g_object_ref() from st_theme_get_custom_stylesheets()

Bug #1702151 reported by Dave Stroud on 2017-07-03
58
This bug affects 10 people
Affects Status Importance Assigned to Milestone
GNOME Shell
New
Unknown
gnome-shell (Ubuntu)
Medium
Marco Trevisan (Treviño)

Bug Description

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

---

Todays update had a kernal and my gnome shell update. Happened when I rebooted. I now have a black screen and no panel. Icons are all that shows up on desktop.

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gnome-shell 3.24.2-0ubuntu7
ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
Uname: Linux 4.11.0-10-generic x86_64
ApportVersion: 2.20.5-0ubuntu5
Architecture: amd64
CurrentDesktop: GNOME
Date: Mon Jul 3 12:46:31 2017
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
ProcCmdline: gnome-shell --sm-client-id 102c52716a25d9b2dd149578036660315000000013290000
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f9bec254d5c <g_type_check_instance_is_fundamentally_a+44>: movzbl 0x14(%rax),%edx
 PC (0x7f9bec254d5c) ok
 source "0x14(%rax)" (0x20706f746b736558) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: gnome-shell
StacktraceTop:
 g_type_check_instance_is_fundamentally_a () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_object_ref () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 st_theme_get_custom_stylesheets () from /usr/lib/gnome-shell/libgnome-shell.so
 ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
 ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6
Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Dave Stroud (bigdavesr) wrote :

StacktraceTop:
 g_type_check_instance_is_fundamentally_a (type_instance=type_instance@entry=0x563538c8ee40, fundamental_type=fundamental_type@entry=80) at ../../../../gobject/gtype.c:4026
 g_object_ref (_object=0x563538c8ee40) at ../../../../gobject/gobject.c:3180
 st_theme_get_custom_stylesheets (theme=0x56353d1bca80) at st/st-theme.c:311
 ffi_call_unix64 () at ../src/x86/unix64.S:76
 ffi_call (cif=cif@entry=0x56352dc4e538, fn=<optimized out>, rvalue=<optimized out>, rvalue@entry=0x7ffe7a6c85e8, avalue=avalue@entry=0x7ffe7a6c84c0) at ../src/x86/ffi64.c:525

Changed in gnome-shell (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace

Sounds similar to bug 1702203, but a bit different.

information type: Private → Public
Daniel van Vugt (vanvugt) wrote :
summary: gnome-shell crashed with SIGSEGV in
- g_type_check_instance_is_fundamentally_a()
+ g_type_check_instance_is_fundamentally_a() from g_object_ref() from
+ st_theme_get_custom_stylesheets()
Launchpad Janitor (janitor) wrote :

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

Changed in gnome-shell (Ubuntu):
status: New → Confirmed

Anyone affected here who can provide a full jouralctl log?

tags: added: bionic
Changed in gnome-shell (Ubuntu):
status: Confirmed → Incomplete
Daniel van Vugt (vanvugt) wrote :

It would be better if this bug did not expire. It is confirmed by almost 3000 crash reports from 18.04/18.10 on errors.ubuntu.com.

Changed in gnome-shell (Ubuntu):
status: Incomplete → Confirmed

I agree, it's just quite hard to reproduce.

I've debugged it for a while, but really I don't see anything wrong in st related to this. I'd need a core dump to be able to interact with gdb better.

tags: added: cosmic
tags: removed: artful
tags: added: fixed-3.32.1 fixed-upstream

Actually not... I misread the title.

tags: removed: fixed-3.32.1 fixed-upstream
Changed in gnome-shell (Ubuntu):
assignee: nobody → Marco Trevisan (Treviño) (3v1n0)
status: Confirmed → In Progress
Changed in gnome-shell:
status: Unknown → New
Ben Klein (robobenklein) wrote :

I'm on 19.04 and I seem to be able to reproduce this at least once a day while I leave my screen locked overnight.

Am willing to provide logs and core dumps if possible.

Just let me know how/what you need to capture.

Each morning when I log back in, the screen will sit and freeze for a minute or so while gnome shell crashes and restarts, but at least it keeps my windows and workspaces open / in place. A bit after that is when apport gives me the dialog.

tags: added: disco eoan
tags: removed: cosmic
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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