gnome-shell crashed with SIGSEGV in st_theme_node_lookup_length() from st_theme_node_get_length() from ffi_call_unix64()

[elPraga]

https://errors.ubuntu.com/problem/66cc3c6b0baf1cf6e4b51a794546b929809bacf4

---

This is all the information I was able to gather. GS crashed right after pressing Win+L on a bluetooth keyboard.

ProblemType: Crash
DistroRelease: Ubuntu 20.04
Package: gnome-shell 3.36.0-2ubuntu2
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
Uname: Linux 5.4.0-21-generic x86_64
ApportVersion: 2.20.11-0ubuntu22
Architecture: amd64
CurrentDesktop: GNOME
Date: Mon Apr 6 11:14:17 2020
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
InstallationDate: Installed on 2018-10-29 (524 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
ProcCmdline: /usr/bin/gnome-shell
RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1
SegvAnalysis:
 Segfault happened at: 0x7f3d04d6996d <st_theme_node_lookup_length+125>: mov (%rax),%rdi
 PC (0x7f3d04d6996d) ok
 source "(%rax)" (0xff0082c9ff0082c9) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: gnome-shell
StacktraceTop:
 st_theme_node_lookup_length () at /usr/lib/gnome-shell/libst-1.0.so
 st_theme_node_get_length () at /usr/lib/gnome-shell/libst-1.0.so
 () at /usr/lib/x86_64-linux-gnu/libffi.so.7
 () at /usr/lib/x86_64-linux-gnu/libffi.so.7
 () at /usr/lib/libgjs.so.0
Title: gnome-shell crashed with SIGSEGV in st_theme_node_lookup_length()
UpgradeStatus: Upgraded to focal on 2020-03-27 (9 days ago)
UserGroups: adm cdrom dip kvm libvirt lpadmin plugdev sambashare sudo
separator:

[Apport retracing service (apport)]

StacktraceTop:
 st_theme_node_lookup_length () from /tmp/apport_sandbox_8g0pg8pn/usr/lib/gnome-shell/libst-1.0.so
 st_theme_node_get_length () from /tmp/apport_sandbox_8g0pg8pn/usr/lib/gnome-shell/libst-1.0.so
 ffi_call_unix64 () at ../src/x86/unix64.S:101
 ffi_call_int (cif=<optimized out>, fn=<optimized out>, rvalue=<optimized out>, avalue=<optimized out>, closure=<optimized out>) at ../src/x86/ffi64.c:669
 gjs_invoke_c_function (context=<optimized out>, function=0x56255a1281e0, obj=..., args=..., js_rval=..., r_value=<optimized out>) at ../gi/function.cpp:1116

[Daniel van Vugt (vanvugt)]

I can't seem to find any other reports of this crash right now, but notice you do have a lot of extensions installed:

b'org.gnome.shell' b'enabled-extensions' b"['<email address hidden>', '<email address hidden>', '<email address hidden>', '<email address hidden>', 'gTile@vibou', '<email address hidden>', '<email address hidden>', '<email address hidden>', '<email address hidden>', '<email address hidden>', '<email address hidden>', '<email address hidden>', 'float-mpv@shou', '<email address hidden>', '<email address hidden>', '<email address hidden>', '<email address hidden>', 'gnome-shell-extension-tool', '<email address hidden>', '<email address hidden>', '<email address hidden>', '<email address hidden>', 'cpufreq@konkor', '<email address hidden>', '<email address hidden>', 'you2ber@konkor', '<email address hidden>', '<email address hidden>', '<email address hidden>', '<email address hidden>']"

Please uninstall all of them and then tell us if the problem still occurs.

[elPraga (elpraga)]

Thank you Daniel,

Don't you think though that a faulty extension *should not* cause a *the
whole session* to crash in the first place?

Tomas

On Mon, 6 Apr 2020, 11:56 Daniel van Vugt, <email address hidden>
wrote:

> I can't seem to find any other reports of this crash right now, but
> notice you do have a lot of extensions installed:
>
> b'org.gnome.shell' b'enabled-extensions' b"['<email address hidden>',
> '<email address hidden>', '<email address hidden>',
> '<email address hidden>', 'gTile@vibou',
> '<email address hidden>', '<email address hidden>', 'Space@dev-
> crea.com', '<email address hidden>', 'journal@gnome-shell-
> extensions.zeitgeist-project.com', 'jump-lists@gnome-shell-extensions
> .zeitgeist-project.com', '<email address hidden>', 'float-
> mpv@shou', '<email address hidden>', '<email address hidden>',
> '<email address hidden>', '<email address hidden>', 'gnome-
> shell-extension-tool', '<email address hidden>', 'quake-mode@repsac-
> by.github.com', '<email address hidden>', 'places-menu@gnome-
> shell-extensions.gcampax.github.com', 'cpufreq@konkor', 'sound-output-
> <email address hidden>', '<email address hidden>',
> 'you2ber@konkor', '<email address hidden>', 'steal-my-
> <email address hidden>', '<email address hidden>',
> '<email address hidden>']"
>
> Please uninstall all of them and then tell us if the problem still
> occurs.
>
> ** Information type changed from Private to Public
>
> ** Changed in: gnome-shell (Ubuntu)
> Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1871063
>
> Title:
> gnome-shell crashed with SIGSEGV in st_theme_node_lookup_length()
>
> Status in gnome-shell package in Ubuntu:
> Incomplete
>
> Bug description:
> This is all the information I was able to gather. GS crashed right
> after pressing Win+L on a bluetooth keyboard.
>
> ProblemType: Crash
> DistroRelease: Ubuntu 20.04
> Package: gnome-shell 3.36.0-2ubuntu2
> ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
> Uname: Linux 5.4.0-21-generic x86_64
> ApportVersion: 2.20.11-0ubuntu22
> Architecture: amd64
> CurrentDesktop: GNOME
> Date: Mon Apr 6 11:14:17 2020
> DisplayManager: gdm3
> ExecutablePath: /usr/bin/gnome-shell
> InstallationDate: Installed on 2018-10-29 (524 days ago)
> InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64
> (20181017.3)
> ProcCmdline: /usr/bin/gnome-shell
> RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1
> SegvAnalysis:
> Segfault happened at: 0x7f3d04d6996d
> <st_theme_node_lookup_length+125>: mov (%rax),%rdi
> PC (0x7f3d04d6996d) ok
> source "(%rax)" (0xff0082c9ff0082c9) not located in a known VMA region
> (needed readable region)!
> destination "%rdi" ok
> SegvReason: reading unknown VMA
> Signal: 11
> SourcePackage: gnome-shell
> StacktraceTop:
> st_theme_node_lookup_length () at /usr/lib/gnome-shell/libst-1.0.so
> st_theme_node_get_length () at /usr/lib/gnome-...

[Daniel van Vugt (vanvugt)]

Ideally, you're right. But this is the way gnome-shell is designed. So the options we have right now are either to let extensions do anything (break anything), or to disallow all extensions.

[elPraga (elpraga)]

OK, I get it.

I'm trying to investigate the crash, but I'm rather busy ATM.

You mentioned uninstalling all extensions would **disabling** them have the same effect to trace the crash? (As you understand, it is much less laborious than installing and uninstalling them)

Please, let me know if it is the same for your purposes.

[elPraga (elpraga)]

Might be related to:

https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1868440

[Daniel van Vugt (vanvugt)]

No disabling extensions is not enough because we have found that a disabled buggy extension can still interfere with gnome-shell.

[Daniel van Vugt (vanvugt)]

Confirmed and tracking in:

https://errors.ubuntu.com/problem/66cc3c6b0baf1cf6e4b51a794546b929809bacf4