Skill

Install and Manage Hyprland Desktop on Fedora Linux

A safety-first skill that installs, repairs, updates, and uninstalls Hyprland on Fedora via bundled dry-run scripts.

Works with fedorahyprlanddnfsystemctlpipewire

80
Spark score
out of 100
Updated 11 days ago
Version 15.7.0

Add to Favorites

Why it matters

Automate the complete lifecycle of Hyprland window manager on Fedora-from safety-checked installation through GPU-aware configuration, repair diagnostics, updates, and clean removal-while preserving existing desktop environments and requiring explicit user consent for all system changes.

Outcomes

What it gets done

01

Detect system specs and GPU vendor, then install Hyprland with Wayland portals, PipeWire, and display manager integration via timestamped backups

02

Generate a minimal, GPU-tailored hyprland.conf and verify binaries, portal services, and login desktop entries are functional

03

Diagnose missing configs, inactive services, or broken portals and apply targeted fixes only after user approval

04

Update or uninstall Hyprland packages safely using Fedora tools while preserving GNOME/KDE and user configuration backups

Install

Add it to your toolbox

Run in your project directory:

curl -fsSL https://spark.entire.vc/get/ag-fedora-hyprland-installer | bash

Overview

Fedora Hyprland Installer Skill

This skill runs a safety-first Fedora Hyprland install/repair/update/uninstall workflow via bundled scripts, backing up configs, dry-running package plans, and requiring explicit user approval before any mutating action. Use it when installing, verifying, repairing, or removing a Hyprland desktop stack on Fedora, while keeping any existing GNOME or KDE session intact.

What it does

This skill provides an automated, safety-first workflow for managing Hyprland (a Wayland compositor) on Fedora Linux, covering four workflows: install, repair, update, and uninstall. Before running any bundled script it resolves SKILL_DIR to the directory actually containing SKILL.md rather than assuming the working directory, and stops to ask the user if it can't be resolved from runtime context.

When to use - and when NOT to

Use it when installing or updating a Fedora-packaged Hyprland desktop stack, verifying a Hyprland session (portals, PipeWire, WirePlumber), or diagnosing the specific repair cases the workflow documents. Eight core safety rules govern every action: Fedora-only tooling (dnf, systemctl, loginctl - never apt, pacman, or yay); never blindly execute without inspecting the system first; never uninstall an existing desktop environment (Hyprland is added as an additional display-manager session choice); a mandatory timestamped backup before touching ~/.config/hypr/ or ~/.config/waybar/; GPU-aware handling that checks NVIDIA/AMD/Intel/Hybrid before touching drivers and never uses arbitrary NVIDIA .run installers; clearly identified, non-hardcoded sudo commands; idempotent actions safe to re-run; and explicit consent - showing the exact package/service change and running mutating scripts (like repair.sh --apply) only after user approval.

bash "$SKILL_DIR/scripts/detect-system.sh"
bash "$SKILL_DIR/scripts/detect-gpu.sh"
bash "$SKILL_DIR/scripts/install.sh" --dry-run

Inputs and outputs

Install: detect system and GPU, run preflight.sh (Fedora release, network, package manager, sudo access), back up existing configs, show the package plan via install.sh --dry-run, then on approval install Hyprland plus Wayland portal packages (xdg-desktop-portal-hyprland, xdg-desktop-portal-gtk), PipeWire/WirePlumber, terminal, launcher, status bar, and auth agent; write an initial ~/.config/hypr/hyprland.conf tailored to the detected terminal/launcher/GPU; verify binaries, portal services, and the hyprland.desktop login entry; then report installed packages, backup paths, and login instructions. Repair: inspect logs (journalctl -xe, the user's xdg-desktop-portal unit), run repair.sh to report missing config/portal packages/inactive services, get approval, then repair.sh --apply to fix only what it detected - other faults need manual investigation. Update and uninstall follow the same backup-then-dry-run-then-approve-then-execute pattern, with uninstall explicitly preserving GNOME/KDE and user backups.

Integrations

Eight reference manuals ship alongside the workflow scripts, covering Fedora specifics, Hyprland config, NVIDIA/AMD/Intel Mesa stacks, Wayland/environment variables, portals/PipeWire, and a troubleshooting matrix. It explicitly does not enable RPM Fusion or install GPU drivers itself, and its generated config is a minimal starting point that is not merged into an existing hyprland.conf.

Who it's for

Fedora users setting up, diagnosing, updating, or removing a Hyprland desktop who want a safety-railed workflow - backups, dry-runs, explicit consent gates - instead of running installer scripts blind, while keeping their existing GNOME or KDE session intact as a fallback.

FAQ

Common questions

Discussion

Questions & comments · 0

Sign In Sign in to leave a comment.