Hyprland plugins more seamless update process

Bugs / FRs / Support
, ,
1
Hyprland version 
Hyprland 0.51.1 built from branch  at commit 71a1216abcc7031776630a6d88f105605c4dc1c9  ([gha] Nix: update inputs).
Date: Mon Sep 22 20:54:03 2025
Tag: v0.51.1, commits: 6436
built against:
 aquamarine 0.9.4
 hyprlang 0.6.3
 hyprutils 0.8.4
 hyprcursor 0.1.13
 hyprgraphics 0.1.6


no flags were set

Describe your issue / feature…

After Arch Updated the packages, starting Hyprland was crashing the hyprland session. I gave up and few days later figured out that it could be the plugins and when i updated the plugins, everything was working perfectly.

Don’t know if hyprland should crash just because plugin wasn’t updated.

Here’s crash report if you want →

hyprlandCrashReport27948.txt (7.1 KB)

hyprlandCrashReport3464.txt (8.0 KB)

hyprlandCrashReport3061.txt (7.1 KB)

hyprlandCrashReport2456.txt (7.1 KB)

My point is, can we have more seamless plugin behaviour in one of the following ways –>

  1. Official plugins are part of hyprland itself and no need to be updating
  2. Or, only update the plugin which are enabled. updating all plugins even those which are disabled is time consuming.
  3. Or, run hyprpm update as part of package update
2 Likes
2

Currently, hyprpm reload -n exists so that you get a notification when plugins are mismatched and it will not load them until you update them. I think it’s a great mechanism. Hyprland launches, works, and you just need to run hyprpm update and your plugins are back.

This instance was a bit of a problem because ABI changed of one of the deps, not Hyprland itself, which hyprpm didn’t catch.

I made an issue here: Add a more robust ABI check system for plugins · Issue #11968 · hyprwm/Hyprland · GitHub to hopefully add a more robust ABI check for plugins and avoid this happening again (hyprpm loading plugins when they are actually ABI-incompatible)