thanks to strellic for this challenge

If selecting a qube other than dom0 fails for backups and trying to choose a different qube causes error 127, try installing zenity in that qube.

You don’t need an intro, a conclusion and a journey just to write one post, the readers only want information. Just give the readers what they want

Here’s how to make helix-gpt work

This is how to automate and sync your backups across devices.

By using tunnels, you can forward only requests, without installing applications on the target machine

QubesOS is amazing for security, and equally amazing at making CTFs 10x harder than they need to be. It’s the firewall’s fault.

The reason why audio won’t work out of the box in minimal templates (debian-12-minimal, fedora-41-minimal) is that the package responsible for sending audio from VMs to your host (dom0 or sys-audio), pipewire-qubes, isn’t included in them by default.

When you try to run FreeRDP 3, you will likely get the BadAtom error.

QubesOS is built on the principle of isolation, and GPUs aren’t designed to meet the strict isolation requirements QubesOS demands because they prioritize performance instead.

Nix is great for keeping your system clean and your sanity slightly intact. But thanks to how QubesOS handles templates and persistence, it’s not plug-and-play.

After this guide, you will be able to:

• replace apt or pacman with the nixpkgs package repository, even if you don’t care about declarativity
• use home-manager to set up all your configs and apps declaratively with just one config file and use it on any machine
• use any nixpkgs package one time only and without bloat, fix dependency hell and weird dependencies