** Description changed: This is https://github.com/paradoxxxzero/gnome-shell-system-monitor- applet/issues/449. - [Impact] + [Impact] When the gnome-shell-extension-system-monitor is enabled, after the user's session is locked then unlocked, then gnome-shell starts profusely logging errors of this sort: Aug 09 17:34:44 localhost org.gnome.Shell.desktop[16993]: == Stack trace for context 0x556916f3c320 == Aug 09 17:34:44 localhost org.gnome.Shell.desktop[16993]: #0 0x5569172eba10 i /usr/share/gnome-shell/extensions/system-moni...@paradoxxx.zero.gmail.com/extension.js:2009 (0x7fcadae3db38 @ 39) Aug 09 17:34:44 localhost org.gnome.Shell.desktop[16993]: #1 0x7ffcee147f70 b resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7fcb140b5de0 @ 71) Aug 09 17:34:44 localhost org.gnome.Shell.desktop[16993]: #2 0x7ffcee148760 b /usr/share/gnome-shell/extensions/system-moni...@paradoxxx.zero.gmail.com/extension.js:928 (0x7fcb02dac340 @ 70) Aug 09 17:34:44 localhost org.gnome.Shell.desktop[16993]: #3 0x7ffcee148820 b resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7fcb140b5de0 @ 71) Aug 09 17:34:44 localhost org.gnome.Shell.desktop[16993]: #4 0x7ffcee1488d0 b self-hosted:913 (0x7fcb140f12b8 @ 346) Aug 09 17:34:45 localhost gnome-shell[16993]: Object Gio.Settings (0x55692427b520), has been already deallocated - impossible to access to it. This might be caused by the fact that the object has been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs This will quickly fill the logs to the limits of what journald allows (4G here) and make observing the log difficult in general (since the log entries come in at the frequency of enabled monitors of the extension). [Test Case] 1. apt-get install gnome-shell-extension-system-monitor 2. enable the extension in gnome-tweaks 3. lock the screen, wait a few seconds, then log back in - 4. observe in journalctl --follow the stack traces for the extension. If you disable the extension, the logging stops + 4. observe in journalctl --follow the stack traces for the extension. If you disable the extension, the logging stops. Sometimes it takes a couple of minutes for the log spamming to start after logging back in When testing the fix, it is important that after upgrading to the new version, you logout of your session then back in. Disabling/enabling the extension does not seem to be enough. [Regression Potential] Regression potential is considered low since the patch simply moves the initialization code into the enable() function (gnome-shell appears to disable the extension on lock, and enable on unlock).
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1786608 Title: gio.settings errors after lockscreen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-system-monitor/+bug/1786608/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
