Your message dated Thu, 14 Feb 2019 16:13:24 +0000 with message-id <[email protected]> and subject line Re: Bug#922218: gnome-shell fills up logs with an stack trace has caused the Debian Bug report #922218, regarding gnome-shell fills up logs with an stack trace 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 [email protected] immediately.) -- 922218: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922218 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: gnome-shell Version: 3.30.1-2 Severity: critical Justification: breaks the whole system Dear Maintainer, gnome-shell is making my system unusable by completelly filling up the /var partition due to the errors it spits into several log files like syslog, user.log and messages. All three of them are Gigabytes of size. The issue that is reported by gnome-shell (hundreds of times per second!) is the following: Feb 12 14:54:25 dori gnome-shell[5179]: Object St.Icon (0x556220576a40), has been already finalized. Impossible to set any property to it. Feb 12 14:54:25 dori org.gnome.Shell.desktop[5179]: == Stack trace for context 0x55621f7d6340 == Feb 12 14:54:25 dori org.gnome.Shell.desktop[5179]: #0 0x55621fc4b2b0 i resource:///org/gnome/shell/ui/osdWindow.js:223 (0x7f055c6c9b38 @ 231) Feb 12 14:54:25 dori org.gnome.Shell.desktop[5179]: #1 0x7ffc616fdf90 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f057c0b5de0 @ 71) Feb 12 14:54:25 dori org.gnome.Shell.desktop[5179]: #2 0x7ffc616fe710 b self-hosted:916 (0x7f057c0f1230 @ 367) Feb 12 14:54:25 dori org.gnome.Shell.desktop[5179]: #3 0x7ffc616fe800 b resource:///org/gnome/gjs/modules/signals.js:128 (0x7f057c0d2230 @ 386) Feb 12 14:54:25 dori org.gnome.Shell.desktop[5179]: #4 0x55621fc4b228 i resource:///org/gnome/shell/ui/layout.js:530 (0x7f055c603230 @ 127) Feb 12 14:54:25 dori org.gnome.Shell.desktop[5179]: #5 0x55621fc4b180 i resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f057c0b5de0 @ 71) Feb 12 14:54:25 dori org.gnome.Shell.desktop[5179]: #6 0x55621fc4b0c0 i self-hosted:916 (0x7f057c0f1230 @ 367) I'm setting a critical severity because as you might imagine, once the var partition is full several unrelated software starts to break. Also for non technical users rebooting wouldn't be a solution as the logs will persist. -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (800, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-1-amd64 (SMP w/40 CPU cores) Locale: LANG=gl_ES.UTF-8, LC_CTYPE=gl_ES.UTF-8 (charmap=UTF-8), LANGUAGE=gl_ES.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.4-1 ii gir1.2-accountsservice-1.0 0.6.45-1 ii gir1.2-atspi-2.0 2.30.0-5 ii gir1.2-freedesktop 1.58.3-2 ii gir1.2-gcr-3 3.28.0-4 ii gir1.2-gdesktopenums-3.0 3.28.1-1 ii gir1.2-gdm-1.0 3.30.1-1 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-4 ii gir1.2-gtk-3.0 3.24.3-1 ii gir1.2-gweather-3.0 3.28.2-2 ii gir1.2-ibus-1.0 1.5.19-1 ii gir1.2-mutter-3 3.30.2-4 ii gir1.2-nm-1.0 1.14.4-4 ii gir1.2-nma-1.0 1.8.18-2 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.9-2 ii gjs 1.52.4-1 ii gnome-backgrounds 3.30.0-1 ii gnome-settings-daemon 3.30.2-1 ii gnome-shell-common 3.30.1-2 ii gsettings-desktop-schemas 3.28.1-1 ii libatk-bridge2.0-0 2.30.0-2 ii libatk1.0-0 2.30.0-2 ii libc6 2.28-5 ii libcairo2 1.16.0-2 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.4-1 ii libedataserver-1.2-23 3.30.4-1 ii libgcr-base-3-1 3.28.0-4 ii libgdk-pixbuf2.0-0 2.38.0+dfsg-7 ii libgirepository-1.0-1 1.58.3-2 ii libgjs0g 1.52.4-1 ii libglib2.0-0 2.58.2-3 ii libglib2.0-bin 2.58.2-3 ii libgstreamer1.0-0 1.14.4-1 ii libgtk-3-0 3.24.3-1 ii libical3 3.0.4-3 ii libjson-glib-1.0-0 1.4.4-2 ii libmutter-3-0 3.30.2-4 ii libnm0 1.14.4-4 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-3 ii libpulse0 12.2-3 ii libsecret-1-0 0.18.7-1 ii libstartup-notification0 0.12-6 ii libsystemd0 240-4 ii libx11-6 2:1.6.7-1 ii libxfixes3 1:5.0.3-1 ii mutter 3.30.2-4 ii python3 3.7.1-3 Versions of packages gnome-shell recommends: ii bolt 0.7-2 ii chrome-gnome-shell 10.1-4 ii gdm3 3.30.1-1 ii gkbd-capplet 3.26.0-5 ii gnome-control-center 1:3.30.2-3 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-21 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 -- no debconf information
--- End Message ---
--- Begin Message ---Version: 3.30.2-3 On Thu, 14 Feb 2019 at 15:53:03 +0100, Sergio Villar Senin wrote: > O Mér, 13-02-2019 ás 11:30 +0000, Simon McVittie escribiu: > > Does this problem persist if you upgrade gnome-shell, mutter and gjs > > to the versions in unstable? (These versions should have migrated to > > testing a while ago, but are being held up by uninstallability on > > s390x; > > the release team assure me that they intend to get these versions > > into > > buster before the release.) > > That made it. I upgraded gnome-shell to unstable version and the > problem is gone. Thanks, closing as fixed in the current unstable version of gnome-shell. (It might really be a gjs bug, but they'll migrate together anyway, so it doesn't really matter.) smcv
--- End Message ---
