gnome-shell crashed with SIGSEGV in st_widget_get_theme_node()

Bug #1818712 reported by El jinete sin cabeza
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-shell (Ubuntu)
New
Medium
Unassigned

Bug Description

https://gitlab.gnome.org/GNOME/gnome-shell/issues/1018

---

I do not know what happened.

ProblemType: Crash
DistroRelease: Ubuntu 19.04
Package: gnome-shell 3.30.2-2ubuntu2
Uname: Linux 5.0.0-050000-generic x86_64
ApportVersion: 2.20.10-0ubuntu21
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Mar 5 14:56:23 2019
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
GsettingsChanges:
 b'org.gnome.shell' b'favorite-apps' redacted by apport
 b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true'
 b'org.gnome.shell' b'enabled-extensions' b"['desktop-icons@csoriano', '<email address hidden>']"
 b'org.gnome.desktop.interface' b'gtk-im-module' b"'ibus'"
InstallationDate: Installed on 2018-12-02 (93 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
ProcCmdline: /usr/bin/gnome-shell
ProcEnviron:
 LANGUAGE=es_CL:es
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=es_CL.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f117e471f48 <st_widget_get_theme_node+24>: mov 0x8(%rbx),%rbp
 PC (0x7f117e471f48) ok
 source "0x8(%rbx)" (0xfffffffffffffbc8) not located in a known VMA region (needed readable region)!
 destination "%rbp" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: gnome-shell
StacktraceTop:
 st_widget_get_theme_node () from /usr/lib/gnome-shell/libst-1.0.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
 ?? () from /usr/lib/libgjs.so.0
 ?? () from /usr/lib/libgjs.so.0
Title: gnome-shell crashed with SIGSEGV in st_widget_get_theme_node()
UpgradeStatus: Upgraded to disco on 2018-12-02 (92 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
separator:

Revision history for this message
El jinete sin cabeza (ejsc-deactivatedaccount) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 st_widget_get_theme_node (widget=0x0) at ../src/st/st-widget.c:603
 ffi_call_unix64 () at ../src/x86/unix64.S:76
 ffi_call (cif=cif@entry=0x55b14faadf78, fn=<optimized out>, rvalue=<optimized out>, rvalue@entry=0x7ffdad2988a8, avalue=avalue@entry=0x7ffdad2987b0) at ../src/x86/ffi64.c:525
 gjs_invoke_c_function (context=0x55b14dbc1c20, function=0x55b14faadf60, obj=..., args=..., js_rval=..., r_value=0x0) at gi/function.cpp:1096
 function_call (context=0x55b14dbc1c20, js_argc=0, vp=0x7ffdad298c48) at /usr/include/mozjs-60/js/RootingAPI.h:1128

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
information type: Private → Public
description: updated
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1796606, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.

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.