One file. Download and run.

=============================================================================== LinuxDoors System Status — for the LinuxDoors AppImage Store =============================================================================== Name: LinuxDoors System Status Price: $0.00 Maker: LinuxDoors.com Created: September 12, 2026 Kind: A LinuxDoors AppImage Software Product File: LinuxDoorsSystemStatus.AppImage Size: 417M (single file, download and run) SHA256: b2877dfc06a02e7f0b529cde0932d1c3cbf7ae8fe4067c21b5605335a05c1f56 CARD DESCRIPTION (the one line the store shows under the name) A professional, WCAG-checked system monitor — CPU, memory, disks, live network connections, and process control in one window. ------------------------------------------------------------------------------- DESCRIPTION ------------------------------------------------------------------------------- A system monitor built to look and feel like part of LinuxDoors itself, rather than a utility borrowed from somewhere else. It watches the machine the way the built-in tools of a well-finished desktop do: per-core CPU load, memory and swap, how full each mounted disk is, what the network is actually doing right now, and which processes are running — with the ability to act on any of that, not just look at it. A Summary tab shows every area at once, each with its own fold toggle so a section can be tucked away without losing it — folded sections keep updating underneath, so opening one again never shows a stale reading. Prefer more room for one thing at a time? Dedicated CPU, Memory, File Systems, Network, and Processes tabs each get the whole window, reading the same live data as the Summary view. Written for LinuxDoors, though nothing in it is specific to LinuxDoors — it runs on Debian and Ubuntu type systems, and on any other Linux distribution that can run an AppImage. ------------------------------------------------------------------------------- What is in the program ------------------------------------------------------------------------------- CPU Every core shown as its own live bar, sized to however many cores the machine actually has, plus an overall-usage line chart scrolling in real time. Numbers come straight from /proc/stat — the same source top itself reads — not a guess or an average smoothed past recognition. MEMORY RAM and swap, each as a bar with the real figures beside it (used and total), and a scrolling chart of RAM usage over time. Read from /proc/meminfo directly. FILE SYSTEMS A table of every real mounted filesystem — device, mount point, size, used, free, and percentage — read from /proc/mounts and statvfs(), with no guessing at what "real" means: pseudo-filesystems are left out. NETWORK A scrolling chart of upload and download throughput sits above a live connections table: protocol, local and remote address, state, and the process that owns each connection. The table comes from ss, the process list from ps — both well-tested tools already on any real Linux system, rather than a hand-rolled reimplementation of a kernel interface. PROCESSES A full, sortable process table — PID, user, CPU, memory, priority, command. Select a process to end it or change its scheduling priority; if the action needs a password, the program asks for one rather than failing silently. LIGHT AND DARK, MEASURED NOT GUESSED Opens in light mode by default, with a one-click switch to dark. Both themes are checked against the real WCAG 2.1 contrast-ratio formula before shipping — every text and background pairing in the interface, including chart labels and grid lines — rather than judged by eye. A self-test (--check-contrast) reports any failing pair; there are none. ZOOM A single +/- control scales the whole interface's base font size, so the window stays legible and proportional at a larger size rather than one panel growing while the rest stays put. ------------------------------------------------------------------------------- Verified across every LinuxDoors desktop ------------------------------------------------------------------------------- LinuxDoors offers a choice of desktop environments, each with its own window manager, and this program was checked under all seven rather than assumed to work everywhere because it worked somewhere: XFCE, MATE, GNOME, Cinnamon, KDE Plasma, LXQt, and Enlightenment. It launches cleanly and renders correctly under each. ------------------------------------------------------------------------------- Why 417M for a program this small ------------------------------------------------------------------------------- The program itself is one Python file of about 45 kilobytes. Everything else in the download is the machinery carried alongside it so the file runs on its own, on a machine that may have none of the following already installed, or a different version of any of them: - Its own copy of Python 3, complete with the standard library, since the AppImage cannot assume the host has Python installed at all. - Its own copy of the Qt 6 toolkit (the parts this program actually uses: the core, the windowing and widget libraries, and the charting library for the live graphs) plus PySide6, the layer that lets the Python code drive Qt. Qt's own graphics, font and text libraries come with it, since they are not optional parts of Qt — they are how it draws anything at all. - Its own copy of glibc, the C library and dynamic loader every one of the above is built on. This is what lets the same file run correctly whether the host is running an older or a newer C library than the one it was built against — the file does not have to match the host's version, because it never uses the host's copy. None of this is unused padding: it is the complete, working set of libraries the interface is drawn with, compressed as tightly as the format allows (zstd at its highest setting). A distribution's own package manager would install most of this once and share it between many programs; a single portable file cannot do that, so it brings its own copy of everything it needs instead. This is the same reason every other self-contained Qt-based AppImage in the LinuxDoors Store — GIMP, OpenShot, LinuxUltraOffice — lands in a broadly similar size range: the floor is set by the toolkit each one carries, not by how much of that program's own code there is. ------------------------------------------------------------------------------- What it does not do, plainly ------------------------------------------------------------------------------- It is better to know the edges of a program before downloading it. - No historical logging. Charts scroll a recent live window; nothing is written to disk for later review. - No remote monitoring. It watches the machine it runs on, not another one over the network. - No alerting or thresholds. It shows what is happening; deciding whether a number is a problem is left to you. ------------------------------------------------------------------------------- LinuxDoors original ------------------------------------------------------------------------------- Built by LinuxDoors.com — this is our own application, not a mirror and not a repackaging of somebody else's build. The SHA-256 above is authoritative. It carries its own Python 3, its own Qt 6, and its own glibc, so it does not depend on the host's Python or Qt version, or its C library. Nothing is installed on the machine and nothing on the machine is disturbed. ------------------------------------------------------------------------------- Running it — nothing to install ------------------------------------------------------------------------------- chmod +x LinuxDoorsSystemStatus.AppImage ./LinuxDoorsSystemStatus.AppImage On LinuxDoors, which has no FUSE, run it the way LinuxDoors runs any AppImage: ./LinuxDoorsSystemStatus.AppImage --appimage-extract-and-run or through linuxdoors-run-appimage, which does that for you and unpacks it once rather than on every launch. The first launch is slower while it extracts; later launches from the same extracted copy are fast.

=============================================================================== LinuxUltraGrep — for the LinuxDoors AppImage Store =============================================================================== Name: LinuxUltraGrep Price: $0.00 Author: Stan Switaj Provider: GoodsAppStore.com Created: September 17, 2026 Updated: September 18, 2026 Kind: A LinuxDoors AppImage Software Product File: LinuxUltraGrep.AppImage Size: 38M (single file, download and run) SHA256: 475f56f6e6051a75fb36875fe8d813319379c47d5564e49ea2e63ed1aa13a7f4 Bug reports: bug-reports-linuxultragrep@linuxdoors.com CHANGED, 3 OCTOBER 2026 -- FIXED: DID NOT START ON SOME REAL DESKTOPS On Linux Mint 22.3 and some Ubuntu-family desktops, this AppImage failed to open at all, printing "qt.qpa.plugin: ... xcb-cursor0 or libxcb-cursor0 is needed" and exiting. The AppImage bundles its own Qt, but was missing one small library (libxcb-cursor, plus its own two helper libraries) that Qt's screen code needs -- present on Debian and LinuxDoors by other means, but not installed by default on Mint or Ubuntu. That library is now bundled inside the AppImage itself, so it no longer depends on the host having it. CARD DESCRIPTION (the one line the store shows under the name) Search inside files, and search for files, with the speed of grep. ------------------------------------------------------------------------------- DESCRIPTION ------------------------------------------------------------------------------- A search program. Type what you are looking for, say where to look, press Find. It looks inside files the way grep does, and it looks for files by name the way find does, and it can replace what it finds across a thousand files after showing you exactly what it intends to change. It does what grepWin does on Windows, which is the program people miss most when they come to Linux and discover that the searching is all on the command line. Everything grepWin offers is here — text or regular expression, match case, whole words, inverse search, searching again inside what was found, file name patterns, folders to skip, size and date limits, hidden and binary files, symbolic links, replace with backups, saved searches, a regular expression tester and an export. Two searches, two tabs. Contents looks inside files. File names looks at the names themselves. They are separate because they are separate questions, and mixing them means half your results are always the kind you did not ask for. They share the filters underneath, so switching tabs does not mean setting it all up again. Everything it needs travels with it. There is no Python to install first and no Qt to match, and nothing on the machine for it to disagree with — which is the point of shipping it as one file. Written for LinuxDoors, though nothing in it is specific to LinuxDoors — it runs on Debian and Ubuntu type systems, and on any other Linux distribution that can run an AppImage. ------------------------------------------------------------------------------- What does the searching, and why ------------------------------------------------------------------------------- Whichever is quickest, and the answer is not always the same program. Measured over /usr/include — 4,692 files — best of three runs, warm caches: GNU grep across 10 processes 0.029s GNU grep -r 0.081s python, 10 processes 0.168s python, one thread 0.406s python, 10 threads 0.628s Two things in that table decided how the program is built. The first is that threads make Python searching *slower* — slower than not using them at all. Python's regular expression engine holds the interpreter lock while it works, so ten threads take turns rather than run together. The pool here is a process pool and never a thread pool. The second is that the two engines did not agree on the answer. grep counted 32,580 where Python counted 36,770, because `grep -c` counts *lines that match* while Python was counting *matches* — a line with three hits is one line and three matches. A search that reports a different number depending on which program happened to run is worse than a slow one. So the fast program is never asked for a count. It is asked only *which lines match*, which is the part it is extraordinarily good at, and the exact matches within those few lines are worked out afterwards, in one place, in one way. The status bar names the engine that ran, and `--check` runs every engine over the same folder and fails if any of them disagree by so much as one. On a machine with no grep at all there is still the built-in engine, and it is not a toy: it maps large files rather than reading them, stops at the first null byte that says a file is not text, and runs across every core but two. Nothing here *requires* an external program. ------------------------------------------------------------------------------- Looking inside files ------------------------------------------------------------------------------- Text or regular expression Python's own, which is very close to what grepWin gives through boost Match case exactly as typed Whole words needle, not needless Inverse search the files with no match at all Search within the results narrow a search rather than start over Dot matches newline for patterns that span lines The results are a file, then every line in it that matched, with the matched part picked out and the line number beside it. Double-click and the file opens in your editor at that line — and at the column the match starts on, not merely the top of the file. ------------------------------------------------------------------------------- Looking for files ------------------------------------------------------------------------------- A pattern matches the file name. Put a slash in it — test/fixtures — and it matches the path instead. Wildcards * ? [ ] work, or tick Regular expression for the full thing. The folder you are searching in is never part of what is matched. It is part of every result, so if its name happened to contain what you typed, everything would match — and turning on Match case would appear to fix it while fixing nothing. Include folders, in the filters, matches the folders themselves and not only what is inside them. It is a question you can only ask of names — there is no such thing as grepping a directory — so it greys out on the Contents tab rather than disappearing, which would leave you hunting for where it went. Three of the file filters deliberately do not apply to folders. Name matches would wipe out every folder the moment it said *.py, which is what it says nearly always; size and age are about files. All three would read as the option being broken rather than as a filter doing its job. What does apply is what is about folders: hidden ones, skipped ones, and whether subfolders are being walked at all. A folder in the results has an arrow. Open it and it lists what is in it, folders first, and those open too, so a match can be walked down into rather than only glanced at. What is inside is read when you open it and not when you search: a name search can match thousands of folders, and reading every one of them to fill rows nobody has scrolled to would turn a search of a disk into that search plus thousands of directory reads. Expand all reads the first two hundred and says so; the rest read themselves as they are opened. ------------------------------------------------------------------------------- Which files get looked at ------------------------------------------------------------------------------- Name matches *.py, *.txt — or a regular expression Skip folders .git, node_modules and the rest, and editable Include subfolders or just the one Include hidden files off by default Include binary files off by default; a null byte in the first few kilobytes is what says a file is not text Follow symbolic links off by default, and a loop of links will not hang it Size smaller or bigger than a figure you set Changed before or after a date The panel comes back the way you left it, open or closed, with every box in it as it was. A filter that quietly resets itself overnight is a fine way to wonder why the same search now finds something else. ------------------------------------------------------------------------------- Replacing ------------------------------------------------------------------------------- Replace shows you what it will do before it does it: every match, the line as it stands and the line as it would become, with a tick beside each one. Untick what you would rather keep. Nothing is written until you press the button, and what is written is only what is still ticked. Backups are on by default, beside the file or in a folder of your choosing. File dates can be kept, because changing a thousand modification times is a rotten way to find out you meant a different folder. \1 and \2 put the groups from the search into the replacement. ------------------------------------------------------------------------------- The command line ------------------------------------------------------------------------------- The same search, without the window. The short flags are grep's, because anybody reaching for this already knows them. LinuxUltraGrep.AppImage -r 'def .*self' ~/code LinuxUltraGrep.AppImage -rl --include '*.py' TODO ~/code LinuxUltraGrep.AppImage --files '*.conf' /etc LinuxUltraGrep.AppImage --files test --folders ~/code LinuxUltraGrep.AppImage -r --replace new old ~/code --dry-run LinuxUltraGrep.AppImage --column -o -E '\bclass \w+' ~/code -i -s -w -v -F -E case, whole words, inverse, fixed, regex -l -c -h -q -o names only, counts, no file name, quiet, just the matched part -r --no-recursive into subfolders, or not --include --exclude-dir which files, which folders to skip --hidden --binary --follow --column file:line:column:text --files search names rather than contents --folders match folder names too; they print with a trailing slash, the way ls -F writes them --replace --dry-run change things, or see what would change --open --open-with open every match in an editor --engine auto, grep or python --check --bench prove the engines agree; time them With no pattern and no --files, the window opens. ------------------------------------------------------------------------------- The rest of it ------------------------------------------------------------------------------- A regular expression tester. Try a pattern against text you type, see every match and what each group caught, before turning it loose on ten thousand files. Saved searches. Keep a search you use often and load it back in one click, with its pattern, its folder and its filters. A results toolbar. Expand all, Minimize all, Search within, Export and Clear results, with a box that narrows the list you already have without searching again. Export. The results to a text file or a CSV, file and line and text. How results open. It uses whichever editor it finds — LinuxNoteText first — and opens at the line and column of the match. If you would rather it ran something else, say so once: a command of your own with {file}, {line}, {column}, {dir} and {name} in it, quoted as a shell would, so a path with a space in it stays one argument. Text size. Tools, Text size — a slider rather than a pair of buttons, because the question is "how big", not "one step bigger": with buttons you find the size you want by pressing until it looks right, and with a slider you put it where you want it. It applies as it slides, and it reaches the results already on screen rather than only the next ones. Light and dark. Every colour pair that sits on top of another is measured against the WCAG contrast standard rather than judged by eye, in both themes, and the program will tell you so itself — Tools, Check the colours. ------------------------------------------------------------------------------- Built by LinuxDoors — this is our own application, not a mirror and not a repackaging of somebody else's build. The SHA-256 above is authoritative. It carries its own Python and its own Qt, so the window and the search work on a computer with nothing installed on it. The filters, the two engines, the replacing and the matching are all the program's own code. GNU grep is used when it is on the machine and is faster, and never trusted to do the counting. ------------------------------------------------------------------------------- Running it — nothing to install ------------------------------------------------------------------------------- chmod +x LinuxUltraGrep.AppImage ./LinuxUltraGrep.AppImage Or give it a folder to start in: ./LinuxUltraGrep.AppImage ~/code On LinuxDoors, which has no FUSE, run it the way LinuxDoors runs any AppImage: ./LinuxUltraGrep.AppImage --appimage-extract-and-run or through linuxdoors-run-appimage, which does that for you and unpacks it once rather than on every launch. Settings live in ~/.linuxultragrep.save, written mode 0600 when the program closes. Nothing secret goes in it — there is nothing secret to put — but it holds where you have been looking and what you have been looking for, which is nobody else's business. Deleting that file puts everything back as it started.