Arch Linux: Hyprland 0.46.2 Crashes After Upgrade — Here's a Temporary Workaround

Yesterday I encountered a nasty surprise after upgrading Hyprland to version 0.46.2—it crashed on startup, leaving me unable to log into my Wayland session. If you’re experiencing this problem, here’s a temporary workaround so you can keep working until a fix arrives.


The Issue

Hyprland 0.46.2 appears to crash immediately upon launch, preventing you from getting into your usual tiling window manager environment.


The Temporary Fix: Downgrade to 0.45.2-3

  1. Drop to a TTY or Alternate Session

    • Press Ctrl + Alt + F1 (or any function key up to F6) to switch to a virtual terminal outside of your Wayland session.
    • Alternatively, log in via any other desktop environment or a rescue environment.
  2. Downgrade Hyprland

    • If you still have the previous Hyprland package in your Pacman cache, run:

      sudo pacman -U /var/cache/pacman/pkg/hyprland-0.45.2-3-x86_64.pkg.tar.zst
      
    • If it’s not cached, download the package from the Arch Linux Archive and install it manually:

      sudo pacman -U hyprland-0.45.2-3-x86_64.pkg.tar.zst
      
    • If you’re also using hyprlock, you will have to downgrade it as well to 0.5.0-1:

      sudo pacman -U /var/cache/pacman/pkg/hyprlock-0.5.0-1-x86_64.pkg.tar.zst
      

      Or, if it’s not cached, download it from the Arch Linux Archive.

  3. Restart

    • Log out or reboot, then select Hyprland as usual.
    • You should now be able to launch Hyprland at version 0.45.2-3 without crashing.

Wrapping Up

This is just a stopgap solution while the crashing issue is being fixed. Once I have more information, I will post an update on how you can safely upgrade to the latest package. In the meantime, downgrading lets you keep using your favorite Wayland compositor without interruption.


Disclaimer: This workaround is provided for educational purposes. Always check the official Arch Linux or Hyprland documentation for updates and exercise caution when downgrading packages.

comments powered by Disqus