Toxicblue

Overview

toxicblue is a project that leverages the BlueBuild template to create minimally-opinionated Fedora Atomic operating system images for various Wayland compositors. The project aims to provide ready-to-use images with sane defaults for the following compositors:

• Hyprland (with waybar)
• niri (with waybar)
• Qtile (experimental)
• River (with waybar)
• Sway (with waybar)
• Wayfire (with wf-shell)

Features

• Saner SDDM defaults
• Optimized waybar defaults
• Comprehensive toolkit for a functional Wayland compositor desktop
• Pre-configured, minimally opinionated setups for each supported compositor

Purpose

While the Fedora Atomic ecosystem offers excellent base images and tools for immutable image building, it lacks readily available images for most Wayland compositors (except Sway). toxicblue fills this gap by providing images with sensible defaults for a variety of Wayland compositors.

Customization

For custom modifications, it's recommended to create a new repo using the BlueBuild template rather than forking this project. Set your base-image to a toxicblue image to apply your customizations efficiently without constant upstream synchronization.

Installation

Available Images

Note

nvidia images are recommended for systems with Nvidia GPUs Turing or newer (RTX Series | GTX 16xx Series+).

Name	Compositor	Nvidia Support
hyprland	Hyprland	No
hyprland-nvidia	Hyprland	Yes, open drivers
niri	Niri	No
niri-nvidia	Niri	Yes, open drivers
qtile	Qtile	No
qtile-nvidia	Qtile	Yes, open drivers
river	River	No
river-nvidia	River	Yes, open drivers
sway	Sway	No
sway-nvidia	Sway	Yes, open drivers
wayfire	Wayfire	No
wayfire-nvidia	Wayfire	Yes, open drivers

Rebasing Process

To rebase an existing Silverblue/Kinoite/Sericea installation to the latest toxicblue build:

Important

Only the latest tag is supported. [!NOTE] Two reboots are required. The first boot into toxicblue provisions the necessary SDDM user, a one-time step.

1. Rebase to the unsigned image:

   rpm-ostree rebase ostree-unverified-registry:ghcr.io/toxicwebdev/$IMAGE_NAME:latest

2. Reboot:

   systemctl reboot

3. Rebase to the signed image:

   rpm-ostree rebase ostree-image-signed:docker://ghcr.io/toxicwebdev/$IMAGE_NAME:latest

4. Final reboot:

   systemctl reboot

Post-install

Nvidia

If you are using an nvidia image, run this after installation:

rpm-ostree kargs \
    --append-if-missing=rd.driver.blacklist=nouveau \
    --append-if-missing=modprobe.blacklist=nouveau \
    --append-if-missing=nvidia-drm.modeset=1 \
    --append-if-missing=nvidia-drm.fbdev=1

You may also need this (solves flickering and LUKS issues on some nvidia hardware):

rpm-ostree kargs \
    --append-if-missing=initcall_blacklist=simpledrm_platform_driver_init

Nvidia optimus laptop

If you are using an nvidia image on an optimus laptop, run this after installation:

ujust configure-nvidia-optimus

Screenshots

Verification

Images are signed using Sigstore's cosign. Verify signatures by downloading the cosign.pub file and running:

cosign verify --key cosign.pub ghcr.io/toxicwebdev/$IMAGE_NAME:latest

Contributing

Please refer to the contributing documentation and adhere to the Code of Conduct.