#1143172 Package: hyprland,Version: 0.56.0+ds-1,,hyprland: regression in 0.56.0+ds-1, crashes on startup with SIGABRT on minimal configuration

Package:
hyprland
Source:
hyprland
Description:
Dynamic tiling Wayland compositor
Submitter:
ALEKSANDR
Date:
2026-08-14 06:35:02 UTC
Severity:
normal
#1143172#5
Date:
2026-07-31 08:59:16 UTC
From:
To:
Dear Maintainer,

After upgrading hyprland from 0.55.4+ds-2+b1 to 0.56.0+ds-1 on Debian
unstable
(Sid), Hyprland consistently aborts during startup with SIGABRT, even when
started with a minimal configuration.

The problem appeared immediately after the package upgrade:

2026-07-29 17:25:33
hyprland:amd64 0.55.4+ds-2+b1 -> 0.56.0+ds-1

Hardware
========

CPU: AMD Ryzen (Cezanne)
GPU: AMD Radeon Vega (integrated, amdgpu)

Software
========

Distribution:
  Debian unstable (Sid)

Packages:

hyprland            0.56.0+ds-1
libaquamarine11     0.12.1-1
libhyprgraphics4    0.5.1-2+b1
libhyprutils12      0.13.1-2
libhyprlang2        0.6.8-4+b1
libhyprcursor0      0.1.13-2

Problem
=======

Hyprland aborts immediately during startup.

The crash is fully reproducible with:

     Hyprland --config /tmp/min.conf

where /tmp/min.conf contains only a minimal valid configuration.

Troubleshooting already performed
=================================

The following possibilities have been excluded:

  * minimal configuration
  * empty exec-once section
  * no waybar
  * no mako
  * xdg-desktop-portal stopped
  * xdg-desktop-portal-hyprland stopped
  * previous Linux kernel
  * AQ_NO_ATOMIC=1
  * same Mesa stack
  * same Hypr libraries

Crash backtrace
===============

The relevant frames are:

     Desktop::View::CWindow::getFullWindowBoundingBox()
     Desktop::View::CWLSurface::getSurfaceBoxGlobal()
     CBackgroundEffectProtocol::bindManager()

Hyprland terminates with SIGABRT.

Regression test
===============

I downgraded ONLY the package "hyprland" using snapshot.debian.org:

     0.56.0+ds-1  ->  0.55.4+ds-2+b1

No Hypr libraries were downgraded because they are identical in both
repository snapshots.

After downgrading only hyprland:

     Hyprland --config /tmp/min.conf

starts successfully every time.

Therefore the regression appears to be introduced by hyprland 0.56.0+ds-1.

Regression confirmed by A/B testing.

Only the hyprland binary changed:

0.55.4+ds-2+b1 -> starts successfully.
0.56.0+ds-1    -> aborts with SIGABRT.

All dependent Hypr libraries remained at identical versions:

libaquamarine11 0.12.1-1
libhyprgraphics4 0.5.1-2+b1
libhyprutils12 0.13.1-2
libhyprlang2 0.6.8-4+b1
libhyprcursor0 0.1.13-2

Expected result
===============

Hyprland starts normally.

Actual result
=============

Hyprland aborts during startup with SIGABRT.

I can provide the complete Hyprland crash report if required.

#1143172#10
Date:
2026-07-31 19:01:30 UTC
From:
To:
hyprland 0.56.0 requires hyprutils >= 0.14.0. sid has 0.13.1, so the
binary in sid is built against a version upstream declares insufficient.

Upstream d30bb9555639564d2b3eb83f5c7c615ffe6f1af4, released in v0.56.1,
a one-line CMakeLists change raising the minimum from 0.13.1 to 0.14.0:

    build: update hyprutils dependency to 0.14.0 (#15518)
    Crashes at startup with hyprutils < 0.14.0.

The hyprutils fix (41fb809, "memory: fix virtual inheritance casts") is
in header-only templates, so the build-time version decides, not the
installed runtime library.

Verified: rebuilt 0.56.0+ds-1 with no source changes, only
build-depending on libhyprutils-dev 0.14.0-1 from experimental. Crash
gone.

Fix: d/control libhyprutils-dev (>= 0.14.0), plus upstream d30bb955 as a
patch so a build against 0.13.1 fails at configure rather than producing
a crashing binary. Blocked until hyprutils 0.14.0 migrates from
experimental (libhyprutils13). 0.55.4+ds-2+b1 is unaffected.

#1143172#15
Date:
2026-07-31 20:04:05 UTC
From:
To:
Dear Maintainers,

I am writing to confirm this issue.

Hardware: AMD Ryzen 8840U (Hawk Point) with Ryzen 780M Graphics (integrated)

The crash log is very similar to the one attached by the original reporter
as are the symptoms which occurred immediately after upgrading.

As in the initial report, downgrading from 0.56.0+ds-1 to
0.55.4+ds-2+b restored
normal operation immediately with no other changes.

I am happy to provide any logs if that would be helpful.

#1143172#20
Date:
2026-08-01 11:24:19 UTC
From:
To:
Hi,

thanks for the reports, we already have a confirmed transition request[1] to update
hyprutils and aquamarine to their latest upstream.
New version should be in unstable pretty soon.

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1142671

Best,

#1143172#25
Date:
2026-08-08 06:20:23 UTC
From:
To:
Hi,

can you confirm that this issue no longer exists after upgrading to
hyprland 0.56.2+ds-1?

If the issue still appears, please share
hyprland --version and hyprctl systeminfo.

Best,

#1143172#30
Date:
2026-08-14 06:33:43 UTC
From:
To:
Closing as hyprland has been rebuild against latests libs.
User feedback indicates that issue has been resolved.

Best,