SUMMARY On a three-monitor setup, using the spectacle app via the print screen button causes one screen to freeze (darkened with a bubble that says "Click and drag to make a selection."), with no screen capture UI showing up, indability to escape this function, and an error message to show up on another screen (as below). STEPS TO REPRODUCE 1. Hit Print Screen to run Spectacle's screen clipping. That's about it. OBSERVED RESULT On a three-monitor setup, using the spectacle app via the print screen button causes one screen to freeze (darkened with a bubble that says "Click and drag to make a selection.") - on that screen, the cursor can move, but no windows can be placed on the screen. Most of the time, the screen capture interface does not show up, and clicking around, hitting escape, or hitting enter results in nothing (rarely it does, seemingly at random). On another screen, an error report pops up and reads: An error occurred while taking a screenshot. KWin screenshot request failed: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. Potentially relevant information: - Method: CaptureScreen - Method specific arguments: "DP-4" Clicking OK on this popup, and then hitting print screen again, may return the screens to their base form without spectacle's alterations. EXPECTED RESULT The normal screen dimming, spectacle UI of drawing a box around the screen clipping section, and immediate return to normal display function should occur. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 42 (Kernel v. 6.15.3-200.fc42z86_64 (64-bit)) KDE Plasma Version: 6.4.1 KDE Frameworks Version: 6.15.0 Qt Version: 6.9.1 Spectacle version 1:6.4.1-1.fc42 ADDITIONAL INFORMATION Hardware Specs: AMD Ryzen 7 7800X3D 8-core processor Memory 48 giB of RAM Graphics Processor 1: AMD Radeon RX 6700 XT (discrete) Graphics Processor 2: AMD Radeon Graphics (integrated) Wayland graphics
Thanks for the bug report. This looks like bug 487802, based on the error you're seeing. Please follow the other report for updates. *** This bug has been marked as a duplicate of bug 487802 ***