Your message dated Mon, 30 Sep 2019 20:56:57 -0400
with message-id
<caaajcmzgtxoqwqqe2jy91gexuj4yx_ik_bzfdtu6qc-x4z7...@mail.gmail.com>
and subject line close bugs fixed in older gnome-shell release
has caused the Debian Bug report #927162,
regarding gnome-shell: intermittent segfault in st_widget_get_theme_node() at
st-widget.c:603
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
927162: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927162
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnome-shell
Version: 3.30.2-3
Severity: critical
Justification: causes serious data loss
Dear Maintainer,
* What led up to the situation?
Just using GNOME normally causes the crash to happen.
* What exactly did you do (or not do) that was effective (or
ineffective)?
It seems to happen randomly, more so on Wayland. I haven't been able to
pinpoint any specific application, extension, or setting.
* What was the outcome of this action?
GNOME shell segfaults. On Wayland, this causes all the applications to
die, and I get booted back to gdm3 (i.e. data loss). On X11, I see the shell
restart only, keeping my applications intact.
* What outcome did you expect instead?
No segfaulting.
The stack trace is attached as gnome-shell-journalctl.log
The coredump (35 MB compressed, 1.2 GB raw): https://transfer.sh/WmwCL/gnome-
shell-coredump.xz
(Hash is attached as gnome-shell-coredump.xz.sha256)
I have had this crash happen multiple times on Wayland and X11; this is the
first crash where I was able to get a coredump. Note that the stack trace is a
little different each time the crash occurs, e.g. this is the first time I've
seen TopIcons show up in the trace. Everything else looks the same.
-- System Information:
Debian Release: buster/sid
APT prefers testing-debug
APT policy: (500, 'testing-debug'), (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 4.19.0-4-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_USER, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages gnome-shell depends on:
ii dconf-gsettings-backend [gsettings-backend] 0.30.1-2
ii evolution-data-server 3.30.5-1
ii gir1.2-accountsservice-1.0 0.6.45-2
ii gir1.2-atspi-2.0 2.30.0-7
ii gir1.2-freedesktop 1.58.3-2
ii gir1.2-gcr-3 3.28.1-1
ii gir1.2-gdesktopenums-3.0 3.28.1-1
ii gir1.2-gdm-1.0 3.30.2-3
ii gir1.2-geoclue-2.0 2.5.2-1
ii gir1.2-glib-2.0 1.58.3-2
ii gir1.2-gnomebluetooth-1.0 3.28.2-3
ii gir1.2-gnomedesktop-3.0 3.30.2.1-1
ii gir1.2-gtk-3.0 3.24.5-1
ii gir1.2-gweather-3.0 3.28.2-2
ii gir1.2-ibus-1.0 1.5.19-4
ii gir1.2-mutter-3 3.30.2-6
ii gir1.2-nm-1.0 1.14.6-2
ii gir1.2-nma-1.0 1.8.20-1
ii gir1.2-pango-1.0 1.42.4-6
ii gir1.2-polkit-1.0 0.105-25
ii gir1.2-rsvg-2.0 2.44.10-1
ii gir1.2-soup-2.4 2.64.2-2
ii gir1.2-upowerglib-1.0 0.99.10-1
ii gjs 1.54.3-1
ii gnome-backgrounds 3.30.0-1
ii gnome-settings-daemon 3.30.2-3
ii gnome-shell-common 3.30.2-3
ii gsettings-desktop-schemas 3.28.1-1
ii libatk-bridge2.0-0 2.30.0-5
ii libatk1.0-0 2.30.0-2
ii libc6 2.28-8
ii libcairo2 1.16.0-4
ii libcanberra-gtk3-0 0.30-7
ii libcanberra0 0.30-7
ii libcroco3 0.6.12-3
ii libecal-1.2-19 3.30.5-1
ii libedataserver-1.2-23 3.30.5-1
ii libgcr-base-3-1 3.28.1-1
ii libgdk-pixbuf2.0-0 2.38.1+dfsg-1
ii libgirepository-1.0-1 1.58.3-2
ii libgjs0g 1.54.3-1
ii libglib2.0-0 2.58.3-1
ii libglib2.0-bin 2.58.3-1
ii libgstreamer1.0-0 1.14.4-1
ii libgtk-3-0 3.24.5-1
ii libical3 3.0.4-3
ii libjson-glib-1.0-0 1.4.4-2
ii libmutter-3-0 3.30.2-6
ii libnm0 1.14.6-2
ii libpango-1.0-0 1.42.4-6
ii libpangocairo-1.0-0 1.42.4-6
ii libpolkit-agent-1-0 0.105-25
ii libpolkit-gobject-1-0 0.105-25
ii libpulse-mainloop-glib0 12.2-4
ii libpulse0 12.2-4
ii libsecret-1-0 0.18.7-1
ii libstartup-notification0 0.12-6
ii libsystemd0 241-3
ii libx11-6 2:1.6.7-1
ii libxfixes3 1:5.0.3-1
ii mutter 3.30.2-6
ii python3 3.7.2-1
Versions of packages gnome-shell recommends:
ii bolt 0.7-2
ii chrome-gnome-shell 10.1-5
ii gdm3 3.30.2-3
ii gkbd-capplet 3.26.1-1
ii gnome-control-center 1:3.30.3-1
ii gnome-user-docs 3.30.2-1
ii iio-sensor-proxy 2.4-2
ii switcheroo-control 1.2-2
ii unzip 6.0-22
Versions of packages gnome-shell suggests:
ii gir1.2-telepathyglib-0.12 0.24.1-2
ii gir1.2-telepathylogger-0.2 0.8.2-3
Apr 15 10:50:47 gnome-shell[1646]: Object Shell.TrayIcon (0x55e2444efe90), has
been already deallocated — impossible to access it. This might be caused by the
object having been destroyed from C code using something such as destroy(),
dispose(), or remove() vfuncs.
Apr 15 10:50:47 org.gnome.Shell.desktop[1646]: == Stack trace for context
0x55e2413b31e0 ==
Apr 15 10:50:47 org.gnome.Shell.desktop[1646]: #0 55e24f0b0420 i
/usr/share/gnome-shell/extensions/topic...@phocean.net/extension.js:121
(7f1ab6c58af0 @ 92)
Apr 15 10:50:47 gnome-shell[1646]: clutter_actor_destroy: assertion
'CLUTTER_IS_ACTOR (self)' failed
Apr 15 10:51:50 gnome-shell[1646]: Object St.Button (0x55e2457acda0), has been
already deallocated — impossible to get any property from it. This might be
caused by the object having been destroyed from C code using something such as
destroy(), dispose(), or remove() vfuncs.
Apr 15 10:51:50 gnome-shell[1646]: Object St.Button (0x55e2457acda0), has been
already deallocated — impossible to access it. This might be caused by the
object having been destroyed from C code using something such as destroy(),
dispose(), or remove() vfuncs.
Apr 15 10:51:50 org.gnome.Shell.desktop[1646]: == Stack trace for context
0x55e2413b31e0 ==
Apr 15 10:51:50 org.gnome.Shell.desktop[1646]: #0 7ffdf9b09450 b
resource:///org/gnome/shell/ui/boxpointer.js:234 (7f1ab7b1b670 @ 574)
Apr 15 10:51:50 org.gnome.Shell.desktop[1646]: #1 7ffdf9b09530 b
resource:///org/gnome/gjs/modules/_legacy.js:82 (7f1ab7fb0b80 @ 71)
Apr 15 10:51:50 org.gnome.Shell.desktop[1646]: #2 7ffdf9b09610 b
self-hosted:981 (7f1ab7ff01f0 @ 474)
Apr 15 10:51:50 org.gnome.Shell.desktop[1646]: #3 7ffdf9b0b090 b
resource:///org/gnome/shell/ui/layout.js:211 (7f1ab7b01790 @ 62)
Apr 15 10:51:50 org.gnome.Shell.desktop[1646]: == Stack trace for context
0x55e2413b31e0 ==
Apr 15 10:51:50 org.gnome.Shell.desktop[1646]: #0 55e24eeb0470 i
resource:///org/gnome/shell/ui/boxpointer.js:448 (7f1ab7b1b8b0 @ 179)
Apr 15 10:51:50 org.gnome.Shell.desktop[1646]: #1 7ffdf9b08830 b
resource:///org/gnome/gjs/modules/_legacy.js:82 (7f1ab7fb0b80 @ 71)
Apr 15 10:51:50 org.gnome.Shell.desktop[1646]: #2 7ffdf9b09450 b
resource:///org/gnome/shell/ui/boxpointer.js:235 (7f1ab7b1b670 @ 597)
Apr 15 10:51:50 org.gnome.Shell.desktop[1646]: #3 7ffdf9b09530 b
resource:///org/gnome/gjs/modules/_legacy.js:82 (7f1ab7fb0b80 @ 71)
Apr 15 10:51:50 org.gnome.Shell.desktop[1646]: #4 7ffdf9b09610 b
self-hosted:981 (7f1ab7ff01f0 @ 474)
Apr 15 10:51:50 org.gnome.Shell.desktop[1646]: #5 7ffdf9b0b090 b
resource:///org/gnome/shell/ui/layout.js:211 (7f1ab7b01790 @ 62)
Apr 15 10:51:50 kernel: gnome-shell[1646]: segfault at fffffffffffffbc8 ip
00007f1af86f5ae8 sp 00007ffdf9b07780 error 5 in libst-1.0.so[7f1af86ce000+2c000]
Apr 15 10:51:50 kernel: Code: ff 90 48 8d 3d 37 7c 00 00 e9 74 93 fd ff 0f 1f
40 00 41 57 41 56 41 55 41 54 55 53 48 83 ec 28 48 63 1d bb 88 01 00 48 01 fb
<48> 8b 6b 08 48 85 ed 74 17 48 83 c4 28 48 89 e8 5b 5d 41 5c 41 5d
62ee3d858614ac38e34b0b91d1f7f47c2114b286c39b0a4a01d83670ebd5cc46
gnome-shell-coredump.xz
--- End Message ---
--- Begin Message ---
Version: 3.34.0-1
--- End Message ---
