gnome-shell crashed with SIGSEGV in libst-1.0.so[7f85e3513000+4e000]

Bug #2007974 reported by Coeur Noir
8
This bug affects 1 person
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.0.so[7f85e3513000+4e000]
[ 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-shell@aunetx
<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
ProcVersionSignature: Ubuntu 5.15.0-60.66-generic 5.15.78
Uname: Linux 5.15.0-60-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.3
Architecture: amd64
CasperMD5CheckResult: pass
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-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
RelatedPackageVersions: mutter-common 42.5-0ubuntu1
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Coeur Noir (coeur-noir) wrote :
Coeur Noir (coeur-noir)
description: updated
Revision history for this message
Daniel van Vugt (vanvugt) wrote : Re: gnome-shell crashed with SIGSEGV

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[7f85e3513000+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.

summary: - Session starts with all gnome-shell extensions disabled
+ gnome-shell crashed with SIGSEGV
summary: - gnome-shell crashed with SIGSEGV
+ gnome-shell crashed with SIGSEGV in libst-1.0.so[7f85e3513000+4e000]
affects: gnome-shell (Ubuntu) → ubuntu
Changed in ubuntu:
status: New → Incomplete
Revision history for this message
Coeur Noir (coeur-noir) wrote :

Hi,

nothing in /var/crash

journalctl -S "2023-02-26 13:00:00" > journalctl_lastboot → see attached file

there are things around gnome-shell but also gdm-password or gnome-session. Those last two worry me.

gnome-shell extension « lockkeys » may be using « obsolete » ways and the permissions issues about « burn-my-windows » has been fixed since then ( I know why and it's not the topic here. )

I understand why gnome-shell extensions are legitimately not « your » concern here but I'm mostly worried by the inability to open my session every now and then.

Revision history for this message
Coeur Noir (coeur-noir) wrote :

same log but "grep" gnome-shell

Revision history for this message
Coeur Noir (coeur-noir) wrote :

journalctl -S "2023-02-26 13:00:00" | grep -Ei "gnome-shell|gnome-session|password" > journalctl_today_other_grep

Maybe something about DING extension ? ( this one is part of Ubuntu ).

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

Thanks for the logs. Unfortunately they did not reveal the cause of the crash.

Next please:

  cd ~/.local/share/gnome-shell/
  rm -rf extensions

and then log in again. Has that fixed the crash?

Revision history for this message
Coeur Noir (coeur-noir) wrote :

Ok, so you offer me to remove all gnome-shell extensions ?

Might be enough to only disable them ? ? ?

Or remove is the only way to validate something here ?

Revision history for this message
Coeur Noir (coeur-noir) wrote :
Download full text (4.8 KiB)

It happens again today ( without removing any extension )

In journalctl -S today can see warnings about lockkeys extension :

mars 18 16:18:53 ASGARD gnome-shell[3556]: Usage of object.actor is deprecated for PanelMenuButton
                                           get@resource:///org/gnome/shell/ui/environment.js:411:29
                                           enable@/home/django/.local/share/gnome-shell/extensions/lockkeys@fawtytoo/extension.js:52:5
                                           _callExtensionEnable@resource:///org/gnome/shell/ui/extensionSystem.js:183:32
                                           _onEnabledExtensionsChanged/<@resource:///org/gnome/shell/ui/extensionSystem.js:532:35
                                           _onEnabledExtensionsChanged@resource:///org/gnome/shell/ui/extensionSystem.js:532:14
                                           _onUserExtensionsEnabledChanged@resource:///org/gnome/shell/ui/extensionSystem.js:520:14
                                           createCheckedMethod/<@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:533:46
                                           set UserExtensionsEnabled@resource:///org/gnome/shell/ui/shellDBus.js:483:25
                                           _handlePropertySet@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:374:35
                                           _wrapJSObject/<@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:393:35
mars 18 16:18:53 ASGARD gnome-shell[3556]: Usage of object.actor is deprecated for PanelMenuButton
                                           get@resource:///org/gnome/shell/ui/environment.js:411:29
                                           updateState@/home/django/.local/share/gnome-shell/extensions/lockkeys@fawtytoo/extension.js:29:10
                                           enable@/home/django/.local/share/gnome-shell/extensions/lockkeys@fawtytoo/extension.js:56:5
                                           _callExtensionEnable@resource:///org/gnome/shell/ui/extensionSystem.js:183:32
                                           _onEnabledExtensionsChanged/<@resource:///org/gnome/shell/ui/extensionSystem.js:532:35
                                           _onEnabledExtensionsChanged@resource:///org/gnome/shell/ui/extensionSystem.js:532:14
                                           _onUserExtensionsEnabledChanged@resource:///org/gnome/shell/ui/extensionSystem.js:520:14
                                           createCheckedMethod/<@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:533:46

grep extensions journalctl_s_today

                                           updateState@/home/django/.local/share/gnome-shell/extensions/lockkeys@fawtytoo/extension.js:29:10
                                           updateState@/home/django/.local/share/gnome-shell/extensions/lockkeys@fawtytoo/extension.js:29:10
                                           updateState@/home/django/.local/share/gnome-shell/extensions/lockkeys@fawtytoo/extension.js:29:10
                                           updateState@/home/django/.local/share/gnome-shell/extensions/lockkeys@fawtytoo/extension.js:29:10
           ...

Read more...

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

The 'lockkeys@fawtytoo' extension is not supported by Ubuntu. But hopefully that's not the cause of your crash...

Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps:

1. Look in /var/crash for crash files and if found run:
    ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.

2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us.

Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself.

Revision history for this message
Coeur Noir (coeur-noir) wrote (last edit ):

Happens again, in a different scenario.

I have logged in as user A - no problem.

Then change user to B, so session A is still running.

First attempt at login to graphical session B → goes back to user's choice.
second attempt → I'm logged in session B but all gnome extensions are disabled.

django@ASGARD:~$ ls -l /var/crash/
total 0

and in dmesg same « error » as before :

[ 7153.079184] gnome-shell[77638]: segfault at 556a7994c000 ip 00007fdc0694c8c5 sp 00007ffd72ed6ce0 error 4 in libst-1.0.so[7fdc06922000+4e000]
[ 7153.079196] 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

and looking at

https://errors.ubuntu.com/user/ad9261621(…)fc81b7

only reads

No errors have been reported from this system

Attached is the output of

journalctl -S today | grep -Ei "extensions|fail|erro" | grep -vEi "thunderbird|firefox"

( since firefox or thunderbird are not the droids we're looking for )

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

Thanks. Unfortunately that log doesn't show any additional information about the crash of PID 77638.

Please try without your extensions since those are the most likely cause of the crash. If you establish the crash was in the extensions then you can reintroduce some of them slowly to figure out which is to blame.

There is also a memory leak in Mesa that would affect your 4th generation Intel GPU: bug 1972977. That might be the cause and one possible workaround might be: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1972977/comments/23

Revision history for this message
Coeur Noir (coeur-noir) wrote :

I tried the latter part of your last comment, about Mesa.
No difference.

Today there was an update available for a gnome-shell extension ( burn-my-windows ) and right after updating, meaning after session log out and log in, same behavior happened.

avril 07 13:45:24 ASGARD kernel: gnome-shell[5679]: segfault at 562abe92d000 ip 00007f62dc12d8c5 sp 00007ffc765c9080 error 4 in libst-1.0.so[7f62dc103000+4e000]
avril 07 13:45:25 ASGARD systemd[2051]: <email address hidden>: Failed with result 'core-dump'.
avril 07 13:45:25 ASGARD systemd[2051]: Failed to start GNOME Shell on Wayland.
avril 07 13:45:25 ASGARD systemd[2051]: <email address hidden>: Triggering OnFailure= dependencies.
avril 07 13:45:25 ASGARD systemd[2051]: Started Disable GNOME Shell extensions after failure.

…culprit might be somewhere in those gnome-shell extensions…

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for Ubuntu because there has been no activity for 60 days.]

Changed in ubuntu:
status: Incomplete → Expired
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.