https://bugs.kde.org/show_bug.cgi?id=525343
--- Comment #5 from Michał <[email protected]> --- Ha! I've figured out some extra circumstances that cause this, after combining what you two said with the clue I discovered at the end of OP. The original repro steps indeed won't just work in isolation on a freshly logged-in system. SCENARIO #1 1. Hit keys for "Capture Active Window" (Alt+PrtSc) 2. The screenshot gets taken and a notification is shown that it was saved. The Spectacle window didn't open up, expectedly. 3. Now original repro follows: hit PrtSc "accidentally" 4. Press ESC 5. The Spectacle window now suddenly pops up, despite not being opened at all before SCENARIO #2 1. Do something that causes the Spectacle window to be opened and then have it either minimized or inactive (say you took a screenshot some time before, for example by opening the screenshot overlay, selecting some area and pressing Accept; and then just forgot about the Spectacle window in the background) 2. Now original repro follows: hit PrtSc "accidentally" 3. Press ESC 4. The Spectacle window now suddenly pops up. But interestingly, it's visible that original minimized window closes up and this new window gets immediately re-opened, rather than having this minimized window be brought up, and on a different wrong screen too (different from when it was before and from where screenshot was taken and from where the cursor resides, seemingly). SCENARIO #3 I've also noticed, directly related to those shenanigans, that hitting "Capture Active Window" (Alt+PrtSc) while Spectacle window is minimized, causes Spectacle's minimized window to close (fine), the screenshot is then taken as expected, but the notification that it was saved to file doesn't get shown at all. Only taking the second screenshot by hitting the keys once again afterwards, will produce the expected notification. It seems that the notification missing is the only problem in this scenario and that the preference to also copy the screenshot to the clipboard was respected, which is an appreciated improvement that must have happened somewhat recently. That makes it scenario #3 of unexpected behavior, since I realized I've also ran into this chain of events and had missing notification, but never paid enough close attention to figure out the circumstances. Hence I labeled this section as such for readability. I hope this will help :) -- You are receiving this mail because: You are watching all bug changes.
