Hyprland crashes after monitors are disconnected

[jaypikay]

Hyprland received signal 11(SEGV)
Version: 29e2e59fdbab8ed2cc23a20e3c6043d5decb5cdc
Tag: v0.48.1
Date: Fri Mar 28 16:16:07 2025
Flags:

When no displays are connected Hyprland crashes. I do use an KVM without EDID emulation, and switching the input the monitors are disconnected. After a while Hyprland will crash.

hyprlandCrashReport2083.txt

[vaxerski]

can you get a debug stacktrace? https://wiki.hyprland.org/Crashes-and-Bugs/#obtaining-a-debug-stacktrace

[jaypikay]

Hi, as by now I wasn't able to reproduce the crash with the debug flag enabled, also with and without debug flag the crashes do not happen. When in the past, it just took seconds after disconnecting, now the screens stay all black and the system is unrespsonive.

[vaxerski]

that's not great. Are you on git or 0.48.1 with the debug build?

[jaypikay]

Yes, I have used this as the version to test. (used the commit id provided by the Arch package, but it matches with the tagged one).
Even when it is not crashing right now, the fact that the screens won't turn back on again still occurs. Should I open a different Bug report, so if others have this issue are able to find it more easily?

[matsondawson]

I've had hyprland crash ever since I installed it when the monitor goes to sleep, or is turned off.
I figured out today if I create a headless monitor it wont crash anymore.
Of course I end up with a workspace I don't want, but I can handle that.

e.g.

exec-once=hyprctl output create headless Virtual
monitor=DP-2,preferred,auto,1
monitor=FALLBACK,3840x1600@60,auto,1

workspace = 1,monitor:DP-2,default:true
workspace = 2,monitor:DP-2,default:true
workspace = 3,monitor:DP-2,default:true
workspace = 4,monitor:DP-2,default:true
workspace = 5,monitor:DP-2,default:true

[kchr]

I have the same issue when disconnecting from my docking station, which has two external monitors attached to it.

The backtrace from the crash report seems to show the same stack frames as the OP posted (full crash report attached):

Backtrace:
        # | Hyprland(_Z12getBacktracev+0x61) [0x563f838f75b1]
                getBacktrace()
                ??:?
        #1 | Hyprland(_ZN14NCrashReporter18createAndSaveCrashEi+0x129f) [0x563f8384afef]
                NCrashReporter::createAndSaveCrash(int)
                ??:?
        #2 | Hyprland(+0x2464b8) [0x563f837b84b8]
                CCompositor::getMonitorFromCursor()
                ??:?
        #3 | /usr/lib/libc.so.6(+0x3e540) [0x7fcc95c3e540]
                ??
                ??:0
        #4 | [0x563fb20c6410]
                ??
                ??:0

I am running hyprland v0.51.1.

Attachments

hyprlandCrashReport152294.txt
hyprctl_systeminfo.txt
coredump.txt

[edqx]

I have a similar issue, Hyprland is crashing when I switch my monitor signal back to HDMI, which Hyprland is running on.

Here's the last lines of my crash report:

[CRITICAL] [AQ] Cannot open backend: no allocator available
[CRITICAL] m_pAqBackend couldn't start! This usually means aquamarine could not find a GPU or encountered some issues. Make sure you're running either on a tty or on a Wayland session, NOT an X11 one.
[CRITICAL] Critical error thrown: CBackend::create() failed!

hyprlandCrashReport5367.txt

[edqx]

I think it's actually more related to drivers being attached/detached from VFIO. I have a virtual machine setup with GPU passthrough. When I quit my VM, the GPU gets assigned back to the host PC, and Hyprland appears to crash in that case.

[edqx]

This was fixed in a recent update, sometime in the last month. I'm unsure what commit would've fixed it.

[G-Rowell]

Hi all & vaxerski (thank you for your work on Hyprland)

I can +1 this issue,

I get a crash on Firefox when disconnecting from my dock (which has 2 monitors + more)

OS: Arch
Browser: Firefox
DE: Wayland + Hyprland
Dock is a Dell brand

It reliably (every time) crashes Firefox on disconnecting the dock, but not on connecting the dock.

It has been occuring for 2 or so weeks for me, including after running sudo pacman -Syu; reboot

I'll try to get some logs & more info, but I am at reporting this from work

Thanks all

[jaypikay]

Is it only Firefox (FF) that crashes? Than it is a FF problem, it does not like having Windows on non present monitors. I also have noticed this, and think it is a pure FF problem. It sounds like your Hyprland continues running just fine, except for FF?

[kchr]

This is most likely another issue, as discussed here: #11529

A fix has been merged into main with #11916, so you could try compiling the latest source or wait for the next release to see if it solves your problem (I have the same issue as well with Firefox, along with the problem outline in this discussion).

[G-Rowell]

Thanks both, good points,

hopefully a future release solves it.
Appreciated

[oliwoli]

Also can +1 this. For me I've observed chrome and blender crashing when I turn my monitor off.
But for example Zen Browser (which is Firefox) is fine.

Edit: Interestingly for chrome, it seems if I just disable any extension and then re-enable it, chrome won't crash. But after a reboot, it crashes again. Blender seems more stable, haven't been able to reproduce the crash consistently.

Update: I noticed for me the crash actually happens after turning the monitor back on. I noticed this / verified it by playing some audio in chrome and turning the monitor off (audio still plays), then turning it back on (chrome is dead).

---

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.5
 hyprlang 0.6.3
 hyprutils 0.10.0
 hyprcursor 0.1.13
 hyprgraphics 0.2.0


no flags were set

-- package versions: 
google-chrome 142.0.7444.59-1
blender 17:4.5.3-8
libnvidia-container 1.17.9-1
linux-firmware-nvidia 20251021-1
nvidia-container-toolkit 1.17.9-1
nvidia-lts 1:580.95.05-6
nvidia-utils 580.95.05-1
opencl-nvidia 580.95.05-1

OS: Arch Linux x86_64
Kernel: 6.12.56-1-lts
CPU: Intel i7-6700K (8) @ 4.200GHz
GPU: NVIDIA GeForce GTX 1070

[ronilaukkarinen]

For me Hyprland crashes every time with std::out_of_range when physical monitor disconnects (when I press the power off button in my screen). This has been happening for a week or so.

Environment:

• Hyprland version: v0.52.0-19-gcb47eb1d1 (commit cb47eb1, built Nov 16, 2025)
• OS: Arch Linux (kernel 6.17.8-arch1-1)
• GPU: NVIDIA GeForce RTX 3070 (GA104)
• Monitor: DP-1 (DisplayPort)
• Plugins: hyprbars (Vaxry) 1.0

Reproduction steps:

1. Have Hyprland running with a physical monitor connected via DisplayPort (DP-1)
2. Turn off the physical monitor (power button)
3. Hyprland crashes immediately with std::out_of_range exception
4. User is forcibly logged out and loses session

Issue:
The crash occurs consistently and reproducibly when the physical monitor disconnects. The issue is in the ExtWorkspace protocol handling when onMonitorCreated is called during monitor disconnect/reconnect events.

Crash location:

• File: src/protocols/ExtWorkspace.cpp:302
• Function: CExtWorkspaceManagerResource::onMonitorCreated
• Error: std::out_of_range exception thrown

Full crash report:

--------------------------------------------
Hyprland Crash Report
--------------------------------------------
Oops

Hyprland received signal 6(ABRT)
Version: cb47eb1d11bbac1ebab8f9cd7a5f96a475eaab28
Tag: v0.52.0-19-gcb47eb1d1
Date: Sun Nov 16 14:23:45 2025
Flags:

Hyprland seems to be running with plugins. This crash might not be Hyprland's fault.
Plugins:
hyprbars (Vaxry) 1.0

System info:
System name: Linux
Node name: infinity
Release: 6.17.8-arch1-1
Version: #1 SMP PREEMPT_DYNAMIC Fri, 14 Nov 2025 06:54:20 +0000

GPU:
06:00.0 VGA compatible controller [0300]: NVIDIA Corporation GA104 [GeForce RTX 3070]
[10de:2484] (rev a1) (prog-if 00 [VGA controller])


os-release:
NAME="Arch Linux"
PRETTY_NAME="Arch Linux"
ID=arch
BUILD_ID=rolling
ANSI_COLOR="38;2;23;147;209"
HOME_URL="https://archlinux.org/"
DOCUMENTATION_URL="https://wiki.archlinux.org/"
SUPPORT_URL="https://bbs.archlinux.org/"
BUG_REPORT_URL="https://gitlab.archlinux.org/groups/archlinux/-/issues"
PRIVACY_POLICY_URL="https://terms.archlinux.org/docs/privacy-policy/"
LOGO=archlinux-logo

Libraries:
Hyprgraphics: built against 0.3.0, system has 0.3.0
Hyprutils: built against 0.10.2, system has 0.10.2
Hyprcursor: built against 0.1.13, system has 0.1.13
Hyprlang: built against 0.6.5, system has 0.6.5
Aquamarine: built against 0.9.5, system has 0.9.5

Backtrace:
# | Hyprland(_Z12getBacktracev+0x61) [0x5652cad42121]
        getBacktrace()
        /usr/src/debug/hyprland-git/hyprland/src/helpers/MiscFunctions.cpp:755
#1 | Hyprland(_ZN14NCrashReporter18createAndSaveCrashEi+0xcd6) [0x5652cac6dfe6]
        std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char>
>::_Alloc_hider::_Alloc_hider(char*, std::allocator<char> const&)
        /usr/include/c++/15.2.1/bits/basic_string.h:205 (discriminator 1)
#2 | Hyprland(+0x2b0c02) [0x5652cabcfc02]
        handleUnrecoverableSignal(int)
        /usr/src/debug/hyprland-git/hyprland/src/Compositor.cpp:115
#3 | /usr/lib/libc.so.6(+0x3e4d0) [0x7f5545e3e4d0]
        ??
        ??:0
#4 | /usr/lib/libc.so.6(+0x9890c) [0x7f5545e9890c]
        ??
        ??:0
#5 | /usr/lib/libc.so.6(gsignal+0x20) [0x7f5545e3e3a0]
        ??
        ??:0
#6 | /usr/lib/libc.so.6(abort+0x26) [0x7f5545e2557a]
        ??
        ??:0
#7 | /usr/lib/libstdc++.so.6(+0x97bf6) [0x7f5546297bf6]
        ??
        ??:0
#8 | /usr/lib/libstdc++.so.6(+0xb1eba) [0x7f55462b1eba]
        ??
        ??:0
#9 | /usr/lib/libstdc++.so.6(_ZSt10unexpectedv+0) [0x7f55462975d9]
        ??
        ??:0
#1 | /usr/lib/libstdc++.so.6(+0xb2176) [0x7f55462b2176]
        ??
        ??:0
#11 | /usr/lib/libstdc++.so.6(_ZSt20__throw_out_of_rangePKc+0x48) [0x7f554629bdb5]
        ??
        ??:0
#12 | Hyprland(+0x1972b4) [0x5652caab62b4]
        Hyprutils::Memory::CUniquePointer<CExtWorkspaceManagerV1>::get() const
        /usr/include/hyprutils/memory/UniquePtr.hpp:92
#13 | Hyprland(_ZN28CExtWorkspaceManagerResource16onMonitorCreatedERKN9Hyprutils6Memo
ry14CSharedPointerI8CMonitorEE+0x160) [0x5652caf21120]
        Hyprutils::Memory::CUniquePointer<CExtWorkspaceGroupResource>
Hyprutils::Memory::makeUnique<CExtWorkspaceGroupResource,
Hyprutils::Memory::CWeakPointer<CExtWorkspaceManagerResource>&,
Hyprutils::Memory::CUniquePointer<CExtWorkspaceGroupHandleV1>,
Hyprutils::Memory::CSharedPointer<CMonitor>
const&>(Hyprutils::Memory::CWeakPointer<CExtWorkspaceManagerResource>&,
Hyprutils::Memory::CUniquePointer<CExtWorkspaceGroupHandleV1>&&,
Hyprutils::Memory::CSharedPointer<CMonitor> const&)
        /usr/include/hyprutils/memory/UniquePtr.hpp:137 (discriminator 4)
#14 | Hyprland(+0x602974) [0x5652caf21974]
        std::_Function_handler<void (void*, SCallbackInfo&, std::any),
CExtWorkspaceProtocol::CExtWorkspaceProtocol(wl_interface const*, int const&,
std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >
const&)::{lambda(void*, SCallbackInfo&, std::any)#2}>::_M_invoke(std::_Any_data
const&, void*&&, SCallbackInfo&, std::any&&)
        /usr/src/debug/hyprland-git/hyprland/src/protocols/ExtWorkspace.cpp:302
(discriminator 7)
#15 | Hyprland(_ZN18CHookSystemManager4emitEPSt6vectorI14SCallbackFNPtrSaIS1_EER13SCa
llbackInfoSt3any+0x137) [0x5652cadc1697]
        std::any::has_value() const
        /usr/include/c++/15.2.1/any:334
#16 | Hyprland(_ZN8CMonitor9onConnectEb+0x1e65) [0x5652cad6a975]
        std::any::has_value() const
        /usr/include/c++/15.2.1/any:334
#17 | Hyprland(_ZN11CCompositor16enterUnsafeStateEv+0x188) [0x5652cabde978]
        Hyprutils::Memory::CWeakPointer<CMonitor>::lock() const
        /usr/include/hyprutils/memory/WeakPtr.hpp:132
#18 | Hyprland(_ZN8CMonitor12onDisconnectEb+0xa85) [0x5652cad64025]
        CMonitor::onDisconnect(bool)
        /usr/src/debug/hyprland-git/hyprland/src/helpers/Monitor.cpp:415
#19 | Hyprland(+0x44c47d) [0x5652cad6b47d]
        std::_Function_handler<void (),
CMonitor::onConnect(bool)::{lambda()#6}>::_M_invoke(std::_Any_data const&)
        /usr/src/debug/hyprland-git/hyprland/src/helpers/Monitor.cpp:151 (discriminator 1)
#2 | /usr/lib/libhyprutils.so.9(_ZN9Hyprutils6Signal15CSignalListener12emitInternalEP
v+0x2d) [0x7f5546c9061d]
        ??
        ??:0
#21 |
/usr/lib/libhyprutils.so.9(_ZN9Hyprutils6Signal11CSignalBase12emitInternalEPv+0x19a)
[0x7f5546c9087a]
        ??
        ??:0
#22 | /usr/lib/libaquamarine.so.8(_ZN10Aquamarine13SDRMConnector10disconnectEv+0x44)
[0x7f5546d8b714]
        ??
        ??:0
#23 |
/usr/lib/libaquamarine.so.8(_ZN10Aquamarine11CDRMBackend14recheckOutputsEv+0x1ef)
[0x7f5546d86b1f]
        ??
        ??:0
#24 | /usr/lib/libhyprutils.so.9(_ZN9Hyprutils6Signal15CSignalListener12emitInternalE
Pv+0x2d) [0x7f5546c9061d]
        ??
        ??:0
#25 |
/usr/lib/libhyprutils.so.9(_ZN9Hyprutils6Signal11CSignalBase12emitInternalEPv+0x19a)
[0x7f5546c9087a]
        ??
        ??:0
#26 |
/usr/lib/libaquamarine.so.8(_ZN10Aquamarine8CSession18dispatchUdevEventsEv+0x5c2)
[0x7f5546d685a2]
        ??
        ??:0
#27 | Hyprland(+0x53375a) [0x5652cae5275a]
        aquamarineFDWrite(int, unsigned int, void*)
        /usr/src/debug/hyprland-git/hyprland/src/managers/eventLoop/EventLoopManager.cpp:51
#28 | /usr/lib/libwayland-server.so.0(wl_event_loop_dispatch+0x1d2) [0x7f5546b64182]
        ??
        ??:0
#29 | /usr/lib/libwayland-server.so.0(wl_display_run+0x37) [0x7f5546b66297]
        ??
        ??:0
#3 | Hyprland(_ZN17CEventLoopManager9enterLoopEv+0x291) [0x5652cae55381]
        std::__new_allocator<char>::allocate(unsigned long, void const*)
        /usr/include/c++/15.2.1/bits/new_allocator.h:151
#31 | Hyprland(main+0x1234) [0x5652cab46614]
        Hyprutils::Memory::CUniquePointer<CCompositor>::get() const
        /usr/include/hyprutils/memory/UniquePtr.hpp:92
#32 | /usr/lib/libc.so.6(+0x27635) [0x7f5545e27635]
        ??
        ??:0
#33 | /usr/lib/libc.so.6(__libc_start_main+0x89) [0x7f5545e276e9]
        ??
        ??:0
#34 | Hyprland(_start+0x25) [0x5652cabcf0a5]
        _start
        ??:?

Log tail:
[LOG] [AQ] drm: Connector DP-1 disconnected
[LOG] Destroy called for monitor DP-1
[LOG] [hookSystem] New hook event registered: preMonitorRemoved
[LOG] onDisconnect called for DP-1
[LOG] [CGammaControl] Destroying gamma control for DP-1
[LOG] Monitor DP-1 -> destroyed all render data
[LOG] Disconnecting Monitor DP-1 was on workspace 1
[LOG] Removed monitor DP-1!
[WARN] Unplugged last monitor, entering an unsafe state. Good luck my friend.
[LOG] Entering unsafe state

Impact:
This causes complete session loss every time the monitor is turned off, forcing users to keep their monitors on 24/7 or risk losing all open applications and work.

Note:
I've seen mentions in other discussions that this might be related to the ExtWorkspace protocol handling. The crash consistently occurs at the same location in ExtWorkspace.cpp:302.