Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to Install on PopOS 20.04 #774

Open
jeremyakers opened this issue Jan 20, 2023 · 6 comments
Open

Unable to Install on PopOS 20.04 #774

jeremyakers opened this issue Jan 20, 2023 · 6 comments

Comments

@jeremyakers
Copy link

jeremyakers commented Jan 20, 2023

I'm trying to install the system monitor applet. I've tried installing via both Chrome (109.0.5414.74) and Firefox (108.0.2)
First thing I notice both browsers show this warning even before I attempted to install:
Screenshot 2023-01-20 at 14-22-06 system-monitor - GNOME Shell Extensions

In an attempt to resolve this, before even installing: I check the docs at the specified link which say to install gnome-chrome-shell:
https://wiki.gnome.org/action/show/Projects/GnomeShellIntegration/Installation?action=show&redirect=Projects%2FGnomeShellIntegrationForChrome%2FInstallation#Ubuntu_Linux
Like so:
Screenshot 2023-01-20 at 14-23-56 Projects_GnomeShellIntegration_Installation - GNOME Wiki!

Which I already had installed:

$ dpkg -l chrome-gnome-shell
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name               Version      Architecture Description
+++-==================-============-============-===================================================
ii  chrome-gnome-shell 10.1-5       all          GNOME Shell extensions integration for web browsers

I have the browser plugin installed for both Chrome and Firefox:
Screenshot from 2023-01-20 14-27-36

So since I seem to have all the required components installed: I went ahead and tried to install the system-monitor extension. Firefox prompts me for permission to install, which I grant, and it just says "ERROR":
Screenshot 2023-01-20 at 14-11-48 system-monitor - GNOME Shell Extensions

If I refresh the page it adds the button to configure the extension:
Screenshot 2023-01-20 at 14-30-57 system-monitor - GNOME Shell Extensions

I'm able to open the preferences / configuration GUI:
Screenshot from 2023-01-20 14-12-15

Running gnome-extensions info/show just shows:

$ gnome-extensions show system-monitor@paradoxxx.zero.gmail.com
system-monitor@paradoxxx.zero.gmail.com
  Name: system-monitor
  Description: Display system information in GNOME Shell status bar, such as memory, CPU, disk and battery usages, network rates…
  Path: /home/jeremy/.local/share/gnome-shell/extensions/system-monitor@paradoxxx.zero.gmail.com
  URL: https://github.com/paradoxxxzero/gnome-shell-system-monitor-applet
  Version: 40
  State: ERROR
$ gnome-extensions info system-monitor@paradoxxx.zero.gmail.com
system-monitor@paradoxxx.zero.gmail.com
  Name: system-monitor
  Description: Display system information in GNOME Shell status bar, such as memory, CPU, disk and battery usages, network rates…
  Path: /home/jeremy/.local/share/gnome-shell/extensions/system-monitor@paradoxxx.zero.gmail.com
  URL: https://github.com/paradoxxxzero/gnome-shell-system-monitor-applet
  Version: 40
  State: ERROR

I have the pre-reqs installed:

$ sudo apt install gir1.2-gtop-2.0 gir1.2-nm-1.0 gir1.2-clutter-1.0 gnome-system-monitor
Reading package lists... Done
Building dependency tree       
Reading state information... Done
gir1.2-clutter-1.0 is already the newest version (1.26.4+dfsg-1).
gir1.2-gtop-2.0 is already the newest version (2.40.0-2).
gir1.2-nm-1.0 is already the newest version (1.22.10-1ubuntu2.3).
gnome-system-monitor is already the newest version (3.36.1-0ubuntu0.20.04.1).

I also tried downloading the ZIP and installing/enabling via gnome-extensions CLI.

I'm lost as to how to troubleshoot this any further. How do I access an actual log/stacktrace/etc for why the extension is failing to load?

System info:
Screenshot from 2023-01-20 14-40-53

EDIT: I installed gnome-shell-extensions-manager and that gave me access to the underlying error message:
Error: Tried to construct an object without a GType; are you using GObject.registerClass() when inheriting from a GObject type?

@jeremyakers
Copy link
Author

Updated to add:
I installed gnome-shell-extensions-manager and that gave me access to the underlying error message:
Error: Tried to construct an object without a GType; are you using GObject.registerClass() when inheriting from a GObject type?

@jeremyakers
Copy link
Author

After installing gnome-shell-extensions-manager, and using that to finally get at the true underlying error message: I searched the issues here on github and found the solution:

Alt-F2 then r

This reloaded gnome-shell and fixed it for me.

@ZimbiX
Copy link
Collaborator

ZimbiX commented Jan 21, 2023

I'm glad you figured that out. To see error logging:

journalctl -f /usr/bin/gnome-shell /usr/bin/gjs

For more up-to-date Gnome Shell versions, you'd need to instead install system-monitor-next due to delays from the current maintainers of this repo

@ZimbiX
Copy link
Collaborator

ZimbiX commented Jan 21, 2023

I think this issue can be closed now. Needing to reload after installing is common to many Gnome extensions. I don't yet know why it's the case here. If it's going to be addressed, there should be an issue dedicated to that, if it's still a problem with system-monitor-next.

@ZimbiX
Copy link
Collaborator

ZimbiX commented Jan 21, 2023

Oh, and I haven't seen that warning before. Maybe it's because your distro's Gnome packages are older than what the website / browser extension is expecting...

@jeremyakers
Copy link
Author

Yeah I guess my only feedback would be to add a step in the documentation that says reloading may be necessary (And explain how). I've personally never had to reload for any other extensions I've installed, and even though I've been a GNOME user for many, many years I did not even know about that reload command.

I think it's fine that reload may be necessary, but a user may not know that it's necessary nor how to do it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants