Synex Updates for Mid August 2026
Synex Updates for Mid August 2026
Table of Contents
Mid-August 2026 has turned out to be a genuinely busy little window for Synex, the Argentine, Debian-based distribution that's been quietly building a loyal following among people who like their Linux minimal, sensible and just a bit polished. Within the space of a single day, the project pushed out a refreshed Semi-rolling release, introduced a brand-new snapshot management tool for Btrfs users, fixed a long-standing installer headache for older BIOS machines, and switched on a download mirror hosted on its own infrastructure. That's a lot of ground to cover, so let's get into it properly.
Semi-Rolling Refresh: COSMIC 1.5.0, Btrfs Snapshots and a Boot Fix
Synex Semi-rolling is the project's faster-moving branch, built on top of Debian Testing rather than Debian Stable, and it's traditionally where the team lets new ideas breathe before they're considered mature enough for the main Synex 13 line. The 26.08.17 build carries three headline changes, and each one deserves a proper look.
The most visible update is the jump to COSMIC 1.5.0, the latest release of System76's Rust-based desktop environment. This isn't a token version bump either; the refresh touches the entire stack, from the Wayland compositor itself through to the panel and its applets, the settings centre, the session manager, and the bundle of first-party applications that ship alongside the desktop.
As with every COSMIC release Synex has shipped, the team layers its own visual identity on top of the upstream environment rather than presenting it bare. That means the familiar Synex orange accent colour, the Inter and Hack typefaces, a custom wallpaper, and a dock that arrives pre-loaded with the system's essential tools. Third-party GTK applications are nudged towards a coherent dark theme too, so the desktop doesn't start looking patchy the moment you install something from outside the default selection. For anyone curious about how the packaging itself comes together, the cosmic-synex repository remains public, so it's entirely possible to inspect the build process or compile it yourself if that's your idea of a good weekend.
The second, and arguably more consequential, addition is synex-snapshots, a new graphical application built with GTK4 and libadwaita for creating, managing and restoring snapshots on systems running Btrfs. This is the kind of tool that quietly transforms how comfortable people feel experimenting with their system, because it takes away a lot of the anxiety that normally comes with poking around configuration files or testing new software.
The application automatically detects the Btrfs layout already in place on the running system and works out which top-level subvolumes are actually in active use. Rather than mixing snapshot data in with those working subvolumes, everything is tucked away in its own dedicated subvolume, @snapshots, mounted at /.snapshots. That separation alone avoids a fair few of the headaches that can crop up when snapshot data and live system data start sharing the same space.
Synex Snapshots supports two distinct modes of operation. A Single snapshot preserves the state of one particular subvolume, while a Full snapshot captures a consistent set covering every operational subvolume the tool has detected. All snapshots are created as read-only, and every set is accompanied by its own manifest containing metadata, identifiers, and the information needed to validate the operation later on. The interface also keeps manually created snapshots visually distinct from the ones the system generates automatically as a safety net before a restoration.
Restoration is clearly where the bulk of the engineering effort went. Before touching anything, the tool runs a validation pass on the chosen snapshot set and automatically creates a fresh snapshot of the current state, labelled Pre-restore. This particular snapshot isn't cleaned up automatically; it sticks around until the user decides to delete it themselves, giving everyone an extra safety net in case a restoration doesn't go the way they expected.
The actual swap of subvolumes is handled carefully too. New restored subvolumes are prepared independently first, and only once the restoration is being applied are the current subvolumes moved into a transactional backup state, rather than being destroyed outright. Only after that does the tool put the newly restored subvolumes into their proper, canonical locations. That sequencing means the previous state stays available right through the riskiest part of the process, giving the system a way back if something goes wrong before the change is finalised.
Once a restoration has been applied, a reboot becomes mandatory, and Synex Snapshots records the state of the operation so that a second restoration can't be triggered before the system has actually booted from the new subvolumes. After the reboot, a systemd oneshot service checks that the system did indeed start from the new state, wraps up the transaction, and automatically removes the temporary subvolumes left over from the previous installation along with the operation's internal data. The Pre-restore snapshot, sensibly, is left alone for the user to deal with as they see fit.
Full restorations aim to return the entire operational set to the state represented by the chosen snapshot, rather than restoring isolated files in isolation, which keeps consistency intact across all the subvolumes involved. Coverage of /boot is also handled thoughtfully: when /boot lives inside the root Btrfs subvolume itself, it's naturally captured as part of the snapshot. When it sits on a separate ext4 partition instead, Synex Snapshots creates and validates a zstd-compressed archive so that content can be restored too, and in that scenario /boot/efi is kept untouched throughout the operation.
Every action requiring administrative privileges is kept well away from the graphical interface itself, routed instead through a limited root helper authorised via Polkit. That design choice means the application continues to run as a normal user and only escalates privileges for the specific operations that genuinely need them. Synex Snapshots 0.1.0 also ships with an interface available in both English and Spanish, along with desktop integration and a foundation the team plans to keep building on.
It's worth noting where these features debut first. synex-snapshots has landed in Semi-rolling before anywhere else, which fits the pattern the branch has been settling into: it's the proving ground where new developments circulate and pick up real-world use before being folded into the stable branch. COSMIC itself followed the same path, eventually graduating to Stable once it had been through a full cycle without significant issues, and the project intends to keep using Semi-rolling this way for future tools too. For people running Synex 13, that means synex-snapshots will arrive once it's had time to mature under real usage. In the meantime, anyone keen to try it early, and to contribute feedback along the way, can already find it in these Semi-rolling images.
The third change fixes something rather more mundane but no less important: installation on machines using legacy BIOS/MBR booting had been broken, and it's now been resolved. The root cause turned out to be the absence of grub-pc-bin on the installation media, without which the installer had no way of writing the bootloader to the MBR. The images now include both grub-pc-bin and grub-efi-amd64-bin, so installation should complete cleanly regardless of whether a machine boots in legacy or UEFI mode.
Semi-rolling 26.08.17 is available across the KDE Plasma, GNOME, Xfce and COSMIC editions, and as always, checking the checksums before creating installation media is a sensible habit to keep.
A New Home-Grown Download Mirror
Alongside the Semi-rolling refresh, Synex also switched on a new download mirror hosted on its own infrastructure, at repo.synex.ar/iso/. Until now, SourceForge has been the sole distribution point for Synex ISO images, and it isn't going anywhere; it remains the project's primary mirror and continues to hold the full historical archive of releases.
The new mirror mirrors the same structure already familiar from SourceForge, with images split across two branches. The stable branch, covering both the desktop and Synex Server editions, sits at repo.synex.ar/iso/stable/, while the semi-rolling branch, built on Debian Testing, is at repo.synex.ar/iso/semi-rolling/. Every image on the new mirror comes with its own SHA-256 checksum file, so verification ahead of creating installation media can be done without needing to reach out to a separate source.
There's a practical detail worth flagging here, because it affects how people should think about using this mirror. It only ever publishes the most recent version of each branch; once a new revision appears, the previous one is retired from the mirror. For the stable branch, that's not a huge concern since the complete version history remains available on SourceForge for anyone who genuinely needs an older release. Semi-rolling is a different story, though: no previous images are kept on either mirror for that branch, which lines up neatly with the nature of a rolling release, where the currently published image is always meant to be the one in use.
The motivation behind standing up this mirror is straightforward enough. Having distribution running on infrastructure the project itself controls gives Synex a download channel that doesn't depend on third-party services, and it complements the APT repository that already operates on the same domain. SourceForge's role hasn't changed at all as a result; it continues functioning as the primary mirror and historical archive, with no disruption to its existing links or behaviour. Images are now simply available from both places, and, as ever, checking checksums before building installation media remains good practice regardless of which mirror you pull from.
Under the Bonnet: Core Components and Package Highlights
For anyone wanting a clearer picture of what's actually inside these images, the underlying foundations are worth spelling out. The 26.08.17 build is constructed on Debian Testing and ships Linux kernel 7.1.8, systemd 261.2, OpenSSL 3.6.3, Mesa 26.1.5, PipeWire 1.6.8 alongside WirePlumber 0.5.15, Firefox ESR 140.13.0, and Flatpak 1.18.1.
Installation runs through Calamares 3.4.2 paired with the project's own calamares-settings-synex 1.0.29, and every edition includes the Synex Package Manager at version 1.2.3 alongside the newly introduced synex-snapshots 0.1.0.
Each desktop edition brings its own specific versions worth noting. KDE Plasma sits at 6.7.2, running alongside KWin 6.7.2 and KDE Applications 26.04.0.
GNOME Shell is at 50.3, paired with GDM3 50.1 and Nautilus 50.2.2.
Xfce comes in at 4.20, with xfce4-panel 4.20.8, xfce4-session 4.20.4, xfwm4 4.20.0 and Thunar 4.20.9 rounding out that edition.
COSMIC, as already covered, sits at Epoch 1.5.0.
Looking at the broader package set tracked for this build, the total sits at 2,065 packages, and it's a good snapshot of just how much comes bundled into a modern Debian-based system beyond the headline desktop components. There's a genuinely wide spread of infrastructure in there: full multimedia stacks built around FFmpeg 8.1.2 and GStreamer 1.28, print handling through CUPS 2.4.18 alongside a broad set of vendor printer drivers, and networking tools such as NetworkManager 1.58.0 and wpasupplicant. Filesystem tooling is comprehensive too, spanning btrfs-progs 7.0, e2fsprogs 1.47.4, xfsprogs 6.19.0, cryptsetup 2.8.7 and the LVM2 toolset, which together back up the journaled filesystem support Synex advertises across Btrfs, ext4, XFS and ZFS.
Development and scripting runtimes are represented by Python 3.14.6 and Git 2.53.0, while accessibility tooling includes Orca and Speech Dispatcher. Spanish-language support runs deep throughout the package set too, with hunspell-es, aspell-es, manpages-es and dedicated Spanish task packages all present, reflecting the project's Argentine roots and its genuinely bilingual approach to documentation and interface. On the hardware side, firmware packages cover an extensive range of wireless, graphics and peripheral chipsets, and Bluetooth support comes via BlueZ 5.87 with the Blueman front-end for anyone who prefers a graphical way to manage connections.
It's also worth pointing out a small quirk in how GRUB is packaged in this release: both grub-pc-bin and grub-efi-amd64-bin are present, which lines up precisely with the boot fix described earlier and confirms that both legacy BIOS and UEFI installation paths are properly catered for on these images. Meanwhile, the Synex-branded packages, things like synex-branding, synex-center, synex-gtk-defaults and synex-lvm-setup, show the layer of project-specific tooling and configuration that sits on top of the underlying Debian base, tying the whole experience together into something that feels distinctly like Synex rather than a generic Debian remix.
A Brief Word to Close
Mid-August 2026 has been a properly productive stretch for Synex. COSMIC users get a meaningful upgrade, Btrfs users gain a genuinely thoughtful snapshot and restore tool that takes system safety seriously without getting in the way, BIOS-based machines can install correctly again, and the project now has its own download infrastructure sitting alongside SourceForge. None of these changes are flashy for the sake of it; they're the sort of steady, deliberate progress that tends to define distributions built for the long haul rather than for headlines.
Disclaimer
Synex, COSMIC, Debian, KDE Plasma, GNOME, Xfce, Btrfs, and all other product and project names mentioned in this article are trademarks or registered trademarks of their respective owners. This article has been prepared in good faith using publicly available official sources, with reasonable care taken to ensure accuracy at the time of writing; however, software details can change quickly, and readers are encouraged to consult official project channels for the latest information. As always, we encourage the responsible, legal and informed use of open-source software, in accordance with each project's own licensing terms.
References
˙✧˖°📷 ༘ ⋆｡°
Comments
Post a Comment
Hello and welcome to The Distrowrite Project! We appreciate your engagement and value diverse perspectives. Our community thrives on respectful and constructive discussions. Please ensure your comments align with our guidelines: no hate speech, personal attacks, or spam. Let us foster a positive environment where everyone feels comfortable to share their thoughts and insights. Kindly direct any complaints and suggestions for any software/hardware directly, clearly and politely to the respective developer(s). Thank you for being a part of our community!