Bug 462767 - Press "New Screen Copy" on Spectacle window crashes Spectacle
Summary: Press "New Screen Copy" on Spectacle window crashes Spectacle
Status: RESOLVED FIXED
Alias: None
Product: Spectacle
Classification: Applications
Component: General (other bugs)
Version First Reported In: 21.12.3
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: Boudhayan Gupta
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-12-08 05:12 UTC by Hubert Kaschulke
Modified: 2023-01-03 20:41 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In: 23.04
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Hubert Kaschulke 2022-12-08 05:12:49 UTC
STEPS TO REPRODUCE
1. Press Print-Button on your keyboard or execute Spectacle program in your menu to start Spectacle
2. Spectacle window opens
3. Press the button "New Screen Copy" (in my German version: "Neues Bildschirmfoto aufnehmen") on Spectacle window
4. Spectacle window disappears; process remains
5. Press Print-Button on your keyboard again
6. Spectacle window opens
7. Instead of "New Screen Copy" the button now shows "Cancel" (in my German version: "Abbrechen")
8. Press button "Cancel" on Spectacle window
9. Button text changes to "New Screen Copy" (in my German version: "Neues Bildschirmfoto aufnehmen")
10. Pressing this button starts at 3. again

OBSERVED RESULT
s. above

EXPECTED RESULT
Press button "New Screen Copy" (in my German version: "Neues Bildschirmfoto aufnehmen") should make a new screen copy. Spectacle window should not disappear.

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma:  
(available in About System)
KDE Plasma Version: 5.24.4
KDE Frameworks Version: 5.90.0
Qt Version: 5.15.2

ADDITIONAL INFORMATION
openSUSE Leap 15.4
Comment 1 Nate Graham 2023-01-03 20:41:17 UTC
Spectacle has been rewritten for the upcoming 23.04 release, the the version you're using is quite old and out of support. So it's likely that the issue doesn't happen anymore or is different in the new version. I can't reproduce it there, so it seems like it has indeed been fixed.