Hello, Thanks for the feedback. There are actually bug report and pull request pending on upstream Github repository about the issue with Gnome 3.36. I've opened a bug report on Redhat Bugzilla about this to follow upstream discussions:

Feel free to make any comment on it.




Installation went fine, dependencies problem with python2-qt5-webkit are gone.

Problem with gnome-session-c and /dev/nvidiactl solved.

Hello Alex,

Time passes, and new ideas come. I wonder, and only if you don't mind, if you could give a try to a new attempt to catch this issue.

First, it would be interesting to verify the content of the directories listed in your XDG_DATA_DIRS environment variable:


If in the directories listed you find a glib-2.0/schemas sub-directory, verify that only one of them contains a file. If this file is present multiple times (different directories), maybe we have found the problem. You will probably find one in ~/.local/share/gnome-shell/extensions/ sub-directories too.

Before going further, please copy the metadata.json file from ~/.local/share/gnome-shell/extensions/ (the one that was installed with the extension from to a temporary folder. Then proceed as usual (uninstall the extension from and install the one from fedora repository). Before closing your session, overwrite the file /usr/share/gnome-shell/extensions/ with the one you saved in a temporary folder before. Then, close session, open new session, activate the newly installed extension and see what happens.

Please, comments are always welcome.

Best regards,


Hello Alex,

You're welcome. Thank you for trying to catch this issue. I'll push this package to updates.

Best regards,


Hello Alex,

Thank you very much for your feedback.

Before pushing this package to stable, I wonder if you could give one last try to these extension. In order to try to skip some possible side-effects, could you please try the alternative way from my last message? This alternative requires you to install this extension package (probably deactivating this extension from your current account maybe required to avoid one possible crash), then create a new fresh account on your system (if possible - needs to be root). Once this account exists, log into this account (not useful to reboot before, but who knows...). Gnome-shell will be launched with all parameters left to their default without any supplemental extension (don't forget to choose xorg session and not wayland). Launch Tweak-Tool and activate one extension only: gnome-shell gnome-shell-extension-system-monitor-applet. See what happens and comments if needed.

Once again thank you for your patience.

Best regards,


Hello Alex,

Thank you very much for trying to catch this issue and for providing all the logs of your tests.

Concerning bugzilla not listing this gnome-shell extension, I suppose as it is the first release of it in Fedora that it will appear once pushed to stable (my first package in Fedora so not so confident in this explanation). I think we have no other solution to keep on trying to debug this issue through this thread.

Concerning this issue, and to be sure of your configuration, I wonder if you could provide the output of the commands below typed in a terminal in your user's session, once you suppressed the extension installed from and you installed Fedora's one:

dnf list installed gnome-shell gnome-shell-extension-system-monitor-applet

ls -l ~/.local/share/gnome-shell/extensions/

If folder is listed in ~/.local/share/gnome-shell/extensions/, please remove it:

rm -rf ~/.local/share/gnome-shell/extensions/

If you don't mind resetting all the settings you made for this extension (alternative proposition below), could you also type:

dconf reset -f /org/gnome/shell/extensions/system-monitor/

Also verify that /usr/share/glib-2.0/schemas/gschemas.compiled has been freshly recompiled (date and time of the file must be nearly the one you installed the Fedora package of this extension) and that /usr/share/glib-2.0/schemas/ file is present.

As your terminal is still opened, please verify what type of session you are using (X11 or Wayland).


will give you the number of your user's session (most of the cases 2). The in the terminal type:

loginctl show-session <YOUR_NUMBER> -p Type

You should see one output indicating either Type=x11 or Type=wayland

Then close your session and re-open it (or safer and surely overkill: reboot) . Once the gnome session re-opened, try to activate the newly installed extension with Tweak Tool. Then post results.

Here is the alternative proposition, in case you don't want to loose the settings you applied to the existing extension from or if the previous tips didn't work. Just install the Fedora extension package, verify that /usr/share/glib-2.0/schemas/gschemas.compiled has been freshly recompiled and that /usr/share/glib-2.0/schemas/ file is present. Then, create a new user on your system. It will be used only for tests. Open a new session with the newly created user. Verify the session type (X11 or Wayland), and try to activate the newly installed Fedora extension with Tweak Tool (do not activate any other gnome-shell extension unless those activated by default). Then post results. It would be probably worth trying to open the gnome session with the two possible way (X11 or Wayland) and to try to activate this extension in each one.

Feel free to make any comment about this issue, and thank you very much for your patience.



@alexpl sorry but I can't reproduce your issue on my production laptop running Fedora 26. I wonder if you could provide more information about the process you followed to install this extension? It would be probably more accurate to open a bug report against this extension, in order to try to catch the issue you encountered (for example: Was the extension from completely removed? Was the file /usr/share/glib-2.0/schemas/gschemas.compiled regenerated just after you installed this Fedora 26 package? ). Please, feel free to make any comment about this issue.


-- NVieville