Display system information in gnome shell status bar, such as memory usage, CPU usage, and network rate...

How to install

sudo dnf install --refresh --advisory=FEDORA-2017-5c8e0c725d \*

This update has been submitted for testing by nvieville.

4 years ago

This update has been pushed to testing.

4 years ago
User Icon alexpl commented & provided feedback 4 years ago
karma

As soon as I enabled the extension in Tweak Tool, gnome-shell crashed and I was thrown to gdm, but I could not log in to GNOME any more. I rebooted, just in case there was a conflict somewhere, still unable to login. Eventually I switched to a VT and removed it, problem solved.

I got these messages:

Oct 14 19:37:57 gnome-shell[15464]: System monitor applet init from /usr/share/gnome-shell/extensions/system-monitor@paradoxxx.zero.gmail.com
Oct 14 19:37:57 gnome-shell[15464]: Settings schema 'org.gnome.shell.extensions.system-monitor' does not contain a key named 'compact-display'
Oct 14 19:37:57 kernel: traps: gnome-shell[15464] trap int3 ip:7fc1faed0e51 sp:7ffdc147a420 error:0 in libglib-2.0.so.0.5200.3[7fc1fae81000+110000]
Oct 14 19:37:57 audit[15464]: ANOM_ABEND auid=1000 uid=1000 gid=1000 ses=8 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 pid=15464 comm="gnome-shell" exe="/usr/bin/gnome-shell" sig=5 res=1
Oct 14 19:37:58 gnome-session[14507]: gnome-session-binary[14507]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 5
Oct 14 19:37:58 gnome-session[14507]: gnome-session-binary[14507]: WARNING: App 'org.gnome.Shell.desktop' respawning too quickly
Oct 14 19:37:58 gnome-session-binary[14507]: Unrecoverable failure in required component org.gnome.Shell.desktop
Oct 14 19:37:58 gnome-session-binary[14507]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 5
Oct 14 19:37:58 gnome-session-binary[14507]: WARNING: App 'org.gnome.Shell.desktop' respawning too quickly
Oct 14 19:37:58 gnome-session[14507]: Unable to init server: Could not connect: Connection refused
Oct 14 19:37:58 gnome-session-f[15723]: Cannot open display: 
Oct 14 19:37:59 gnome-session[14507]: gnome-session-binary[14507]: WARNING: Client '/org/gnome/SessionManager/Client27' failed to reply before timeout
Oct 14 19:37:59 gnome-session[14507]: gnome-session-binary[14507]: WARNING: Client '/org/gnome/SessionManager/Client28' failed to reply before timeout
Oct 14 19:37:59 gnome-session-binary[14507]: WARNING: Client '/org/gnome/SessionManager/Client27' failed to reply before timeout
Oct 14 19:37:59 gnome-session-binary[14507]: WARNING: Client '/org/gnome/SessionManager/Client28' failed to reply before timeout

I reinstalled from extensions.gnome.org and it's running fine. Does that missing schema key ring any bells?

Bodhi is disabling automatic push to stable due to negative karma. The maintainer may push manually if they determine that the issue is not severe.

4 years ago

Hello,

@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 gnome.org 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.

Cordially,

-- NVieville

Hello Nicolas,

I'll try to repeat the process some time tomorrow and see if I can reproduce the error. The extension was originally installed from extensions.gnome.org. As far as I can tell, when I removed it prior to installing the packaged version, its folder disappeared from ~/.local/share/gnome-shell/extensions/, so I'm guessing there wasn't something left behind.

I didn't think to check gschemas.compiled, I will keep that in mind.

On github, the maintainers state that libgtop2-devel and NetworkManager-glib-devel are required, but in your spec file I see only gettext and glib2 as build dependencies. Is the documentation obsolete?

I will open a new bug in rhbz if I find anything useful.

Best regards,

Alexander

Hello again,

I gave it another go today, while paying attention to what was happening on the system. I can not open a bug report, as bugzilla does not list gnome-shell-extension-system-monitor-applet among the components.

I had the extension installed from extensions.gnome.org and I uninstalled it using the website. I verified that the extension had disappeared from ~/.local/share/gnome-shell/extensions/, but my settings remained (I checked via dconf-editor).

I installed the packaged version of the extension with dnf and checked if /usr/share/glib-2.0/schemas/gschemas.compiled got regenerated - it did.

I started Tweak Tool to enable the extension, but as soon as that happened, packagekitd crashed and dumped core. I closed Tweak Tool, restarted gnome-shell, reopened Tweak Tool and enabled the extension. At that moment, gnome-shell crashed and I was back at gdm. Every attempt to login failed with a gnome-shell crash, until I removed the extension from a VT with dnf.

I have uploaded a sanitized system log starting right before I removed the extension from extensions.gnome.org, up to the point I had removed the packaged version and logged back in.

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 extensions.gnome.org 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 system-monitor@paradoxxx.zero.gmail.com is listed in ~/.local/share/gnome-shell/extensions/, please remove it:

rm -rf ~/.local/share/gnome-shell/extensions/system-monitor@paradoxxx.zero.gmail.com

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/org.gnome.shell.extensions.system-monitor.gschema.xml file is present.

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

loginctl

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 extensions.gnome.org 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/org.gnome.shell.extensions.system-monitor.gschema.xml 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.

Cordially,

Hi Nicolas,

I guess I should have added those details before you asked, but anyway, I'll do it now.

I am running gnome-shell-3.24.3-2.fc26.x86_64 on X, as I am using nVidia's driver, so I can't run Wayland. I also have gnome-shell-extension-common-3.24.3-1.fc26.noarch. There is only one version of your package for F26 and that would be gnome-shell-extension-system-monitor-applet-0-0.1.20171005git61b0a60.fc26.noarch.

Like I wrote earlier, when I removed the extension from extensions.gnome.org, I checked that ~/.local/share/gnome-shell/extensions/system-monitor@paradoxxx.zero.gmail.com was indeed removed and it was.

These are my other extensions:

invert-window@maiself
openweather-extension@jenslody.de
places-menu@gnome-shell-extensions.gcampax.github.com
screenshot-window-sizer@gnome-shell-extensions.gcampax.github.com
TopIcons@phocean.net

The only thing I hadn't tried was resetting the dconf settings, which I just did.

So to recap what I did in my latest attempt:

  • I went over to extensions.gnome.org, disabled and then removed the extension, while making sure that its directory under ~/.local/share/gnome-shell/extensions/ was also removed.

  • I reset the dconf settings (I backed them up first).

  • I went on to install gnome-shell-extension-system-monitor-applet (with dnf --enablerepo=*testing install etc.) and verified that gschemas.compiled was regenerated and also that the schema XML file was there too.

  • For good measure, I rebooted the system.

  • I logged into GNOME.

  • I fired up Tweak Tool and enabled the extension.

  • gnome-shell crashed, I'm back at gdm. Every subsequent attempt to login results in gnome-shell crashing.

I was almost certain that it would work this timeā€¦

I looked into the error messages (fresh log) and it seems that when I am using the packaged version of the extension, something is triggering #1402492. Since you have packaged a more recent snapshot of the extension than what's currently on extensions.gnome.org, I expect that when the latter gets the newer code, I will face the same error, unless something is different between the packaged version and the other one.

Unless you have another idea, I'd suggest you ignore my -1 karma and push it to stable when you can. If I encounter the same issue when my version gets updated I will file a bug upstream.

Best regards,

Alex

This update has reached 7 days in testing and can be pushed to stable now if the maintainer wishes

4 years ago

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,

Nicolas

Hello Nicolas,

Added a user, switched to a VT, installed the extension, rebooted, logged in to GNOME on X and as soon as I enabled the extension (the only one), gnome-shell crashed.

I decided to let abrt file a report and it turns out I was right about this being #1402492, because my report was added to that bug.

Sorry for taking up so much of your time and thanks for trying to help.

Best regards, Alex

Hello Alex,

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

Best regards,

Nicolas

This update has been submitted for batched by nvieville.

4 years ago

This update has been submitted for stable by nvieville.

4 years ago

This update has been pushed to stable.

4 years ago

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:

echo $XDG_DATA_DIRS

If in the directories listed you find a glib-2.0/schemas sub-directory, verify that only one of them contains a org.gnome.shell.extensions.system-monitor.gschema.xml 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/system-monitor@paradoxxx.zero.gmail.com (the one that was installed with the extension from extensions.gnome.org) to a temporary folder. Then proceed as usual (uninstall the extension from extensions.gnome.org and install the one from fedora repository). Before closing your session, overwrite the file /usr/share/gnome-shell/extensions/system-monitor@paradoxxx.zero.gmail.com/metadata.json 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,

Nicolas

User Icon alexpl commented & provided feedback 4 years ago
karma

Hello Nicholas,

You were spot on.

Among the directories held by XDG_DATA_DIRS was /usr/local/share/, which did contain glib-2.0/schemas/ and in that directory I found gschemas.compiled and org.gnome.shell.extensions.system-monitor.gschema.xml dating back to 17 Jan 2012. As it turns out, instructions at the time required to add the file there: https://github.com/paradoxxxzero/gnome-shell-system-monitor-applet/blob/0dce659308ea46a1ec9fccda0c47ab20a319f262/README.md

That was the reason for the "Settings schema 'org.gnome.shell.extensions.system-monitor' does not contain a key named 'compact-display'" message, the key wasn't there at the time.

I renamed the /usr/local/share/glib-2.0/ folder, disabled and removed my local extension and went on to install yours. After restarting the shell (no need to log out) and enabling the extension via Tweak Tool, everything was working fine.

Thank you so much for your perseverance!

Best regards,

Alex


Please login to add feedback.

Metadata
Type
newpackage
Karma
1
Signed
Content Type
RPM
Test Gating
Settings
Unstable by Karma
-3
Stable by Karma
disabled
Stable by Time
disabled
Dates
submitted
4 years ago
in testing
4 years ago
in stable
4 years ago

Automated Test Results