GNOME 3.34 support, please!

[zefkerr]

I believe that you can do it! Thank you!

[chrisspen]

Feel free to submit a pull request. I'm on 3.28, and I'm in no hurry to upgrade. All that might be needed is to add 3.34 to the version list in metadata.json, but we need someone to test.

[zefkerr]

Feel free to submit a pull request. I'm on 3.28, and I'm in no hurry to upgrade. All that might be needed is to add 3.34 to the version list in metadata.json, but we need someone to test.

I can test it if you need it.

[chrisspen]

Ok, I've made the change. Install from master as explained in the README and let me know if you have any issues.

[recteurlp]

I just installed the RPM from F31 Beta it is working great on Gnome 3.34 ><

Name        : gnome-shell-extension-system-monitor-applet
Epoch       : 1
Version     : 38
Release     : 3.20190515gitfc83a73.fc31
Architecture: noarch
Install Date: mer. 25 sept. 2019 01:00:54 CEST
Group       : Unspecified
Size        : 244369
License     : GPLv3+ and BSD
Signature   : RSA/SHA256, mar. 30 juil. 2019 08:28:16 CEST, Key ID 50cb390b3c3359c4
Source RPM  : gnome-shell-extension-system-monitor-applet-38-3.20190515gitfc83a73.fc31.src.rpm
Build Date  : jeu. 25 juil. 2019 09:28:51 CEST

Can we change/cutomize the "system monitor" button to launch the new "gnome-usage" app with some new pref menu ?

Otherwise:

sudo sed -i 's/gnome-system-monitor.desktop/org.gnome.Usage.desktop/g' /usr/share/gnome-shell/extensions/[email protected]/extension.js

Alt+F2
r

[chrisspen]

I don't control the Fedora packaging. You'd have to ask whoever manages that in the Fedora community.

[nschloe]

I couldn't get this to work on Ubuntu 19.10 (to be released) yet. Where are the error messages logged?

[chrisspen]

I believe all errors go to /var/log/syslog.

[mattia-b89]

I installed -git version on Arch Linux w/ gnome-shell 3.34
and I confirm it works! but with some flaws First, this error throws when I enable the extension, from gnome-tweaks-tool:

Sep 26 19:31:38 arch-xps gnome-shell[16170]: [System monitor] applet enabling
Sep 26 19:31:38 arch-xps gnome-shell[16170]: Usage of object.actor is deprecated for PanelMenuButton
                                             get@resource:///org/gnome/shell/ui/environment.js:242:29
                                             enable@/usr/share/gnome-shell/extensions/[email protected]/extension.js:2339:9
                                             _callExtensionEnable@resource:///org/gnome/shell/ui/extensionSystem.js:131:13
                                             _onEnabledExtensionsChanged/<@resource:///org/gnome/shell/ui/extensionSystem.js:398:13
                                             _onEnabledExtensionsChanged@resource:///org/gnome/shell/ui/extensionSystem.js:395:9
Sep 26 19:31:38 arch-xps gnome-shell[16170]: [System monitor] applet enabling done

Second, when I open preferences window, still from gnome-tweaks-tool

Sep 26 19:34:32 arch-xps gnome-shell[16170]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3000007
Sep 26 19:34:32 arch-xps gnome-shell-ext[16579]: gtk_box_pack: assertion '_gtk_widget_get_parent (child) == NULL' failed
Sep 26 19:34:32 arch-xps gnome-shell-ext[16579]: gtk_box_pack: assertion '_gtk_widget_get_parent (child) == NULL' failed
Sep 26 19:34:32 arch-xps gnome-shell-ext[16579]: gtk_box_pack: assertion '_gtk_widget_get_parent (child) == NULL' failed
Sep 26 19:34:32 arch-xps gnome-shell-ext[16579]: gtk_box_pack: assertion '_gtk_widget_get_parent (child) == NULL' failed
Sep 26 19:34:32 arch-xps gnome-shell-ext[16579]: gtk_box_pack: assertion '_gtk_widget_get_parent (child) == NULL' failed
Sep 26 19:34:32 arch-xps gnome-shell-ext[16579]: gtk_box_pack: assertion '_gtk_widget_get_parent (child) == NULL' failed
Sep 26 19:34:32 arch-xps gnome-shell-ext[16579]: gtk_box_pack: assertion '_gtk_widget_get_parent (child) == NULL' failed
Sep 26 19:34:32 arch-xps gnome-shell-ext[16579]: gtk_box_pack: assertion '_gtk_widget_get_parent (child) == NULL' failed
Sep 26 19:34:32 arch-xps gnome-shell-ext[16579]: gtk_box_pack: assertion '_gtk_widget_get_parent (child) == NULL' failed
Sep 26 19:34:36 arch-xps gnome-shell-ext[16579]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Sep 26 19:34:36 arch-xps gnome-shell-ext[16579]: The offending signal was destroy on Gjs_ExtensionRow 0x55d1904387f0.
Sep 26 19:34:36 arch-xps org.gnome.tweaks.desktop[16170]: == Stack trace for context 0x55d18fac61a0 ==
Sep 26 19:34:36 arch-xps gnome-shell-ext[16579]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Sep 26 19:34:36 arch-xps org.gnome.tweaks.desktop[16170]: == Stack trace for context 0x55d18fac61a0 ==
Sep 26 19:34:36 arch-xps gnome-shell-ext[16579]: The offending signal was destroy on Gjs_ExtensionRow 0x55d1903c5e00.
Sep 26 19:34:36 arch-xps org.gnome.tweaks.desktop[16170]: == Stack trace for context 0x55d18fac61a0 ==
Sep 26 19:34:36 arch-xps gnome-shell-ext[16579]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Sep 26 19:34:36 arch-xps gnome-shell-ext[16579]: The offending signal was destroy on Gjs_ExtensionRow 0x55d1902fc790.
Sep 26 19:34:36 arch-xps org.gnome.tweaks.desktop[16170]: == Stack trace for context 0x55d18fac61a0 ==
Sep 26 19:34:36 arch-xps gnome-shell-ext[16579]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Sep 26 19:34:36 arch-xps gnome-shell-ext[16579]: The offending signal was destroy on Gjs_ExtensionRow 0x55d1902fcd90.
Sep 26 19:34:36 arch-xps org.gnome.tweaks.desktop[16170]: == Stack trace for context 0x55d18fac61a0 ==
Sep 26 19:34:36 arch-xps gnome-shell-ext[16579]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Sep 26 19:34:36 arch-xps gnome-shell-ext[16579]: The offending signal was destroy on Gjs_ExtensionRow 0x55d1904381f0.
Sep 26 19:34:36 arch-xps org.gnome.tweaks.desktop[16170]: == Stack trace for context 0x55d18fac61a0 ==
Sep 26 19:34:36 arch-xps gnome-shell-ext[16579]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Sep 26 19:34:36 arch-xps gnome-shell-ext[16579]: The offending signal was destroy on Gjs_ExtensionRow 0x55d1903c5b00.
Sep 26 19:34:36 arch-xps org.gnome.tweaks.desktop[16170]: == Stack trace for context 0x55d18fac61a0 ==
Sep 26 19:34:36 arch-xps gnome-shell-ext[16579]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Sep 26 19:34:36 arch-xps gnome-shell-ext[16579]: The offending signal was destroy on Gjs_ExtensionRow 0x55d1903c5200.
Sep 26 19:34:36 arch-xps gnome-shell-ext[16579]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Sep 26 19:34:36 arch-xps org.gnome.tweaks.desktop[16170]: == Stack trace for context 0x55d18fac61a0 ==
Sep 26 19:34:36 arch-xps gnome-shell-ext[16579]: The offending signal was destroy on Gjs_ExtensionRow 0x55d1904384f0.
Sep 26 19:34:36 arch-xps gnome-shell-ext[16579]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Sep 26 19:34:36 arch-xps org.gnome.tweaks.desktop[16170]: == Stack trace for context 0x55d18fac61a0 ==
Sep 26 19:34:36 arch-xps gnome-shell-ext[16579]: The offending signal was destroy on Gjs_ExtensionRow 0x55d1903fea90.
Sep 26 19:34:36 arch-xps gnome-shell-ext[16579]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Sep 26 19:34:36 arch-xps gnome-shell-ext[16579]: The offending signal was destroy on Gjs_ExtensionRow 0x55d1903fe790.
Sep 26 19:34:36 arch-xps org.gnome.tweaks.desktop[16170]: == Stack trace for context 0x55d18fac61a0 ==
Sep 26 19:34:36 arch-xps gnome-shell-ext[16579]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Sep 26 19:34:36 arch-xps gnome-shell-ext[16579]: The offending signal was destroy on Gjs_ExtensionRow 0x55d1902fc190.
Sep 26 19:34:36 arch-xps gnome-shell-ext[16579]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Sep 26 19:34:36 arch-xps org.gnome.tweaks.desktop[16170]: == Stack trace for context 0x55d18fac61a0 ==
Sep 26 19:34:36 arch-xps gnome-shell-ext[16579]: The offending signal was destroy on Gjs_ExtensionRow 0x55d1902fca90.
Sep 26 19:34:36 arch-xps gnome-shell-ext[16579]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Sep 26 19:34:36 arch-xps org.gnome.tweaks.desktop[16170]: == Stack trace for context 0x55d18fac61a0 ==
Sep 26 19:34:36 arch-xps gnome-shell-ext[16579]: The offending signal was destroy on Gjs_ExtensionRow 0x55d1903c5500.
Sep 26 19:34:36 arch-xps gnome-shell-ext[16579]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Sep 26 19:34:36 arch-xps gnome-shell-ext[16579]: The offending signal was destroy on Gjs_ExtensionRow 0x55d1903c5800.
Sep 26 19:34:36 arch-xps org.gnome.tweaks.desktop[16170]: == Stack trace for context 0x55d18fac61a0 ==
Sep 26 19:34:36 arch-xps gnome-shell-ext[16579]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Sep 26 19:34:36 arch-xps gnome-shell-ext[16579]: The offending signal was destroy on Gjs_ExtensionRow 0x55d1903fed90.
Sep 26 19:34:36 arch-xps gnome-shell-ext[16579]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Sep 26 19:34:36 arch-xps gnome-shell-ext[16579]: The offending signal was destroy on Gjs_ExtensionRow 0x55d1903fe490.
Sep 26 19:34:36 arch-xps org.gnome.tweaks.desktop[16170]: == Stack trace for context 0x55d18fac61a0 ==
Sep 26 19:34:36 arch-xps gnome-shell-ext[16579]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Sep 26 19:34:36 arch-xps gnome-shell-ext[16579]: The offending signal was destroy on Gjs_ExtensionRow 0x55d1902fc490.
Sep 26 19:34:36 arch-xps gnome-shell-ext[16579]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Sep 26 19:34:36 arch-xps org.gnome.tweaks.desktop[16170]: == Stack trace for context 0x55d18fac61a0 ==
Sep 26 19:34:36 arch-xps gnome-shell-ext[16579]: The offending signal was destroy on Gjs_ExtensionRow 0x55d1903fe190.

[nschloe]

I couldn't get this to work on Ubuntu 19.10 (to be released) yet.

Working for me now, I had misconfigured gnome-tools.

[pcornelissen]

@nschloe Well I'm on 19.10 and it doesn't work, what did you do to get it to work?

[nschloe]

@pcornelissen Make sure to have Extensions enabled in Gnome Tweaks.

[tzstoyanov]

It works on Gnome 3.34 (tested on Fedora 31), but there is one issue - it plots the graph outside of the panel area:

Do you have any idea where this size is set ?

[jbouzekri]

@tzstoyanov : No issue on Ubuntu 19.10 with Gnome 3.34.1. However I don't have the native theme but arc-theme.

[alexkutsan]

Does not work on NixOS. Also marked as broken for NixOS after upgrading to gnome 3.34 https://github.com/NixOS/nixpkgs/pull/68608/files#diff-9da0fbd5440fe0d34c10746cbe5017af

Can someone create fix for latest gnome? This system monitor is the best from all existing.

[zefkerr]

Can you add updated version for GNOME 3.34 to the extension site? https://extensions.gnome.org/extension/120/system-monitor/

[szpak]

In Fedora 31 with Gnome 3.34 the extension from RPM - gnome-shell-extension-system-monitor-applet-38-4.20191019gitf00e248 - generates the aforementioned warning:

Usage of object.actor is deprecated for PanelMenuButton

but in general it works.

[rimas-kudelis]

I can also confirm that this extension works fine with Gnome 3.34.2 on Ubuntu 19.10 after adding "3.34" to the version list.

[scarlion1]

Edit: sorry maybe it's a different bug #575

On Debian 10 testing with Gnome 3.34.2 i tried adding "3.34" to the metadata.json but it's still not loading. Unfortunate because it was working before Gnome told me to upgrade it. Any ideas to get it running? Thanks

Apr 13 17:20:26 throne gnome-shell[1455]: [System monitor] applet init from /home/scar/.local/share/gnome-shell/extensions/[email protected]
Apr 13 17:20:26 throne gnome-shell[1455]: JS ERROR: Extension [email protected]: Error: Tried to construct an object without a GType; are you using GObject.registerClass() when inheriting from a GObject type?#012SystemMonitor_TipItem@/home/scar/.local/share/gnome-shell/extensions/[email protected]/extension.js:640:9#012tip_format@/home/scar/.local/share/gnome-shell/extensions/[email protected]/extension.js:898:27#012SystemMonitor_Cpu@/home/scar/.local/share/gnome-shell/extensions/[email protected]/extension.js:1196:14#012createCpus@/home/scar/.local/share/gnome-shell/extensions/[email protected]/extension.js:1363:20#012enable@/home/scar/.local/share/gnome-shell/extensions/[email protected]/extension.js:2316:26#012_callExtensionEnable@resource:///org/gnome/shell/ui/extensionSystem.js:148:32#012loadExtension@resource:///org/gnome/shell/ui/extensionSystem.js:280:26#012_loadExtensions/<@resource:///org/gnome/shell/ui/extensionSystem.js:490:18#012collectFromDatadirs@resource:///org/gnome/shell/misc/fileUtils.js:27:17#012_loadExtensions@resource:///org/gnome/shell/ui/extensionSystem.js:469:19#012_enableAllExtensions@resource:///org/gnome/shell/ui/extensionSystem.js:499:18#012_sessionUpdated@resource:///org/gnome/shell/ui/extensionSystem.js:530:18#012init@resource:///org/gnome/shell/ui/extensionSystem.js:48:14#012_initializeUI@resource:///org/gnome/shell/ui/main.js:242:22#012start@resource:///org/gnome/shell/ui/main.js:138:5#012@<main>:1:47
Apr 13 17:20:28 throne gnome-shell[1455]: JS WARNING: [/home/scar/.local/share/gnome-shell/extensions/[email protected]/extension.js 925]: reference to undefined property 0
Apr 13 17:20:28 throne gnome-shell[1455]: JS ERROR: TypeError: this.tip_labels[i] is undefined#012update@/home/scar/.local/share/gnome-shell/extensions/[email protected]/extension.js:925:56
Apr 13 17:20:39 throne gnome-software[1626]: failed to create an app for user/*/extensions-web/shell-extension/system-monitor_paradoxxx.zero.gmail.com/*

Get the same error when I try the git version, which already has version 3.34 support,

Apr 13 17:38:58 throne gnome-shell[1455]: [System monitor] applet init from /home/scar/.local/share/gnome-shell/extensions/[email protected]
Apr 13 17:38:58 throne gnome-shell[1455]: JS ERROR: Extension [email protected]: Error: Tried to construct an object without a GType; are you using GObject.registerClass() when inheriting from a GObject type?#012SystemMonitor_TipItem@/home/scar/.local/share/gnome-shell/extensions/[email protected]/extension.js:669:13#012tip_format@/home/scar/.local/share/gnome-shell/extensions/[email protected]/extension.js:946:27#012SystemMonitor_Cpu@/home/scar/.local/share/gnome-shell/extensions/[email protected]/extension.js:1241:14#012createCpus@/home/scar/.local/share/gnome-shell/extensions/[email protected]/extension.js:1408:20#012enable@/home/scar/.local/share/gnome-shell/extensions/[email protected]/extension.js:2341:26#012_callExtensionEnable@resource:///org/gnome/shell/ui/extensionSystem.js:148:32#012loadExtension@resource:///org/gnome/shell/ui/extensionSystem.js:280:26#012_loadExtensions/<@resource:///org/gnome/shell/ui/extensionSystem.js:490:18#012collectFromDatadirs@resource:///org/gnome/shell/misc/fileUtils.js:27:17#012_loadExtensions@resource:///org/gnome/shell/ui/extensionSystem.js:469:19#012_enableAllExtensions@resource:///org/gnome/shell/ui/extensionSystem.js:499:18#012_sessionUpdated@resource:///org/gnome/shell/ui/extensionSystem.js:530:18#012init@resource:///org/gnome/shell/ui/extensionSystem.js:48:14#012_initializeUI@resource:///org/gnome/shell/ui/main.js:242:22#012start@resource:///org/gnome/shell/ui/main.js:138:5#012@<main>:1:47

[mattia-b89]

@scarf did you try the -git version?

[scarlion1]

yeah @mattia-b89 i added that to the end of my comment above, but i think it might be a different bug #575 . No one else here has mentioned the error I'm getting....

[franglais125]

@scarf you might be very unlucky with the timing perhaps. gjs migrated to testing yesterday*, which means you have a weird mixture of packages (not your fault, migrating the whole 3.36 from sid takes time).

You can wait for gnome-shell, mutter and the other bunch to migrate. I'm expecting that this will fix the problem for you.

*https://tracker.debian.org/pkg/gjs

[vkbo]

Yeah, ran into this too. I noticed you posted on the the latest bug report on Debian, so if it's in the pipeline, I'll just sit tight and wait till the packages are through to testing.

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956171

[vkbo]

I can confirm that the package in Debian unstable now works with 3.36.1 packages from testing.

The only issue, which is a minor one, is that the hover labels aren't always entirely cleared from the screen buffer. Sometimes a vertical line from the left edge of the frame remains. This is on wayland though, running the latest amdgpu firmware directly from the firmware repo.

I cannot make a screenshot, because the print screen feature clears the artefacts before the screenshot is taken.

[franglais125]

@vkbo I can't reproduce this (Debian sid, Wayland). Would you mind taking a picture with a phone or other means?

[vkbo]

This is what it looks like.

[franglais125]

@vkbo Perhaps it was just luck/chance, but I just saw that as well.

It seems to me that this glitch could rather be due to the big graphics overhaul that took place in 3.36. Let's see how this evolves as the various point releases fix a few bugs.

[vkbo]

Yes, it does come and go a bit for me too. I'll keep an eye on it as well. It isn't really a big issue, and it clears itself away after a bit.

[mattia-b89]

Anyway, if 3.34 support is ok we should close this issue and open a new one for 3.36 on Debian (I, on Arch Linux it's fine)

[LuxoftAKutsan]

GNOME Shell 3.36.3 is broken now

[mgalgs]

@LuxoftAKutsan Can you please try -next?