Honest system load and hardware health in the top bar. • CPU load over physical cores: SMT sibling threads merged, so 12 busy cores on a 24-thread CPU read 100%, not 50%. • Pressure (PSI) for CPU, memory and I/O: whether a resource is actually slowing work down. • Memory without page cache, zram and swap on disk shown apart; filesystems and disk I/O; AMD GPU load and VRAM. • Every hwmon sensor: temperatures, fans with PWM duty, voltages, power. • Alerts: stalled or stopped fans, hot sensors, nearly full disks, memory spilling to disk, thrashing. • Keeps watching while the screen is locked, so a fan that stops while you are away still raises its alarm. • Fans never seen spinning are treated as not connected; rename, hide and set limits per sensor. Reads only /proc and /sys. No network, no helper processes.
Note: Binary files aren't shown on the web site. To see all files, please download the extension zipfile.
EGO-M-008 warning
extensions using unlock-dialog must document it in disable() comments
Extensions using `unlock-dialog` should document the reason in `disable()` comments.
extension.js:157
disable() {
if (this._timerId) {
GLib.source_remove(this._timerId);
this._timerId = 0;
}
Main.sessionMode.disconnect(this._sessionModeId);
this._settings.disconnect(this._settingsChangedId);
this._indicator.destroy();
this._
| Version | Status |
|---|---|
| 0.1.0 (1) | Unreviewed |
Core Sentinel uses the unlock-dialog session mode so that hardware alarms keep working while the screen is locked: a fan that stalls or a part that overheats while the user is away still raises a notification, and an alert that is still active is not announced again at every unlock. The panel button is hidden while the screen is locked (_syncLocked in extension.js), and disable() carries a comment explaining this. The only synchronous calls are readlink() on sysfs symlinks (lib/io.js), which the kernel answers from memory without touching a device. All /proc and /sys reads are asynchronous (Gio). No network access and no subprocesses.