Bug 450002 - 'When launching Spectacle: Take full screen screenshot' is ignored when I open Spectacle while a notification generated by it is visible
Summary: 'When launching Spectacle: Take full screen screenshot' is ignored when I ope...
Status: RESOLVED FIXED
Alias: None
Product: Spectacle
Classification: Applications
Component: General (other bugs)
Version First Reported In: 22.08.2
Platform: Neon Linux
: NOR normal
Target Milestone: ---
Assignee: Boudhayan Gupta
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-02-11 11:47 UTC by Patrick Silva
Modified: 2023-11-22 14:35 UTC (History)
3 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Patrick Silva 2022-02-11 11:47:23 UTC
STEPS TO REPRODUCE
1. open Spectacle by pressing printscreen key
2. set 'Area' to 'Rectangular region'
2. check 'Quit after manual Save or Copy'
3. click on 'Configure...' button and make sure 'When launching Spectacle' is set to 'Take full screen screenshot'
4. close Spectacle
5. open Spectacle again by pressing printscreen key
6. save the screenshot (Spectacle closes and Plasma shows a notification)
7. open Spectacle again by pressing printscreen key while the notification is visible

OBSERVED RESULT
Spectacle ignores 'When launching Spectacle: Take full screen screenshot'
and activates the overlay to select a rectangular region

EXPECTED RESULT
'When launching Spectacle: Take full screen screenshot' is always respected

Operating System: KDE neon Unstable Edition
KDE Plasma Version: 5.24.80
KDE Frameworks Version: 5.91.0
Qt Version: 5.15.3
Graphics Platform: Wayland
Comment 1 Patrick Silva 2022-05-23 11:31:32 UTC
Still reproducible.

Operating System: KDE neon Unstable Edition
KDE Plasma Version: 5.25.80
KDE Frameworks Version: 5.95.0
Qt Version: 5.15.4
Graphics Platform: Wayland
Comment 2 Justin Zobel 2022-11-11 05:14:57 UTC
Confirmed on 22.08.2 on Fedora 37
Comment 3 Noah Davis 2023-11-22 14:35:25 UTC
This seems to be fixed.