A few Country have switch to NixOS ecosystem.

Like these country that i see:

France

And

The Netherlands

France (DINUM) uses NixOS via project Sècurix and Bureutix

Netherlands (SSC-ICT and DICTU) develop a sovereign government desktop called DAWO (Digitaal Autonome Werkimgeving Overheid)

That based on nixOS

Now, We need to focus to security right now.

(My english are bad i guess, sorry my grammar was so broken)(Indeed it broken)

messed up an ext4 partition resize on nixos and now stuck in an emergency mode boot loop.

ran ⁠e2fsck⁠ from an arch live iso and fixed the filesystem errors, and confirmed the uuid in ⁠hardware-configuration.nix⁠ matches ⁠blkid⁠.

rebooting still hits emergency mode though.

i need to run ⁠nixos-rebuild switch⁠ from the live environment to fix initrd, but ⁠arch-chroot /mnt⁠ fails because nixos doesn't have standard ⁠/bin/bash⁠ paths or ⁠/bin/sh⁠ symlinks set up without activating the system link.

how do you properly enter/chroot a nixos root partition from a non-nixos live usb to rebuild? do i just need to flash an official nixos live iso for ⁠nixos-enter⁠, or is there a way to do it from arch?

Hey all,

I've been working on a Wayland compositor and desktop environment written in Zig andsome C

Just added a Nix flake and NixOS module, so figured I'd share it here.

It's a bit different from most DEs as the compositor and entire desktop shell run in one process, with a custom scene graph, plenty of theming options, window effects, and a pan-and-zoom desktop.

To build it:

nix build github:oxydizer/rediwm

It's early days for NixOS support, so real-world testing and feedback would be appreciated.

The project is open source and AI-assisted, for transparency.

https://github.com/oxydizer/rediwm

Would it be possible to provide a public repository which has offline installers of various Wwise versions? I would use it to distribute new versions for easier access for me and others who don't want to use the installer. Would that be okay with Audiokinetics EULA?

Would be a huge repo though... Maybe there's another way?

The only thing I found is a python script that downloads versions without the launcher (not sure if it's even working....). How would I use that in a NixOS configuration?

I know there have been attempts, including from NixOS itself, NUR, and others. However, most of them rely on manually adding repositories rather than automatically indexing them from GitHub.

I also know that searching GitHub with path:flake.nix won't reveal every repository. There are limitations, such as GitHub's 1,000-result limit for search queries, as well as repositories that only contain personal configurations or devshells.

But with a few workarounds, you could have a server running 24/7 for several days to collect results. Then, you could either run nix flake show or use an rnix parser to identify which repositories actually provide packages. It wouldn't necessarily need to know how many packages each repository contains or anything like that.

Why hasn't anyone attempted this? I mean, I don't think the number of people who own private servers is particularly small. Are there other challenges I haven't considered?

I currently use arch, i tried using nixos on an old laptop but never really liked how i was setting up my configs and it felt weird and "not right". I wanna know how im supposed, or atleast how yall setup your nixos

Hello, I want to declaratively configure my browser but I have a problem, I can't set the theme of the browser. I tried to diff prefs.js and set the diffs in programs.librewolf.profiles.<user>. settings but it doesn't work. Can anyone help me?

I have been following both this sub and /r/unixporn for years now but I have a tendency to not share the things I do and like with others.

I want to try and do that more, so what better place to start than the screen I stare at all day. This is my NNN (NixOS, Niri, Noctalia) setup. It runs on a Framework 13, and the main idea is that everything takes its colors from the wallpaper. Noctalia makes a palette out of it, and templates push that into GTK and Qt apps, Ghostty and the terminal tools, Zen, Zed and Obsidian, even the folder icons (a recolored Numix-Circle). Any picture I drop into the wallpaper folder gets included in the loop.

Under the hood, the rest of the system is pretty cool too. The root gets wiped on every boot and only what I declared comes back, the disk unlocks with the TPM under secure boot, and when I push a signed commit to my config, the laptop deploys it by itself using Comin.

The whole config is public if you want to steal anything: https://codeberg.org/BW20/dots. Happy to answer questions about any of it, especially the theming, which took way more fiddling than anticipated.

So I've had restic pushing my home server backups to S3 for a while, and two things kept nagging me. 1) nothing stops it from grabbing a database halfway through a write. 2) the one time I actually had to restore after a dead disk, it was me going service by service, digging folders out of the snapshot.

I decided to finally pull the setup out of my config into its own module, snapback: https://codeberg.org/BW20/snapback It's my first real nix project besides my personal config, so I am excited to share it!

Before each run it takes a zfs snapshot and bind-mounts it over the paths you back up, just for that run. Restic sees one moment in time but still records the normal paths, so nothing looks different in the repo. Each service declares its own entry next to the rest of its config (paths, which units to stop, optionally how to load a dump back), and then offsite-restore brings back everything or just the services you name. It downloads first, so if that fails nothing's touched, and it keeps whatever it replaced.

services.snapback = {
  enable = true;
  mountPoint = "/persist";
  name = "offsite"; # your services.restic.backups entry

  entries.vaultwarden = {
    paths = [ "/persist/vaultwarden" ];
    units = [ "vaultwarden.service" ];
  };
};

My bucket key can't delete anything, and that turned out to be the fiddly part with restic: it can't clear its own locks. So failed runs retry on a fresh snapshot and restores skip the lock. It works fine with impermanence/preservation setups too, that's what I run.

There's a VM test on every push that checks the backup really reads the snapshot and not the live file, plus a restore and a failed run.

It's pre-1.0, so if any option names feel off, now's definitely the time to tell me. Mirror's on GitHub too :)

Hey folks,

I got a notification recently saying that 3 of my servers hadn't rebooted in over 7 days. This usually doesn't happen, as I use the following module to reboot these servers automatically with kernel updates:

{
  config,
  lib,
  pkgs,
  ...
}:
let
  cfg = config.server.kernelReboot;
in
{
  options.server.kernelReboot.enable = lib.mkEnableOption "nightly reboot if booted kernel != current";

  config = lib.mkIf cfg.enable {
    systemd.services.kernel-reboot = {
      serviceConfig.Type = "oneshot";
      script = ''
        booted="$(readlink /run/booted-system/{initrd,kernel,kernel-modules})"
        current="$(readlink /run/current-system/{initrd,kernel,kernel-modules})"
        if [ "$booted" != "$current" ]; then
          ${pkgs.systemd}/bin/shutdown -r +1
        fi
      '';
    };

    systemd.timers.kernel-reboot = {
      wantedBy = [ "timers.target" ];
      timerConfig.OnCalendar = "*-*-* 02:00:00";
    };
  };
}

My CI/CD pipeline is functional. I just tested it and verified that my servers automatically rebuilt against rev 718f670e845328e9c2cecdd832835712b2cbd065 which is the latest update to stable. But after the rebuild and reboot, new kernels are not live, and I'm stuck on 6.18.57. The 6.18 line is being actively bumped in nixpkgs, as shown by https://github.com/NixOS/nixpkgs/commit/bcd592b6b52ab8e270140b2c8bf2a5977cf4a481

Any idea why this would happen? Config at https://codeberg.org/sensei/nixos

Any help appreciated

hat andere, blöde Distributionen verglichen. Gut gemacht!

verdammt, mann

Oder einfach derjenige, der NixOS so sehr hasste.

Velleicht will ich ihn gar nicht hassen.

Vielleicht ist das ja in Ordnung, wenn du NixOS nicht mehr nutzen willst.

I made a NixOS module and CLI for changing NVIDIA laptop power and current limits at runtime. It loads an edited VBIOS into memory at boot; nothing is flashed, and it lets you apply or release runtime overrides without rebooting.

On my RTX 3080 Ti Laptop: 117.7 → 124.6 W, with a repeatable 5.9% improvement in FurMark score (power and current ceilings are configurable in Nix)

One GPU validated, driver 615.71.09 required (for now). Installation instructions:

https://github.com/Nickdom1/gpu-power-policy

Badge: my NixVegas CTF prize 🙂

Hi, I'm pretty new to the NixOS and Nix community but I built a tool for my own setup and thought someone else might find it useful.

lazyflakes is a TUI in the lazygit style, seach a nixpkgs, pick stable/unstable version of each package and then either:
- open a shell with selected packages
- generate a shell.nix or flake.nix in the current directiory with them
- or install them into your systems configuration
it doesnt update your own configuration files, it just adds lazyflakes.nix that you import to your setup.

It's the first release so it might not work perfectly although I've tested it on my own NixOS (with channels and with flakes) and on home-manager and didn't have any issues so far.

I should also disclose that claude helped me to develop it.

you can find the repo in https://github.com/MaJDa-sh/lazyflakes

to test it you can just use:

nix profile install github:MaJDa-sh/lazyflakes

or:

nix run github:MaJDa-sh/lazyflakes

if you try it, I'd appreciate any feedback, bug reports or suggestions.

Good morning. After updating NixOS, AnyDesk stopped working. Whenever I try to launch it, I get a “Services Crash” error. With ChatGPT’s help, I suspect the issue may be related to GDB.

       PID: 10654 (.anydesk-wrappe)
       TID: 10654 (.anydesk-wrappe)
       UID: 1000 (growlithe)
       GID: 100 (users)
    Signal: 11 (SEGV) si_code: SEGV_ACCERR
 Timestamp: Tue 2026-10-27 07:31:48 -03 (14min ago)

Command Line: /run/current-system/sw/bin/anydesk Executable: /nix/store/jb4br1fifgsi9dci15mhf9cih990hmnd-anydesk-8.1.0/bin/.anydesk-wrapped Control Group: /user.slice/user-1000.slice/user@1000.service/app.slice/app-AnyDesk@c0f066efe0a4462d9e010bb51e3a16ba.service Unit: user@1000.service User Unit: app-AnyDesk@c0f066efe0a4462d9e010bb51e3a16ba.service Slice: user-1000.slice Owner UID: 1000 (growlithe) Boot ID: 3efdfbc20ba54aef9821096426879c7f Machine ID: 4eee646a79794136b67bcdea7c75c8b4 Hostname: nixos Storage: /var/lib/systemd/coredump/core.\x2eanydesk-wrappe.1000.3efdfbc20ba54aef9821096426879c7f.10654.1793097108000000.zst (present) Size on Disk: 227.7K Message: Process 10654 (.anydesk-wrappe) of user 1000 dumped core.

            Stack trace of thread 10654:
            #0  0x000073c18f870a74 dl_main (/nix/store/pqyiidz5mi73wv5f91d48s9plcqyj5bz-glibc-2.44-57/lib/ld-linux-x86-64.so.2 + 0x25a74)
            #1  0x000073c18f86d630 _dl_sysdep_start (/nix/store/pqyiidz5mi73wv5f91d48s9plcqyj5bz-glibc-2.44-57/lib/ld-linux-x86-64.so.2 + 0x22630)
            #2  0x000073c18f86eee1 _dl_start (/nix/store/pqyiidz5mi73wv5f91d48s9plcqyj5bz-glibc-2.44-57/lib/ld-linux-x86-64.so.2 + 0x23ee1)
            #3  0x000073c18f86dbe8 _start (/nix/store/pqyiidz5mi73wv5f91d48s9plcqyj5bz-glibc-2.44-57/lib/ld-linux-x86-64.so.2 + 0x22be8)
            ELF object binary architecture: AMD x86-64

Failed to invoke gdb: No such file or directory.

AnyDesk worked in the previous system generation.

The update changed the kernel from 7.2 to 7.3 and KDE Plasma from 6.7 to 6.8.1, along with several other packages. Those are the changes I was able to identify.

For anyone looking to try an accessible spin of NixOS for themselves or a relative, NixBook OS has been absolute gold for my use case.

You see, I was recently asked to install Linux on an elderly family member's computer. We wanted something locked down, hard to infect, and even harder to break. But something still familiar enough to a lifelong Windows user. Ideally we also wanted a setup I could access remotely for long distance tech support.

My first thought was to go with Zorin OS, which was my entry point to Linux back in February. But I hesitated at this thought because it would mean that I'd have to re-learn things in order to help whenever any technical problems arose.

Then it hit me: what if my relative just used NixOS, like I do? Then I’d be better able to help when issues arose. And I thought I could probably configure a host that made things more simple.

Now on the surface, that sounds absolutely nuts. Starting to use Linux, in your 70s, after a lifetime of Windows is already a tall order. But then adding NixOS on top of that would be asking too much for anyone.

Enter NixBook OS

This was a happy find I just stumbled across, when I started researching how to make NixOS easier to use. NixBook OS is basically a spin of NixOS that abstracts almost all of the complexity of using NixOS while still letting you have all the benefits. It's for new users who want a simple “chromebook like” computer experience

How does it work, exactly? Well NixBook OS ships preconfigured with Flatpak, printer support, auto-updating, garbage collection, and generation management scaled to disk space. It also ships with Cinnamon (the same desktop as Linux Mint) to feel familiar to Windows users.

One odd thing I clocked was that NixBook OS doesn't auto-optimise, which seems like a weird choice for a distro marketed toward older hardware, which usually has a lot less storage. But I guess since they intend you to install most things via Flatpak anyway, I imagine they assume anyone touching the config file knows enough to set up some other things like optimising.

And to be clear you can still change everything in in your /etc/nixos/configuration.nix. As long as you don't touch anything in /etc/nixbook, updates and support keep working.

The Setup

So after a few days of mucking about in a VM, I decided the best way to set up NixBook OS was to create a module called support.nix. I then imported it into the default configuration.nix. The module I created lets me add and remove packages, create a separate admin account just for me, lock down Flatpak and WiFi behind an admin password, and it sets up a way for me to remote access from my own NixOS computer.

Again, this is a separate module that is imported. So none of it interferes with auto-updates or touches the original config.

The Result

So far we are a few weeks in, and NixBook OS is working perfectly. It's a simple setup, and knowing my relative can't install anything without my password gives me real peace of mind. And should anything come up, all I need to do is open RustDesk and I will have immediate access to her computer.

Disclaimer, Literally

I have zero connection to the NixBook project. I'm just happy to share a project that actually makes NixOS accessible to real Linux beginners.

You can find the project here at their GitHub: https://github.com/mkellyxp/nixbook

And you can download their ISO here:
https://nixbookos.org/

i was just discovering apps then i came across the helix editor. its pretty good and have all basic to moderate features built in. but i dont understand why there is very little gossip or none about it while nvim gets so much hype.
i just switched to it and having very good experience till now.
anyone can share ur experience.. any thoughts about helix.

Hey everyone, I've been using NixOS for two weeks now and wanted to share some issues and annoyances I ran in to.
I recently bought a Framework 13 and decided to install NixOS on it. Coming from Arch it has been quite a bit different.

I want to preface this by mentioning that overall it has been a nice experience. I really like the declarative way of managing my system and the Nix language felt really easy to learn if you have prior programming experience. I don't want this to come off as a negative rant.

Installation

At first I wanted to use the GUI installer. However, I tend to place my home directory into its own btrfs subvolume, which the GUI installer didn't seem to allow. I ended up performing a manual installation based on the instructions provided in https://wiki.nixos.org/wiki/Btrfs .

I did end up using top-level subvolumes instead of nested subvolumes though, that's how I've been doing it on Arch.

Everything else went smoothly and I quickly had my system set up how I wanted it.

The Wiki confusion

Speaking of the wiki it's been a somewhat confusing situation for a newcomer. Searching for things online usually tends to bring up results from both the official wiki.nixos.org and nixos.wiki. Sometimes with the one wiki coming up first, sometimes the other. While both mostly have identical contents, sometimes one has information that's missing from the other.

Especially for a newcomer this is confusing. From my understanding wiki.nixos.org is the official wiki with the most up-to-date content?

To flake or not to flake

Something I've noticed from the start is that flakes seems to be the feature everyone is using. While I started out with not using flakes, I quickly found answers, guides, and tutorials online which expected flakes to be used on a system. I did switch over my configuration over to using flakes after a few days, since I found a guide online which used flakes. I knew the problem I was trying to solve could also be solved without flakes, but I didn't want to keep searching.

Overall I'm happy with using flakes to manage my configuration. I just wish this would be a bit more standardized. The split online between flakes and not flakes is a bit confusing for someone starting out.

Missing options in the configuration

Since my scanner is behind NAT, it cannot be found using broadcast messages. On Arch I simply edited /etc/sane.d/airscan.conf to add a manual entry for my scanner. Simple enough, there's probably just an extra options configuration I can add it to, right? Well not really. There's an issue dating back to 2016 which mentions that there's missing options: https://github.com/NixOS/nixpkgs/issues/17411
This issue has been closed in favor of https://github.com/NixOS/nixpkgs/issues/295008, however the underlying problem has not been solved.

I ended up with this option in my config now (based on one of the comments in that issue), which took some time to understand what it's doing, and feels a bit hacky:

     extraBackends = [
      (pkgs.sane-airscan.overrideAttrs (previousAttrs: {
        postInstall = (previousAttrs.postInstall or "") + ''
        echo -e '[devices]\nCanon Scanner = http://192.168.10.50:80/eSCL/, eSCL' >> $out/etc/sane.d/airscan.conf
        '';
      }))

I had a similar issue with another package, where I ended up creating an overlay.

Searching for options and packages

What surprised me was that the common way for looking up options and packages seems to be using https://search.nixos.org . Coming from Arch I expected a local option. Looking in the wiki I found nix search which requires enabling experimental features.

Development environments

Using shells for different projects I'm working on felt really nice. However the option to both use nix-shell and nix develop was a bit confusing at the beginning. Most of the NixOS wiki doesn't cover creating development environments with flakes at all. I did quickly learn to create flakes with shell environments for g++ and Java.

One major issue has been python. I've been working with projects which expect you to use a virtual environment. After installing the modules with pip I ran into the famous

ImportError: libstdc++.so.6: cannot open shared object file: No such file or directoryImportError: libstdc++.so.6: cannot open shared object file: No such file or directory

After looking through the wiki I found out that the recommended way is to use buildFHSEnv. This however seems to be causing issues with direnv and using the shell in Visual Studio Code.

Other issues

Since I've been using VirtualBox on my previous system I decided to give it a try on NixOS. However to my surprise it was being compiled from source. I later learned that this is due to me enabling the extension pack which turns the package unfree. According to the wiki the proper way to avoid this is https://github.com/NixOS/nixpkgs/pull/71127 , which hasn't been worked on since 2019.

After building VirtualBox I ran into a segfault with an issue which has been open since 2021. After adding an environment variable as described here https://github.com/NixOS/nixpkgs/issues/149812#issuecomment-1004387735 it ended up working though.

Since the wiki recommends using virt-manager instead I decided to give that a try. However I'm getting a lot worse performance than with virtual box.

been using for more than 6 months

Hi everyone! I’m working on Nix Pro, a JetBrains plugin with native Nix language support and integrations with Nix tools and language servers.

The latest version, version 2026.1.12 focuses on setup, flake updates, navigation, and debugging:

• Easier nixd setup: The setup assistant detects NixOS and Home Manager configurations exposed by your flake, helps populate nixd settings, and validates package and option expressions.
• Reviewable flake updates: Input updates now have cancellable progress, refreshed revisions, clearer failure messages, and a before-and-after flake.lock diff.
• More reliable completion: Package and library suggestions refresh when relevant Nix files or lock files change, accounting for nested flakes, target systems, and configured package overlays.
• Faster symbol navigation: Project-wide symbol indexing makes finding definitions quicker, particularly in larger configuration repositories.
• Better error navigation: Follow source locations directly from Nix run-console errors, open derivation build logs, and enable full evaluation traces in run configurations.

The aim is to keep the workflow connected: configure the language server, edit your expressions, review dependency updates, and follow failures back to the relevant code.

For transparency, Nix Pro is a paid plugin.

JetBrains Marketplace

Happy to hear any feedback, suggestions, etc to make your Nix experience even better!

Like you tell me I have to code a flake.nix just to get a shell to code without cargo saying ho you don't have that or this.

Don't get me wrong here I love nix, being able to code my config or my package or even to get my config into other people machines but as a CS student, this is so fustrating.

>Sorry for the bad grammar, english is not my first language