Repository navigation
Abora v3.14 DEMO
Pre-releaseAbora OS v3.1.4 DEMO
Abora OS v3.1.4 is a small demo release built on top of the stable Abora v3 base.
This is not a full major release like Denali. This build is mainly here so people can test the newer Abora changes early, especially the work around MangoWM and the current v3.1 branch. Abora v3 took 50+ VM tests to get working properly across desktops, installs, and different setups. This demo has not gone through that same level of testing yet.
There will be bugs.
If you want the most stable Abora experience, use the main v3 Denali release. If you want to test what is coming next and help report issues, v3.1.4 is for you.
Download
Release assets are available below in the GitHub Releases section.
File | Description -- | -- abora-v3.1.4-demo-x86_64.iso | Abora OS v3.1.4 demo ISO SHA256SUMS-v3.1.4.txt | SHA256 checksums, if provided RELEASE_MANIFEST-v3.1.4.txt | Release manifest, if providedAfter downloading, check the ISO with:
sha256sum -c SHA256SUMS-v3.1.4.txt
Important Demo Notice
This release is marked as a DEMO because it has not been fully tested across every desktop environment, virtual machine, or hardware setup.
Abora v3 Denali went through a lot of testing before it became stable. v3.1.4 has not had that same full pass yet.
Things that may break:
Some desktop environments may not start correctly
Some window manager configs may need cleanup
Some hardware may need extra drivers or manual fixes
Some VM setups may behave differently
Installer behavior may not be perfect on every profile
MangoWM may still need polish
App bundles may need more testing
Small branding/version text may still say older Abora versions in some places
Please do not treat this as a final stable release.
What’s New
MangoWM Work
Abora v3.1 introduced MangoWM work, and v3.1.4 continues testing that direction.
MangoWM is part of the newer Abora desktop/window manager testing path. This demo helps check how well it fits into the Abora install flow, desktop selection, configs, and default experience.
Current MangoWM focus:
Better default config testing
Cleaner session behavior
More Abora-friendly setup
Testing how MangoWM works inside the v3 branch
Finding issues before it becomes part of a more stable release
MangoWM may still have bugs. Please report anything broken, weird, missing, or confusing.
v3 Branch Cleanup
v3.1.4 keeps the stable v3 base, but starts testing smaller update-style releases instead of jumping straight into a giant v4 release.
The goal is to make Abora updates feel more normal and easier to follow.
Instead of:
v3 -> v3.5 -> v4
Abora is moving more toward:
v3.1 -> v3.1.4 -> v3.2 -> v3.3 -> v4 later
This should make updates smaller, cleaner, and easier to test.
Installer and System Polish
This build may include smaller installer and system cleanup work from the v3.1 branch.
Focus areas:
Keeping the v3 installer stable
Fixing small rough edges
Cleaning up version labels
Improving demo/testing behavior
Keeping Abora easier to install and report bugs on
This is not meant to replace the full v3 Denali testing pass yet.
Abora Identity Updates
v3.1.4 continues the newer Abora identity work from the v3 era.
Abora v3 was where the distro started feeling more like itself. v3.1.4 keeps that direction going without trying to become a massive new release.
This release is still part of the Denali/v3 family.
Known Limits
This release has known limits because it is a demo build.
Not all desktop environments have been fully tested
Not all window managers have been fully tested
Not all hardware has been tested
Not all virtual machines have been tested
MangoWM may have rough edges
Some install paths may fail
Some desktop profiles may boot differently than expected
Some app bundles may need internet or manual fixes
Some bugs from v3.1 may still exist
This release may not be daily-driver ready for everyone
If you need a stable system, use Abora v3 Denali.
Validation
This build has not gone through the same validation process as Abora v3 Denali.
Abora v3 took around 50+ VM tests before it reached the stable state it is in now. v3.1.4 is a demo and should be treated as early testing.
Expected testing status:
Basic ISO build test
Basic boot test
Basic installer test, if completed
MangoWM testing in progress
Desktop testing incomplete
Hardware testing incomplete
VM testing incomplete
More testing will happen as bugs are reported.
Updating Existing Installs
Existing Abora installs may be able to update through the normal Abora/NixOS update flow, depending on your setup.
For the cleanest test, a fresh install in a VM is recommended.
Recommended test path:
# Test in a VM first
# Do not replace your main install unless you know what you are doing
If you are already on a stable Abora v3 system, do not upgrade your main machine unless you are okay with debugging issues.
Bug Reports
Bug reports are very important for this release.
When reporting an issue, please include:
Your hardware or VM setup
The desktop environment or window manager you selected
Whether you used MangoWM
The ISO version
What broke
What you expected to happen
Any error messages
Installer log, if available:
/tmp/abora-install.log
Even small bugs help.
Abora v3 became stable because problems were tested and fixed. v3.1.4 needs that same kind of feedback.
Final Note
Abora OS v3.1.4 is a demo release.
It is not trying to be the next huge Abora version. It is here to test the next steps of the v3 branch, especially MangoWM and smaller update-style releases.
Expect bugs. Report bugs. Help make the next stable Abora update better.
Demo ISO Notice
This 3.14 build is still a demo/pre-release installer image, so a few rough edges may still exist.
A MangoWM rebuild issue was found during testing where the generated config could reference the wrong fallback path for assets/mango/config.conf, causing nixos-rebuild switch --flake /etc/nixos#abora to fail. This has been identified and will be fixed for the full 3.14 release ISO.
If you installed the demo build and hit this issue, it is not your fault. The problem is in the generated Abora MangoWM config, not your system. A repair path/fallback fix is planned so affected installs can be recovered without reinstalling.
Thanks to everyone testing the demo ISO and reporting issues — this helps make the final 3.14 release much cleaner.