Follow-up to #631. Upgrading a host with desktop_backend=hyprland-kms failed the installer's Plasma/KWin checks. With that policy set, the installer now checks for Hyprland and UWSM instead.
Tested with an upgrade through linux_install.sh --package on Arch with Hyprland 0.56.2 (UWSM).
Activity
5
Nonary13d agoVerified commit b407e712ce8dbfe411b3bb17bf0e37dce7690e99 against canary at df3b45b4df149ab9912bf46b8a38da31aa45afe5. No blocking issue found in the supported Arch/CachyOS upgrade path: the existing hyprland-kms policy selects Hyprland/UWSM checks before installation, the default Plasma/KWin checks are preserved, and package-backed local deployments use the same installer.
The documentation caveat for the non-Pacman direct-file updater is non-blocking; no runtime defect in a supported configuration was established.
Validation was source-only, including inspection of the added regression fixture. No builds, tests, or live compositor validation were run. CI run 743 remains action_required.
aronjanosch12d agoNarrowed the docs sentence to the installer path, including package-backed local deploys; the direct file updater is no longer implied. The check itself is live-tested: my local deploys on Arch + Hyprland KMS have run through it since the fix.
Please address the non-Pacman local-deploy path described in the inline comment.