✖ Headers version mismatch. Please run hyprpm update to fix those.

[ronasimi]

This might be a packaging issue. I'm running hyprland packages from extra-testing

❯ hyprpm update
*sudo* password for ron: 

! Cloning https://github.com/hyprwm/Hyprland, this might take a moment.
✔ Hyprland cloned
✔ checked out to running ver
! configuring Hyprland
✔ configured Hyprland
✖ failed to install headers with error code 4 (Headers version mismatched)
→ if the problem persists, try running hyprpm purge-cache.
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━  5 / 5  Failed

✖ Headers version mismatch. Please run hyprpm update to fix those.
❯ hyprpm list
→ Repository hyprgrass:
  │ Plugin hyprgrass
  └─ enabled: true

  │ Plugin hyprgrass-backlight
  └─ enabled: Plugin failed to build

  │ Plugin hyprgrass-pulse
  └─ enabled: false``

❯ hyprctl version
Hyprland 0.52.0 built from branch unknown at commit unknown unknown (unknown).
Date: unknown
Tag: unknown, commits: 0

Libraries:
Hyprgraphics: built against 0.3.0, system has 0.3.0
Hyprutils: built against 0.10.1, system has 0.10.1
Hyprcursor: built against 0.1.13, system has 0.1.13
Hyprlang: built against 0.6.3, system has 0.6.3
Aquamarine: built against 0.9.5, system has 0.9.5

no flags were set

[vaxerski]

Looks like arch still uses meson... Anyways, https://gitlab.archlinux.org/archlinux/packaging/packages/hyprland/-/issues/30#note_353163

@fufexan can we drop meson for the love of god?

[fufexan]

Will do soon.

[ronasimi]

Thanks, I assumed it was packaging related but somehow didn't think to check the issues on Arch's gitlab. My bad

[Homisiak]

@vaxerski what can I do rn to (even if temporarily) fix the problem?

[vaxerski]

it's my job 😅

[RT-Tap]

Sooo I switched to to the -git version specifically for this fix and when I try to run hyprpm update it seems everything is up to date:

hyprpm -v update
[v] installed version returned: Hyprland 0.52.0 built from branch main at commit 06b37c390715e05f852076a8d1160e27c5cd291c clean (protocols/outputMgmt: fix wlr-randr by defering success event until monitor reloads ( 12236)).
Date: Sat Nov 8 18:45:53 2025
Tag: v0.52.0-2-g06b37c390, commits: 6561

Libraries:
Hyprgraphics: built against 0.3.0, system has 0.3.0
Hyprutils: built against 0.10.1, system has 0.10.1
Hyprcursor: built against 0.1.13, system has 0.1.13
Hyprlang: built against 0.6.3, system has 0.6.3
Aquamarine: built against 0.9.5, system has 0.9.5

no flags were set


[v] parsed commit 06b37c390715e05f852076a8d1160e27c5cd291c at branch main on Sat Nov 8 18:45:53 2025, commits 6561

✔ Headers up to date.
✖ No repos to update.
✔ Ensuring plugin load state
✔ Plugin load state ensured

but when I try to add a plugin I get:

✖ Headers outdated, please run hyprpm update.

Is it still not using the latest commit or am I doing something wrong here?

[danielwerg]

i downgraded:

sudo rm -r /usr/bin/hyprland-{dialog,donate-screen,update-screen}

sudo downgrade hyprgraphics hyprlock hyprland hyprtoolkit
# loading packages...
# warning: downgrading package hyprgraphics (0.3.0-1 => 0.2.0-2)
# warning: downgrading package hyprland (0.52.0-1 => 0.51.1-6)
# warning: downgrading package hyprlock (0.9.2-4 => 0.9.2-3)
# warning: downgrading package hyprtoolkit (0.2.4-1 => 0.2.1-1)

yay -S hyprland-qtutils

hyprpm update

[vaxerski]

@RT-Tap are you sure your hyprpm is also up to date and not left over from some other thing? check whereis hyprpm, should only have one.

If that doesn't help, please attach the log where the error happens but run hyprpm with --verbose

[RT-Tap]

EDIT: I noticed there was a new release so I rebuilt and everything is fine. Thank you for all your help @vaxerski .

So I definitely only have 1 hyprpm (/usr/bin/hyprpm) that was created at the same time as the upgraded hyprland (/usr/bin/hyprland) so that leads me to believe it was upgraded as well. And when i run hyprpm with verbose it's the same as what I posted above but here it is again:

 hyprpm --verbose add https://github.com/Duckonaut/split-monitor-workspaces
[v] running version returned: Hyprland 0.52.0 built from branch main at commit 06b37c390715e05f852076a8d1160e27c5cd291c clean (protocols/outputMgmt: fix wlr-randr by defering success eventuntil monitor reloads ( 12236)).
Date: Sat Nov 8 18:45:53 2025
Tag: v0.52.0-2-g06b37c390, commits: 6561

Libraries:
Hyprgraphics: built against 0.3.0, system has 0.3.0
Hyprutils: built against 0.10.1, system has 0.10.1
Hyprcursor: built against 0.1.13, system has 0.1.13
Hyprlang: built against 0.6.3, system has 0.6.3
Aquamarine: built against 0.9.5, system has 0.9.5

no flags were set

[v] parsed commit 06b37c390715e05f852076a8d1160e27c5cd291c at branch main on Sat Nov 8 18:45:53 2025, commits 6561
✖ Headers outdated, please run hyprpm update.

No mention of hyprpm in the hyprland logs (have debug:disable_logs = false) and nothing in $XDG_RUNTIME_DIR/hyprpm like not even a file its just an empty directory.

[barkely128]

Managed to rollback while avoiding the AUR.

You'll need the cached 'hyprland-qtutils' package

sudo pacman -U /var/cache/pacman/pkg/hyprland-qtutils-0.1.5-4-x86_64.pkg.tar.zst

It should conflict with the new 'extra/hyprland-guiutils' package, if there are any issues, just remove it.

Then I just used

sudo downgrade hyprland

And chose the latest 0.51 micro version.

[tekstryder]

For completeness I xref this discussion in my Arch packaging issue:

• https://gitlab.archlinux.org/archlinux/packaging/packages/hyprland/-/issues/30#note_353665

[tekstryder]

v0.52.1 release addresses the unknown hashes and should close this issue.

https://github.com/hyprwm/Hyprland/releases/tag/v0.52.1

[vaxerski]

yup.