I was trying to do the screenshot of window (fileselector dialog related with Bluetooth) and after clicking by cross cursor into window (fileselector) Spectacle window disappeared. The process (Spectacle) still was working (in background) - I checked on the list of processes I reproduced situation twice. With the same result :(. Looks like basic function doesn't work. This is a bit annoying :/. Option "Window Under Cursor" doesn't work whereas "Rectangle area" works. Seems like something has not been retested :/. Scenario: 1. Invoke fileselector dialog from Bluetooth (I choosed "Send file") 2. Run Spectacle 3. Select following option: "Area: Window Under Cursor" "Delay: On Click" "Include title bar and borders" "Capture the current pop-up only" and press button "Take a New Screenshoot" 4. Click (cross cursor) in window (fileselector) which you want to capture Actual Result: Spectacle window disappears. Process still working in background. Nothing more happen. Expected result. Screenshoot has been done. After click I get back Spectacle window and I'm able to save it or copy to clipboard. My system: Antergos (up-do-date) with kernel: 4.11.3-1-ARCH Plasma-5.10.1 KF-5.34 Qt-5.9.0 To display Plasma uses: "The xcb windowing system"
This seems to be related to the feature "Capture the current pop-up only". I can confirm this bug still exists in Plasma 5.10.5. I'm running KDE neon 5.10.5 with KDE frameworks 5.37.0 and Qt 5.9.1.
Thanks for the report. The problem is unrelated to what is being captured. However, there's simple workaround: Turn off compositing with Shift+Alt+F12. *** This bug has been marked as a duplicate of bug 374864 ***
Plasma 5.12, KF-5.42, KDE Applications 17.12.2 Problem still persists. Spectacle window disappears. Option doesn't work. Thanks for workaround. In my opinion is not much useful. I don't want to remember every time to turn off Plasma effects in every moment when I want to make screen shot.
We hear you, but note that closing this bug as a duplicate only means that there's a different bug tracking the same problem, not that the other bug has been solved already.