Display system information in GNOME Shell status bar, such as memory, CPU, disk and battery usages, network rates… If you get an error after updating, try logging out and logging back in (this is a known issue that is being worked on).
Note: Binary files aren't shown on the web site. To see all files, please download the extension zipfile.
| Version | Status |
|---|---|
| 75 | Active |
| 74 | Rejected |
| 73 | Active |
| 72 | Rejected |
| 71 | Active |
| 70 | Active |
| 69 | Active |
| 68 | Active |
| 67 | Inactive |
| 66 | Active |
| 65 | Active |
| 64 | Active |
| 63 | Active |
| 62 | Active |
| 61 | Active |
| 60 | Active |
| 59 | Rejected |
| 58 | Active |
| 57 | Rejected |
| 56 | Rejected |
| 55 | Active |
| 54 | Rejected |
| 53 | Rejected |
| 52 | Rejected |
| 51 | Rejected |
| 50 | Rejected |
| 49 | Rejected |
| 48 | Rejected |
| 47 | Rejected |
| 46 | Rejected |
| 45 | Rejected |
| 44 | Rejected |
| 43 | Active |
| 42 | Active |
| 41 | Active |
| 40 | Active |
| 39 | Active |
| 38 | Active |
| 37 | Active |
| 36 | Active |
| 35 | Active |
| 34 | Active |
| 33 | Active |
| 32 | Active |
| 31 | Active |
| 30 | Active |
| 29 | Active |
| 28 | Active |
| 27 | Active |
| 26 | Active |
| 25 | Active |
| 24 | Rejected |
| 23 | Rejected |
| 22 | Active |
| 21 | Active |
| 20 | Rejected |
| 19 | Rejected |
| 18 | Rejected |
| 17 | Rejected |
| 16 | Rejected |
| 15 | Rejected |
| 14 | Rejected |
| 13 | Rejected |
| 12 | Rejected |
| 11 | Rejected |
| 10 | Rejected |
| 9 | Rejected |
| 8 | Rejected |
| 7 | Rejected |
| 6 | Rejected |
| 5 | Rejected |
| 4 | Active |
| 3 | Active |
| 2 | Active |
| 1 | Active |
(Copying over my comment from version 74 for ease of reference) Ok, I've fixed the XML filenames as per the EGO Review Guidelines. The reason we have two schema definition files is because we're migrating the schema ID to something more unique for this extension. The current schema ID clashes with an official Gnome extension as well as the upstream version of this extension (this is a fork). There's bit more background on this migration process here [1], but the summary is that we want to rename the schema ID without existing users losing their settings, so we're shipping both schemas, and during extension startup we copy settings from the old schema to the new one. After a few months or so we'll remove the old one. [1] https://discourse.gnome.org/t/settings-migration-after-a-schema-rename/25047
system-monitor-next