Introducing ShaniOS: An Arch-Based Distro with Immutable Design and Flatpak Integration

someone needs to name after her-

2 Likes

shanios release 2025.09.08

https://sourceforge.net/projects/shanios/files/plasma/20250908/signed_shanios-plasma-2025.09.08-x86_64.iso/download

and

https://sourceforge.net/projects/shanios/files/gnome/20250908/signed_shanios-gnome-2025.09.08-x86_64.iso/download

these include packages for guest vm

1 Like

Still not loading up on vmware. I do have 3D set.

Live installer has sway :thinking:

Okay but I don’t know what it needs to make it work on vm. I guess i won’t bother with it. I just wanted it to work out of the box to try it. :person_shrugging:

Hello everyone,

We’re thrilled to announce the latest release of ShaniOS — version 2025.10.05 for both GNOME and Plasma editions. This release focuses on faster deployments, lower installation requirements, improved storage optimization, and expanded hardware compatibility.

:inbox_tray: Downloads


:small_blue_diamond: Key Improvements

Deployment & Updates

  • Faster Downloads: shani-deploy uses aria2c for accelerated multi-connection downloads.

  • Smart Storage: Integrated duperemove to automatically optimize disk space usage.

  • Reduced Storage Requirements: Installable on devices with only 28 GB storage.

  • Better Updates: Clear dialog notifications and terminal-based deployment.

  • Multiple Printer Drivers: Expanded compatibility for HP, Canon, Epson, Brother.

GNOME Edition Highlights

  • GNOME 49, Mutter 49, Nautilus 49

  • GNOME Console, GNOME Software 49

  • Evolution Data Server integration

Plasma Edition Highlights

  • KDE Plasma 6.4.5, KDE Frameworks 6.18.0

  • Qt 6.9.2, KWin compositor with HDR support

  • Dolphin 25.08.1, Konsole 25.08.1, Discover 6.4.5


:small_blue_diamond: Common System Updates

  • Linux Kernel: 6.16.10

  • Mesa: 25.2.4

  • NVIDIA Drivers: 580.82

  • systemd: 258

  • Pipewire: 1.4.8

  • GStreamer: 1.26.6

  • FFmpeg: 8.0

  • NetworkManager: 1.54.1

  • BlueZ: 5.84

  • Podman: 5.6.2

  • Distrobox: 1.8.1

  • Python: 3.13.7

  • Git: 2.51.0

  • GCC: 15.2.1

  • Zsh: 5.9

  • Starship: 1.23.0

Does it work in a VM yet? Qemu at least

It’s using archlinux so yeah

And flatpaks only. Any plans for creating your own forum ?

Flatpaks are cool but solely relying of flatpaks on arch (which is a rolling release) is a little bit controversial i guess. Flatpaks are community maintained and it is possible to have outdated flatpaks i would assume. But i agree that we need a separate app layer on linux to separate it from the system layer so there has to be a standart and flatpak could be that standart. If i am not mistaken there is also the “appimage” and “snap” concepts which are similar. But of course just like anything in linux, it is up to the community to make it viable.

The immutable OS concept is cool. If something goes wrong you can just roll back, and you don’t lose data. The “app layer” not touching the system layer is also great. You can not break such a system even if you tried.

Can we also get a RPI version?

Flatpaks are not cool and are wasting alot of user space. It’s a nightmare in fact. Steam is a perfect sample of it because it’s sandboxed and you need to do things to let it find your hard drives. New users will get frustrated because it does not work out of the box like they are used to in windows.

Steam native is much better.

Personally, immutable and Flatpak-centric are two turn-offs for me. I just don’t have any interest at all with immutable Linux distros. And Flatpak-centric? No thanks. I do have a couple Flatpak apps installed on EndeavourOS, but I prefer to steer clear if possible. Flatpak apps are huge compared to their repo counterparts. And sometimes either unsafe, or not up-to-date, or both.

But that’s the beauty of Linux: CHOICE. While ShaniOS is definitely not for me, I’m sure many others will love it. So, @librewish, good luck with ShaniOS!

3 Likes

I understand that linux purists don’t like flatpak, and yes flatpaks are huge, but that is becuse they are made to work “anywhere”. We have to face the reality that there are too many distros out there using too many different sub-systems. All distros need a different type of package, which is built in a different way, with different dependencies and even the config files are in different places…

Linux is fragmented. That is not flatpak’s fault. And if you want to make something to work in this fragmented system, you need to create a “self-sustaining system”, so that it can work by itself, without the need of any external resource. Even at this state, some flatpak apps still have issues on some iterations of Linux.

So when you look at it like this, flatpaks are amazing. In my case for example, i am writing this from the flatpak version of Chromium. If that wasn’t available to me, i would still be using an ancient version of chromium which arch arm refuses to update since november last year. If you type “pacman -Ss chromium” you’ll see that it is still version 131. I am on 141. So even arch is not perfect.

It’s not. You need to do some more research.

But i don’t want to waste time on this. This debade is going on for years. If it is not systemd it’s about flatpaks and so on.

1 Like

on flatpak :wink: