Thank you Daniel, Don't you think though that a faulty extension *should not* cause a *the whole session* to crash in the first place?
Tomas On Mon, 6 Apr 2020, 11:56 Daniel van Vugt, <daniel.van.v...@canonical.com> wrote: > I can't seem to find any other reports of this crash right now, but > notice you do have a lot of extensions installed: > > b'org.gnome.shell' b'enabled-extensions' b"['clip...@gnome.besnik.de', > 'clipboard-indica...@tudmotu.com', 'night-light-slider.ti...@linux.com', > 'pause-night-li...@tijnschuurmans.nl', 'gTile@vibou', > 'extensi...@abteil.org', 'stopwa...@domen.gamabit.com', 'Space@dev- > crea.com', 'dash-to-d...@micxgx.gmail.com', 'journal@gnome-shell- > extensions.zeitgeist-project.com', 'jump-lists@gnome-shell-extensions > .zeitgeist-project.com', 'jump-li...@thoughtmonster.github.com', 'float- > mpv@shou', 'cast-to...@rafostar.github.com', 'un...@hardpixel.eu', > 'disk-space-us...@atareao.es', 'miniv...@thesecretaryofwar.com', 'gnome- > shell-extension-tool', 'ubuntu-d...@ubuntu.com', 'quake-mode@repsac- > by.github.com', 'gsconn...@andyholmes.github.io', 'places-menu@gnome- > shell-extensions.gcampax.github.com', 'cpufreq@konkor', 'sound-output- > device-choo...@kgshank.net', 'gnome-shell-screens...@ttll.de', > 'you2ber@konkor', 'easyscreenc...@iacopodeenosee.gmail.com', 'steal-my- > fo...@kagesenshi.org', 'appindicatorsupp...@rgcjonas.gmail.com', > 'simple-d...@nothing.org']" > > Please uninstall all of them and then tell us if the problem still > occurs. > > ** Information type changed from Private to Public > > ** Changed in: gnome-shell (Ubuntu) > Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1871063 > > Title: > gnome-shell crashed with SIGSEGV in st_theme_node_lookup_length() > > Status in gnome-shell package in Ubuntu: > Incomplete > > Bug description: > This is all the information I was able to gather. GS crashed right > after pressing Win+L on a bluetooth keyboard. > > 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 > ApportVersion: 2.20.11-0ubuntu22 > Architecture: amd64 > CurrentDesktop: GNOME > Date: Mon Apr 6 11:14:17 2020 > DisplayManager: gdm3 > ExecutablePath: /usr/bin/gnome-shell > InstallationDate: Installed on 2018-10-29 (524 days ago) > InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 > (20181017.3) > ProcCmdline: /usr/bin/gnome-shell > RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1 > SegvAnalysis: > Segfault happened at: 0x7f3d04d6996d > <st_theme_node_lookup_length+125>: mov (%rax),%rdi > PC (0x7f3d04d6996d) ok > source "(%rax)" (0xff0082c9ff0082c9) not located in a known VMA region > (needed readable region)! > destination "%rdi" ok > SegvReason: reading unknown VMA > Signal: 11 > SourcePackage: gnome-shell > StacktraceTop: > st_theme_node_lookup_length () at /usr/lib/gnome-shell/libst-1.0.so > st_theme_node_get_length () at /usr/lib/gnome-shell/libst-1.0.so > () at /usr/lib/x86_64-linux-gnu/libffi.so.7 > () at /usr/lib/x86_64-linux-gnu/libffi.so.7 > () at /usr/lib/libgjs.so.0 > Title: gnome-shell crashed with SIGSEGV in st_theme_node_lookup_length() > UpgradeStatus: Upgraded to focal on 2020-03-27 (9 days ago) > UserGroups: adm cdrom dip kvm libvirt lpadmin plugdev sambashare sudo > separator: > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1871063/+subscriptions > -- 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/1871063 Title: gnome-shell crashed with SIGSEGV in st_theme_node_lookup_length() Status in gnome-shell package in Ubuntu: Incomplete Bug description: This is all the information I was able to gather. GS crashed right after pressing Win+L on a bluetooth keyboard. 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 ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Apr 6 11:14:17 2020 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2018-10-29 (524 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1 SegvAnalysis: Segfault happened at: 0x7f3d04d6996d <st_theme_node_lookup_length+125>: mov (%rax),%rdi PC (0x7f3d04d6996d) ok source "(%rax)" (0xff0082c9ff0082c9) not located in a known VMA region (needed readable region)! destination "%rdi" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: st_theme_node_lookup_length () at /usr/lib/gnome-shell/libst-1.0.so st_theme_node_get_length () at /usr/lib/gnome-shell/libst-1.0.so () at /usr/lib/x86_64-linux-gnu/libffi.so.7 () at /usr/lib/x86_64-linux-gnu/libffi.so.7 () at /usr/lib/libgjs.so.0 Title: gnome-shell crashed with SIGSEGV in st_theme_node_lookup_length() UpgradeStatus: Upgraded to focal on 2020-03-27 (9 days ago) UserGroups: adm cdrom dip kvm libvirt lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1871063/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
