*** This bug is a duplicate of bug 1868660 ***
https://bugs.launchpad.net/bugs/1868660
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 1868660, 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.
** This bug has been marked a duplicate of bug 1868660
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()
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1871684
Title:
gnome-shell crashed - endlessly in a loop from lock screen - with
SIGSEGV in st_theme_node_get_icon_style()
Status in gnome-shell package in Ubuntu:
Triaged
Bug description:
Starting today, gnome-shell is crashing when you try to unlock the
screen. It then shows you your open windows (security?), and then it
restarts to the lock screen from where it will crash again if you move
mouse or press key.
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
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu25
Architecture: amd64
CurrentDesktop: GNOME
Date: Wed Apr 8 20:09:33 2020
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
GsettingsChanges:
InstallationDate: Installed on 2018-03-14 (756 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313)
ProcCmdline: /usr/bin/gnome-shell
RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1
SegvAnalysis:
Segfault happened at: 0x7fc85dfc3aaf <st_theme_node_get_icon_style+159>:
repz cmpsb %es:(%rdi),%ds:(%rsi)
PC (0x7fc85dfc3aaf) ok
source "%es:(%rdi)" (0x7fc85dff48f9) ok
destination "%ds:(%rsi)" (0x00004d83) not located in a known VMA region
(needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: gnome-shell
StacktraceTop:
st_theme_node_get_icon_style () at /usr/lib/gnome-shell/libst-1.0.so
st_texture_cache_load_gicon () at /usr/lib/gnome-shell/libst-1.0.so
() at /usr/lib/gnome-shell/libst-1.0.so
() at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
g_signal_emit_valist () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: gnome-shell crashed with SIGSEGV in st_theme_node_get_icon_style()
UpgradeStatus: Upgraded to focal on 2019-11-25 (135 days ago)
UserGroups: adm cdrom dip fax input kvm lpadmin lxd plugdev sambashare sbuild
sudo
separator:
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1871684/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
