gnome-shell crashed with SIGSEGV in st_theme_node_get_icon_style() from st_texture_cache_load_gicon() from st_icon_update() from _g_closure_invoke_va() from g_signal_emit_valist()

Bug #1868660 reported by errors.ubuntu.com bug bridge
68
This bug affects 9 people
Affects Status Importance Assigned to Milestone
GNOME Shell
Fix Released
Unknown
gnome-shell (Ubuntu)
Fix Released
Medium
Daniel van Vugt
Focal
Fix Committed
Undecided
Daniel van Vugt

Bug Description

The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.35.91-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/f48b96bcfbbd221faf772da51dae29be310cbd9c contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Possibly related (just landed this week in gnome-shell, before version 3.36.1):

https://gitlab.gnome.org/GNOME/gnome-shell/-/commit/3dd8ffc2bb1cef

summary: - /usr/bin/gnome-
- shell:11:st_theme_node_get_icon_style:st_texture_cache_load_gicon:st_icon_update:_g_closure_invoke_va:g_signal_emit_valist
+ gnome-shell crashed with SIGSEGV in st_theme_node_get_icon_style() from
+ st_texture_cache_load_gicon() from st_icon_update() from
+ _g_closure_invoke_va() from g_signal_emit_valist()
Changed in gnome-shell (Ubuntu):
importance: Undecided → Medium
status: New → Triaged
Revision history for this message
Per-Inge (per-inge-hallin) wrote :

Thought this was fixed with gnome 3.36, but I got it when I 1:st closed Gmail and then Chrome.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

In comment #1 I was referring to a fix coming in gnome-shell 3.36.1, which is not yet in Ubuntu. Maybe that will help here, eventually.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :
tags: removed: yakkety
Revision history for this message
Thorsten (thorstenr-42) wrote :

i got this error when hovering with the mouse over the system tray as described in the bug report however Iam using X11 and not wayland

i have the following crash files:
-rw-r----- 1 root root 95M Mai 10 13:15 _usr_bin_gnome-shell.1000.crash
-rw-r--r-- 1 root root 0 Mai 10 13:15 _usr_bin_gnome-shell.1000.upload
-rw------- 1 root root 37 Mai 10 13:15 _usr_bin_gnome-shell.1000.uploaded
-rw-r----- 1 root root 2,4M Mai 10 13:15 _usr_lib_x86_64-linux-gnu_libexec_kdeconnectd.1000.crash
-rw-r--r-- 1 root root 0 Mai 10 13:15 _usr_lib_x86_64-linux-gnu_libexec_kdeconnectd.1000.upload
-rw------- 1 root root 37 Mai 10 13:15 _usr_lib_x86_64-linux-gnu_libexec_kdeconnectd.1000.uploaded

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

The upstream bug claims to have the same root cause as Ubuntu bug 1868440 so it sounds like it's fixed in that case.

Changed in gnome-shell:
importance: Unknown → Undecided
status: Unknown → New
importance: Undecided → Unknown
status: New → Unknown
Changed in gnome-shell (Ubuntu):
status: Triaged → Fix Released
Changed in gnome-shell (Ubuntu Focal):
status: New → Fix Committed
Revision history for this message
Per-Inge (per-inge-hallin) wrote :

I don't know if this is related. It seems I always get a crash either when I start suspend or when I return from suspend. When I send the crash report launchpad don't open. The crash is in gnome-shell and the crash message is "gnome-shell crashed with SIGSEGV in_st_theme_node_ensure_background()".
It might be related to my installation and I will reinstall Focal later today.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

That sounds like bug 1877774

Revision history for this message
Daniel van Vugt (vanvugt) wrote :
Changed in gnome-shell (Ubuntu Focal):
assignee: nobody → Daniel van Vugt (vanvugt)
Changed in gnome-shell (Ubuntu):
assignee: nobody → Daniel van Vugt (vanvugt)
Revision history for this message
Per-Inge (per-inge-hallin) wrote : Re: [Bug 1868660] Re: gnome-shell crashed with SIGSEGV in st_theme_node_get_icon_style() from st_texture_cache_load_gicon() from st_icon_update() from _g_closure_invoke_va() from g_signal_emit_valist()

I don't have problems with suspend any longer. I think this bug is fixed.

However I'm not using the standard kernel. I'm using Kernel:
5.7.7-050707-generic x86_64.
I had a problem with Chrome freezing the computer and this kernel fixed
that problem.

Den tis 14 juli 2020 kl 16:01 skrev Martin Wimpress <
<email address hidden>>:

> ** Changed in: gnome-shell (Ubuntu Focal)
> Assignee: (unassigned) => Daniel van Vugt (vanvugt)
>
> ** Changed in: gnome-shell (Ubuntu)
> Assignee: (unassigned) => Daniel van Vugt (vanvugt)
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1868660
>
> Title:
> gnome-shell crashed with SIGSEGV in st_theme_node_get_icon_style()
> from st_texture_cache_load_gicon() from st_icon_update() from
> _g_closure_invoke_va() from g_signal_emit_valist()
>
> Status in GNOME Shell:
> Unknown
> Status in gnome-shell package in Ubuntu:
> Fix Released
> Status in gnome-shell source package in Focal:
> Fix Committed
>
> Bug description:
> The Ubuntu Error Tracker has been receiving reports about a problem
> regarding gnome-shell. This problem was most recently seen with package
> version 3.35.91-1ubuntu2, the problem page at
> https://errors.ubuntu.com/problem/f48b96bcfbbd221faf772da51dae29be310cbd9c
> contains more details, including versions of packages affected, stacktrace
> or traceback, and individual crash reports.
> If you do not have access to the Ubuntu Error Tracker and are a software
> developer, you can request it at http://forms.canonical.com/reports/.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/gnome-shell/+bug/1868660/+subscriptions
>

--
Skickat från min nya mailadress

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

The upstream fix seems to be in 3.37.1 and 3.36.2. Yet focal has 51 crash reports in 3.36.2 and later. So I think the upstream bug maybe should still be open (not a duplicate):

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

That said, 51 is much lower than the 3000 crash reports from 3.36.0-3.36.1 so maybe upstream did fix most of the problem.

Changed in gnome-shell:
status: Unknown → 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.