https://bugs.kde.org/show_bug.cgi?id=506054
--- Comment #7 from Gabriel García <[email protected]> --- (In reply to Gabriel García from comment #6) > I can confirm a related issue on Arch Linux with KDE Plasma Wayland. > > In my case, Spectacle crashes immediately when a second HDMI display (TV) is > physically connected but disabled in KDE Display Settings. > > Re-enabling the disabled display immediately fixes the issue. > > The issue affects Spectacle startup itself, not only screenshot capture. > > Crash message: > > /usr/include/c++/15.2.1/bits/stl_vector.h:1346: > Assertion '!this->empty()' failed. > > KCrash: Application 'spectacle' crashing... > zsh: IOT instruction (core dumped) spectacle > > Output of `kscreen-doctor -o` showed the second HDMI display as: > > disabled > connected > > GPU: > AMD Radeon RX 6600 > > CPU: > AMD Ryzen 7 5700X3D > > This appears related to connected-but-disabled outputs under Wayland/KScreen. > > Things already tested: > > * Resetting ~/.config/spectaclerc > * Removing ~/.config/kwinoutputconfig.json > * Restarting Plasma session > * Using spectacle -r > * Removing lib32-libva-vdpau-driver > > None fixed the issue except enabling the disabled HDMI display again. Additional observation: After enabling the TV once and later turning it off again + disabling it in Plasma Display Settings, Spectacle continued working normally. This suggests the issue may depend on HDMI hotplug/output state synchronization rather than simply having a connected-but-disabled display. The problem may involve KScreen/KWin output state caching or HDMI state transitions. -- You are receiving this mail because: You are watching all bug changes.
