| 2018-08-11 11:54:09 |
Jamie Strandboge |
bug |
|
|
added bug |
| 2018-08-11 11:54:29 |
Jamie Strandboge |
nominated for series |
|
Ubuntu Cosmic |
|
| 2018-08-11 11:54:29 |
Jamie Strandboge |
bug task added |
|
gnome-shell-extension-system-monitor (Ubuntu Cosmic) |
|
| 2018-08-11 11:54:29 |
Jamie Strandboge |
nominated for series |
|
Ubuntu Bionic |
|
| 2018-08-11 11:54:29 |
Jamie Strandboge |
bug task added |
|
gnome-shell-extension-system-monitor (Ubuntu Bionic) |
|
| 2018-08-11 11:58:52 |
Jamie Strandboge |
gnome-shell-extension-system-monitor (Ubuntu Bionic): status |
New |
Triaged |
|
| 2018-08-11 11:58:55 |
Jamie Strandboge |
gnome-shell-extension-system-monitor (Ubuntu Bionic): assignee |
|
Jamie Strandboge (jdstrand) |
|
| 2018-08-11 11:58:58 |
Jamie Strandboge |
gnome-shell-extension-system-monitor (Ubuntu Cosmic): assignee |
|
Jamie Strandboge (jdstrand) |
|
| 2018-08-11 11:59:05 |
Jamie Strandboge |
gnome-shell-extension-system-monitor (Ubuntu Bionic): importance |
Undecided |
High |
|
| 2018-08-11 11:59:07 |
Jamie Strandboge |
gnome-shell-extension-system-monitor (Ubuntu Cosmic): importance |
Undecided |
High |
|
| 2018-08-11 11:59:11 |
Jamie Strandboge |
gnome-shell-extension-system-monitor (Ubuntu Cosmic): status |
New |
Triaged |
|
| 2018-08-11 12:03:16 |
Jamie Strandboge |
gnome-shell-extension-system-monitor (Ubuntu Cosmic): status |
Triaged |
In Progress |
|
| 2018-08-11 12:03:21 |
Jamie Strandboge |
gnome-shell-extension-system-monitor (Ubuntu Cosmic): status |
In Progress |
Fix Committed |
|
| 2018-08-11 12:12:12 |
Jamie Strandboge |
gnome-shell-extension-system-monitor (Ubuntu Bionic): status |
Triaged |
In Progress |
|
| 2018-08-11 12:13:04 |
Jamie Strandboge |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2018-08-11 12:29:05 |
Jamie Strandboge |
bug watch added |
|
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904442 |
|
| 2018-08-11 12:29:05 |
Jamie Strandboge |
bug task added |
|
gnome-shell-extension-system-monitor (Debian) |
|
| 2018-08-11 12:35:38 |
Launchpad Janitor |
gnome-shell-extension-system-monitor (Ubuntu Cosmic): status |
Fix Committed |
Fix Released |
|
| 2018-08-11 12:51:27 |
Bug Watch Updater |
gnome-shell-extension-system-monitor (Debian): status |
Unknown |
New |
|
| 2018-08-20 15:29:35 |
Łukasz Zemczak |
gnome-shell-extension-system-monitor (Ubuntu Bionic): status |
In Progress |
Fix Committed |
|
| 2018-08-20 15:29:38 |
Łukasz Zemczak |
bug |
|
|
added subscriber SRU Verification |
| 2018-08-20 15:29:42 |
Łukasz Zemczak |
tags |
|
verification-needed verification-needed-bionic |
|
| 2018-08-20 20:00:06 |
Jamie Strandboge |
description |
This is https://github.com/paradoxxxzero/gnome-shell-system-monitor-applet/issues/449.
[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-monitor@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-monitor@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
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). |
This is https://github.com/paradoxxxzero/gnome-shell-system-monitor-applet/issues/449.
[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-monitor@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-monitor@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. 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). |
|
| 2018-08-20 20:06:02 |
Jamie Strandboge |
tags |
verification-needed verification-needed-bionic |
verification-done verification-done-bionic |
|
| 2018-08-27 07:47:55 |
Launchpad Janitor |
gnome-shell-extension-system-monitor (Ubuntu Bionic): status |
Fix Committed |
Fix Released |
|
| 2018-08-27 07:47:58 |
Łukasz Zemczak |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2020-02-21 08:12:54 |
Bug Watch Updater |
gnome-shell-extension-system-monitor (Debian): status |
New |
Fix Released |
|
