Hi Vladimir,

On Thu Nov 19, 2026 at 10:32 AM CET, Vladimir K wrote:
> Package: hyprland-guiutils
> Version: 0.2.2-1~bpo13+1
> Severity: normal
>
> Dear Maintainer, hyprland-dialog segfaults at any interaction attempt
>
> hyprland-dialog[123011]: segfault at 0 ip 0000000000000000 sp 
> 00007ffd1153e868 error 14 likely on CPU 3 (core 3, socket 0)
> Code: Unable to access opcode bytes at 0xffffffffffffffd6.
> hyprland-dialog[123087]: segfault at 0 ip 0000000000000000 sp 
> 00007ffe13149088 error 14 likely on CPU 4 (core 0, socket 0)
> Code: Unable to access opcode bytes at 0xffffffffffffffd6.
> hyprland-dialog[123162]: segfault at 0 ip 0000000000000000 sp 
> 00007ffda80a1fe8 error 14 likely on CPU 3 (core 3, socket 0)
> Code: Unable to access opcode bytes at 0xffffffffffffffd6.
> hyprland-dialog[123241]: segfault at 0 ip 0000000000000000 sp 
> 00007ffea683b3d8 error 14 likely on CPU 5 (core 1, socket 0)
> Code: Unable to access opcode bytes at 0xffffffffffffffd6.
> hyprland-dialog[123310]: segfault at 0 ip 0000000000000000 sp 
> 00007ffe3a336458 error 14 likely on CPU 5 (core 1, socket 0)
> Code: Unable to access opcode bytes at 0xffffffffffffffd6.
> hyprland-dialog[123452]: segfault at 0 ip 0000000000000000 sp 
> 00007ffcc65daad8 error 14 likely on CPU 2 (core 2, socket 0)
> Code: Unable to access opcode bytes at 0xffffffffffffffd6.
>
> BTW, are any newer backports no longer viable for trixie?
We are currently in the transition of the latest upstream released
libraries into testing. After that I will look into backporting them
ASAP. This should fix the segfaults caused by ABI mismatches.

Best,
-- 
Carl

Attachment: signature.asc
Description: PGP signature

Reply via email to