gnome-shell crashed with SIGSEGV in libst-1.0.so[7f85e3513000+4e000]
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu |
Expired
|
Undecided
|
Unassigned |
Bug Description
Hello,
it happens every now and then, for few months ( I'd say since december '22 ).
Power on the machine → login screen → password → gets back to login screen → again, password → session opens but all gnome-shell extensions are disabled.
And each time, I can find this in dmesg :
[ 21.981578] gnome-shell[1839]: segfault at 5617f4861000 ip 00007f85e353d8c5 sp 00007ffc70c8cf70 error 4 in libst-1.
[ 21.981588] Code: 74 5f 4c 89 e6 48 89 df 4c 63 e8 e8 95 7f fd ff 48 85 c0 74 41 48 8b 15 d9 76 04 00 48 8b 2a 66 0f 1f 44 00 00 48 39 c3 74 0b <0f> b6 50 ff f6 44 55 01 01 74 10 42 0f b6 14 28 84 d2 74 18 f6 44
How narrow down a culprit ?
Extensions installed :
blur-my-
<email address hidden>
<email address hidden>
lockkeys@fawtytoo
<email address hidden>
<email address hidden>
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-shell 42.5-0ubuntu1
ProcVersionSign
Uname: Linux 5.15.0-60-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.3
Architecture: amd64
CasperMD5CheckR
CurrentDesktop: ubuntu:GNOME
Date: Tue Feb 21 14:04:20 2023
DisplayManager: gdm3
InstallationDate: Installed on 2022-06-01 (264 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
ProcEnviron:
TERM=xterm-
PATH=(custom, no user)
XDG_RUNTIME_
LANG=fr_FR.UTF-8
SHELL=/bin/bash
RelatedPackageV
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)
description: | updated |
Please use 'journalctl' to find the system log messages that came before:
[ 21.981578] gnome-shell[1839]: segfault at 5617f4861000 ip 00007f85e353d8c5 sp 00007ffc70c8cf70 error 4 in libst-1. 0.so[7f85e35130 00+4e000]
Please also follow these steps to check for crash reports:
https:/ /wiki.ubuntu. com/Bugs/ Responses# Missing_ a_crash_ report_ or_having_ a_.crash_ attachment
That said, we'd kind of be wasting our time if we didn't first establish that the crash is caused by an official Ubuntu component. If it's come from one of your extensions then we can't track the problem here.