https://intergenos.org/news.html Releases, fixes and package news for InterGenOS, newest first. en Copyright 2026 InterGenOS Mon, 24 Aug 2026 14:15:33 -0500 https://intergenos.org/favicon.png https://intergenos.org/news.html https://intergenos.org/news.html#r001-1-known-issues https://intergenos.org/news.html#r001-1-known-issues Mon, 24 Aug 2026 14:15:33 -0500 Update Five issues in the R001.1 release are confirmed and being worked; fixes are landing in the next point release. (1) Privileged actions through the assistant do not work in R001.1 — the message "runner not found / package may be misinstalled" is incorrect; do not reinstall packages over it. (2) Wiki-grounded answering currently runs on keyword matching. (3) On machines with more than one local account, the assistant's activity log (~/.local/state/intergen/intergen.log, which records web-search queries) is readable by other local accounts on a standard install; the personal-facts database and transcripts are created with loose permissions too, but on a standard install they sit behind a private ~/.local/share folder and are not reachable by other accounts — run: chmod 700 ~/.local/state/intergen ~/.local/share/intergen. (4) Some discrete GPUs (3–7 GB VRAM) are not yet used for inference; replies are slower than intended on that hardware. (5) Web-search requests are phrasing-sensitive; "search the web for …" is the reliable form until R001.2. https://intergenos.org/news.html#pkm-upgrade-rollback https://intergenos.org/news.html#pkm-upgrade-rollback Fri, 21 Aug 2026 10:34:05 -0500 Update Every pkm upgrade printed a warning for each package — "no cached archive … rollback unavailable if the install fails" — and the warning was wrong on both ends. The rollback copy it reported on was never actually being kept: the lookup used a filename shape the download cache never contains, so it missed every time, on every system. And the protection that does exist went unmentioned — the Chronicle backup engine captures a restore point before every package transaction, covering the files about to change and the package database. pkm 0.2.0-62 fixes the lookup, so a rollback copy of each outgoing version is kept whenever the cache holds its archive, and replaces the per-package warning with a single line stating the protection actually in force: a captured restore point, kept rollback copies, or — normal for the first upgrade after a fresh installation — neither. Installed systems pick the fix up from the signed package mirror — run: sudo pkm upgrade. One note: the upgrade that installs this fix still prints the old warnings a final time, since it runs the previous version's code; the first upgrade after it shows the new line. https://intergenos.org/news.html#camera-virtman-fixes https://intergenos.org/news.html#camera-virtman-fixes Fri, 21 Aug 2026 08:44:44 -0500 Update Two applications that failed at launch have been fixed and republished. The camera application's live preview required a GStreamer element that was not packaged — it now works end to end, verified on real hardware with a real camera. The virtual machine manager stopped opening after recent glib releases removed a compatibility alias its startup path still used — a startup patch restores it. Both were found by launch-testing every graphical application in the shipped set. A new package, gst-plugin-gtk4 1.28.1, ships the missing element, version-matched to the GStreamer stack, and the camera application now declares it as a dependency so the pair installs together. Installed systems pick everything up from the signed package mirror — run: sudo pkm upgrade. As with every package, the mirror's signed index covers the updates: they verify before they install. https://intergenos.org/news.html#wiki-release-invariant https://intergenos.org/news.html#wiki-release-invariant Fri, 21 Aug 2026 05:22:05 -0500 Update The InterGenOS wiki has been updated so its pages no longer name a specific "current release." Pages now describe the system as it ships and point to the repository README and the mirror's image directory for the live answer — so the documentation cannot drift out of date when a new release publishes. The change covers both the wiki served at wiki.intergenos.org and the copy installed on every system. Installed systems pick the update up from the signed package mirror as intergenos-wiki 1.0.0-13 — run: sudo pkm upgrade. As with every package, the mirror's signed index covers it: the update verifies before it installs. https://intergenos.org/news.html#r001-1-released https://intergenos.org/news.html#r001-1-released Thu, 20 Aug 2026 14:39:16 -0500 Point release The first point release of InterGenOS is available. R001.1 is an updated x86_64 UEFI live ISO built against R001's proven substrate, and it replaces R001 as the recommended download: boot it to try the system, or run FORGE from it to install a full desktop, with an encrypted disk, a signed boot chain and the local InterGen assistant included. This release addresses several small fixes, and delivers our first post-release package additions set. Some land on the image itself — log rotation on every install, USB and NVMe tooling, ethernet diagnostics, and hybrid-graphics switching — and the rest are ready to install from the signed package mirror: the full VPN client set, container tooling, and a network-diagnostics suite. One note regarding a cosmetic fix we'll finalize with our next point release — every Secure-Boot install prints a "...prohibited by secure boot policy" error at the boot menu (a flash on single-monitor machines, persistent on the second screen of multi-head machines); harmless to boot integrity — it's just Secure Boot doing its job against a GRUB font file the image should have carried built-in. See the CHANGELOG for the complete list of changes included in this release. Check the image before you boot it. The published sha256 is 31b6e0a38ff74170a927413037e8b03b441e7178385d12ed8074c5041e0cd527, published beside the ISO as a file you can pass straight to sha256sum -c, and that checksum file carries a detached signature from the release key at intergenos-r001.1.iso.sha256.asc. The package mirror's index is signed with the same key, whose primary fingerprint is 5597 A3E0 587B 2530 06D0 DD7B 8C50 8261 8208 3050. None of these checks depends on trusting the announcement. Download: https://repo.intergenos.org/iso/intergenos-r001.1.iso Checksum file: https://repo.intergenos.org/iso/intergenos-r001.1.iso.sha256 Its signature: https://repo.intergenos.org/iso/intergenos-r001.1.iso.sha256.asc Release key: https://repo.intergenos.org/keys/intergenos-release-key.asc Install guide: https://wiki.intergenos.org/install/forge-guide.html Full CHANGELOG: https://github.com/InterGenJLU/intergenos/blob/master/CHANGELOG.md https://intergenos.org/news.html#first-package-wave https://intergenos.org/news.html#first-package-wave Thu, 20 Aug 2026 14:39:16 -0500 Packages R001.1 delivers the first post-release additions to the package set. Five land on the image itself: log rotation on every install, USB and NVMe tooling, ethernet diagnostics, and hybrid-graphics switching for dual-GPU laptops. The rest are ready to install from the signed package mirror: the full VPN client set (OpenVPN, OpenConnect, and WireGuard tooling with NetworkManager integration), container tooling (compose, buildx, buildah, skopeo), and a network-diagnostics suite (mtr, tcpdump, iperf3, nmap, socat, and a meta-package that pulls the set in one install). Everything installs through pkm and verifies against the signed index like every other package. https://intergenos.org/news.html#r001-released https://intergenos.org/news.html#r001-released Sun, 16 Aug 2026 19:45:45 -0500 Release The first public release of InterGenOS is available. R001 is an x86_64 UEFI live ISO: boot it to try the system, or run FORGE from it to install a full desktop, with an encrypted disk, a signed boot chain and the local InterGen assistant included. Check the image before you boot it. The published sha256 is 1beeb90539bc1031ad135148f379e97a1830b835350f9c7924fd7b9fc3db07c7, published beside the ISO as a file you can pass straight to sha256sum -c, and that checksum file carries a detached signature from the release key at intergenos-r001.iso.sha256.asc. The package mirror's index is signed with the same key, whose primary fingerprint is 5597 A3E0 587B 2530 06D0 DD7B 8C50 8261 8208 3050. None of these checks depends on trusting the announcement. Download: https://repo.intergenos.org/iso/intergenos-r001.iso Checksum file: https://repo.intergenos.org/iso/intergenos-r001.iso.sha256 Its signature: https://repo.intergenos.org/iso/intergenos-r001.iso.sha256.asc Release key: https://repo.intergenos.org/keys/intergenos-release-key.asc Install guide: https://wiki.intergenos.org/install/forge-guide.html