Packages

LinuxDoors System Status -- a PySide6 system monitor (CPU per-core, memory/swap, file systems, network throughput + a real live connection table, and process control) built in this project's own PySide6/QSS house style, reusing FlashScp's already WCAG-verified light/dark palette architecture (DARK_PALETTE/LIGHT_PALETTE dicts, the same WCAG 2.1 relative-luminance contrast-ratio formula, a --check-contrast self-test flag) rather than deriving a new one. Programmer-authored asset treated as a source tarball, same pattern as packages/sudo, packages/flashscp, and packages/linuxdoors-powertoys. Features: a +/- zoom that scales the whole window's base font size (not per-panel); each section (CPU/Memory/File Systems/Network/Processes) has its own (+)/(-) fold toggle in its header, and keeps updating on the timer underneath whether folded or not, so re-opening one never shows a stale reading; full process control (End Process via SIGTERM, Change Priority via os.setpriority), retrying as root through the same su -c + password-dialog pattern every other LinuxDoors admin tool uses if the plain attempt is refused; a real network connections table (proto/local/remote/state/owning process) via `ss -tulpn`, not just an aggregate throughput graph -- chosen over hand-parsing /proc/net/tcp's hex address format + inode-to-pid mapping, the same 'use a well-tested existing tool' reasoning already applied choosing wmctrl over a hand-rolled X11 client for LinuxDoors PowerToys. Real bugs found and fixed before shipping, each confirmed against an actual screenshot or a real failure, not guessed: (1) `ps`'s nice-value column reports a literal '-' instead of a number for kernel threads and real-time-scheduled processes -- a bare `int(nice)` crashed the whole app on first launch; fixed to fall back to None/'-' display. (2) A genuine QtCharts axis-label bug, found and fixed in three real steps: the Y-axis showed '...' instead of real percentage/throughput numbers on every chart. First suspected (and fixed as a real but insufficient issue) a printf-format escaping bug -- y_label='%' fed into '%d'+y_label produces the invalid trailing-bare-percent format '%d%', which needs '%d%%' to safely emit a literal percent sign. That fix alone didn't resolve it; isolated the real cause by reproducing the identical axis configuration in a bare, minimally-nested test window, where it rendered correctly, proving the bug was about layout/sizing, not the axis setup itself. Root cause: the chart's only height constraint was setMinimumHeight(110), with the default width policy left unconstrained inside a several-levels-deep Section/QVBoxLayout/QScrollArea hierarchy -- with 5 axis tick labels needing real vertical room and no explicit sizePolicy telling Qt to actually claim horizontal space during the scroll area's first layout pass, QtCharts computed its label elision against that undersized initial layout and never revisited it. Fixed with an explicit QSizePolicy.Expanding/Fixed policy and a taller 180px minimum height -- confirmed via a real screenshot showing genuine '0%/25%/50%/75%/100%' labels afterward. (3) A `wmctrl -r NAME` test call (used only during this app's own screenshot-verification tooling, to maximize the test window) silently failed for the same reason already documented for LinuxDoors PowerToys: name-based window lookup shares wmctrl's broken window-listing code path under this exact Xvfb test harness; switched to the already-proven-working `wmctrl -r :ACTIVE:` (reads _NET_ACTIVE_WINDOW directly, a separate code path) instead. Cross-desktop-environment tested for real: launched cleanly (no crash, confirmed via captured stdout/stderr, not just process exit code) under all seven LinuxDoors-supported window managers -- xfwm4 (XFCE), marco (MATE), mutter --x11 (GNOME/Budgie), muffin --x11 (Cinnamon), kwin_x11 (KDE Plasma), openbox (LXQt), and enlightenment_start. Unlike LinuxDoors PowerToys, this app has no window-manager-specific feature (no EWMH tricks of its