After installing gnome-shell-extension-system-monitor-applet it cannot be activated and extensions.gnome.org tells: INCOMPATIBLE This extension is incompatible with your GNOME Shell version. For GNOME Shell 3.12 or newer you can set "disable-extension-version-validation" dconf setting to true to force installation of incompatible extensions. The upstream bug for this is: > Needs update to run on GNOME 44 > https://github.com/paradoxxxzero/gnome-shell-system-monitor-applet/issues/791 The workaround mentioned there (adding '44' to the version list in metadata.json appears to have been applied already. Reproducible: Always Steps to Reproduce: 1. Install gnome-shell-extension-system-monitor-applet 2. Visit https://extensions.gnome.org/extension/120/system-monitor/ 3. INCOMPATIBLE Actual Results: gnome-shell-extension-system-monitor-applet cannot be activated. Expected Results: gnome-shell-extension-system-monitor-applet should be usable.
Hello, Thanks for reporting this issue. As you said it, the patch for Gnome 44 is already applied in the sources of the gnome-shell-extension-system-monitor-applet rpm package. To activate this Gnome Shell Extension in your user's session, you have to use the gnome-extensions-app application. To install it (in a root console or via sudo): dnf install gnome-extensions-app The gnome-shell-extension-system-monitor-applet rpm package installs at the system level (for all users) this Gnome Shell Extension. Once activated in your session, your own settings are saved locally, but the extension is still available globally for all users. If you try to activate it through the Gnome Shell Extension web site: https://extensions.gnome.org/extension/120/system-monitor/ This will locally (in your user session) installs the extension available on this website. This one will take priority over the global version. Unfortunately, the version available on this website is not up to date and is incompatible with Gnome 44. So, you need to disable the version installed from this website, remove it from your user directory, usually located here: ~/.local/share/gnome-shell/extensions/ See https://gjs.guide/extensions/overview/anatomy.html#extension-zip for more on this subject. Once the extension uninstalled from your user account, the globally installed extension through the rpm package should be available and functional. Maybe you should close and re-open your user session in the process before using gnome-extensions-app to activate it. Hope this will help you to achieve your goal. Feel free to make any comment about these subjects. Cordially, -- NVieville
I don't know why/how, this seems to be broken in the last few weeks, currently at: gnome-shell-44.5-1.fc38.x86_64 gnome-shell-extension-system-monitor-applet-38-23.20230420git21d7b4e.fc38.noarch it seems that gnome-shell 44.4 to 44.5 (mutter 44.4 to 44.5) broke it?
Hello, @Hin-Tak Leung, thank you for reporting this issue. Could you please try to check your installation/configuration of this gnome-shell extension, as explained in post #1? Could you please also describe the issue further, as don't really get what broken could mean. Is there no extension available in your gnome session? Is the extension showing up, but not functioning correctly? It would be also helpful if you could post the text of an error or a warning emitted by the extension while working. For this, you can refer to the this Web page https://gjs.guide/extensions/development/debugging.html#looking-glass You can launch looking-glass (Alt + F2), then click on the Extensions button, scroll to gnome-shell-extension-system-monitor-applet and finally click on show errors. You also can get some information through a root terminal with journalctl cli. You could then type a command line like: journalctl -q --no-pager /usr/bin/gnome-shell | grep monitor And explore the output to look for a possible error. A report of the errors will be very helpful to try to catch this issue. For my part, I'm using the same packages as you describe: gnome-shell-44.5-1.fc38.x86_64 gnome-shell-extension-system-monitor-applet-38-23.20230420git21d7b4e.fc38.noarch And no issue noted, everything is working on multiple machines. Feel free to make any comment about this issue. Cordially, -- NVieville
Fedora Linux 38 entered end-of-life (EOL) status on 2024-05-21. Fedora Linux 38 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.