gnome-shell crashed with SIGSEGV in _st_theme_node_ensure_background() from st_theme_node_paint_equal() from st_widget_recompute_style() from st_widget_style_changed() [when locking the screen] [usually due to dash-to-panel]
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
GNOME Shell |
Fix Released
|
Unknown
|
|||
gnome-shell (Ubuntu) |
Fix Released
|
High
|
Marco Trevisan (Treviño) | ||
Focal |
Fix Released
|
High
|
Marco Trevisan (Treviño) |
Bug Description
[ Impact ]
GNOME shell crashes on extensions loading / updates
[ Test case ]
- No clear test case, normally may happen during screen locking/unlocking
- But crashes should be monitored at
https:/
[ Regression potential ]
Stylesheet memory could be leaked
---
Seems to be reproducible
Suspend the computer
Start the computer from suspend
Start chrome gmail.
Has happened two times
ProblemType: CrashDistroRelease: Ubuntu 20.10
Package: gnome-shell 3.36.2-1ubuntu1
ProcVersionSign
Uname: Linux 5.4.0-28-generic x86_64
ApportVersion: 2.20.11-0ubuntu33
Architecture: amd64
CasperMD5CheckR
CrashCounter: 1
CurrentDesktop: ubuntu:GNOME
Date: Sat May 9 20:00:47 2020
DisplayManager: gdm3
ExecutablePath: /usr/bin/
InstallationDate: Installed on 2020-04-16 (23 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200415.2)
ProcCmdline: /usr/bin/
RelatedPackageV
SegvAnalysis:
Segfault happened at: 0x7fe1b40c4252 <_st_theme_
PC (0x7fe1b40c4252) ok
source "(%rax)" (0x00000000) not located in a known VMA region (needed readable region)!
destination "%r12" ok
SegvReason: reading NULL VMA
Signal: 11SourcePackage: gnome-shell
StacktraceTop:
_st_theme_
st_theme_
?? () from /usr/lib/
st_widget_
?? () from /usr/lib/
Title: gnome-shell crashed with SIGSEGV in _st_theme_
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
separator:
summary: |
gnome-shell crashed with SIGSEGV in _st_theme_node_ensure_background() + when using dash-to-panel |
Changed in gnome-shell (Ubuntu): | |
status: | New → Fix Committed |
importance: | Medium → Low |
tags: | added: fixed-in-3.36.3 fixed-upstream |
information type: | Private → Public |
Changed in gnome-shell-extension-dash-to-panel: | |
status: | Unknown → Fix Released |
tags: | added: focal |
no longer affects: | gnome-shell-extension-dash-to-panel |
Changed in gnome-shell (Ubuntu): | |
status: | Fix Committed → Fix Released |
Changed in gnome-shell (Ubuntu): | |
status: | Fix Released → Fix Committed |
summary: |
gnome-shell crashed with SIGSEGV in _st_theme_node_ensure_background() - when using dash-to-panel + from st_theme_node_paint_equal() from st_widget_recompute_style() from + st_widget_style_changed() |
summary: |
gnome-shell crashed with SIGSEGV in _st_theme_node_ensure_background() from st_theme_node_paint_equal() from st_widget_recompute_style() from - st_widget_style_changed() + st_widget_style_changed() [usually with the dash-to-panel extension] |
description: | updated |
summary: |
gnome-shell crashed with SIGSEGV in _st_theme_node_ensure_background() from st_theme_node_paint_equal() from st_widget_recompute_style() from - st_widget_style_changed() [usually with the dash-to-panel extension] + st_widget_style_changed() [when locking the screen] |
description: | updated |
Changed in gnome-shell (Ubuntu Focal): | |
importance: | Undecided → High |
status: | New → In Progress |
Changed in gnome-shell (Ubuntu): | |
assignee: | nobody → Marco Trevisan (Treviño) (3v1n0) |
Changed in gnome-shell (Ubuntu Focal): | |
assignee: | nobody → Marco Trevisan (Treviño) (3v1n0) |
summary: |
gnome-shell crashed with SIGSEGV in _st_theme_node_ensure_background() from st_theme_node_paint_equal() from st_widget_recompute_style() from - st_widget_style_changed() [when locking the screen] + st_widget_style_changed() [when locking the screen] [usually due to + dash-to-panel] |
tags: |
added: verification-done verification-done-focal removed: verification-needed verification-needed-focal |
Changed in gnome-shell: | |
status: | Unknown → Fix Released |
Probably the same as Bug 1877760