One of monitors turns black when taking screenshot with spectacle

When pressing a hotkey to capture a region, or when using the UI button, in **Spectacle** on **Ubuntu 24.04** with **KDE Neon** *(manully installed)*, one of my monitors turns black. I then have to replug it in or disable-enable in the settings. There are three monitors: laptop's built-in, a Philips connected via USB-C -> HDMI *(works)* and an MSI connected via HDMI *(doesn't work)* I tried to: - unplug/disable all other screens including built-in laptop screen - remove all hotkeys and only use the capture UI button *(to diagnose potential hotkey conflicts)* - install spectacle from snap store instead of the bundled one *(doesn't work with KDE Neon)* - use shutter instead *(doesn't work on Wayland)* - use flameshot instead *(doesn't work with multiple monitors)* - reset all monitors' scale to 100% Notably: - it only happens to one particular monitor *(independent of monitor arrangement or the output it is plugged into)* - [running](https://pastebin.com/QD6dibpG) spectacle -m or capturing the "current screen" does not cause the issue, it is only region capture that does - [running](https://pastebin.com/QD6dibpG) spectacle -r also turns the monitor black - even though the screen turns black, **the output is still correct** *(the screenshot of the region is properly taken)* - after going black, the monitor is still connected *(does not show "awaiting input")* - for a split second, I can see the capturing overlay, then the screen goes black - it is not shut off, the backlight is visible, its just black - locking the computer and unlocking it does not restore the image This started happening after I switched from KDE to KDE Neon. I might've broken some dependency of spectacle in the process, but I'm not sure how to check that, and the spectacle logs have no errors. Restarting the PC after installing upgrades. Now *every restart* fixes the issue temporarily. After a restart, everything works, then after some time stops and breaks (I'm still trying to find the exact action that breaks it) Edit: Using "PixelTaken" as an alternative, the issue is also present.