Bug 508488 - "Remember last used capture mode" setting is broken
Summary: "Remember last used capture mode" setting is broken
Status: CONFIRMED
Alias: None
Product: Spectacle
Classification: Applications
Component: General (other bugs)
Version First Reported In: 6.4.4
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Noah Davis
URL:
Keywords: regression
Depends on:
Blocks:
 
Reported: 2025-08-19 19:50 UTC by PQCraft
Modified: 2025-10-14 10:20 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 PQCraft 2025-08-19 19:50:02 UTC
SUMMARY
No matter what I do, I cannot get Spectacle to use the last used capture mode. I have "When launching Spectacle" set to "Use last-used capture mode" and "Press screenshot key to" set to "Take a new Screenshot".

STEPS TO REPRODUCE
1. Press prt sc
2. Spectacle opens in rectangle selection mode
3. Press 'New Screenshot' and select 'Active Window'
4. Spectacle takes a screenshot of the active window
5. Press prt sc (it does not matter if you copy or save the screenshot or if you close Spectacle)

OBSERVED RESULT
Spectacle opens in rectangular selection mode instead of active window

EXPECTED RESULT
Spectacle should take a screenshot of the active window again because that is the last used mode

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Arch Linux with plasma-desktop 6.4.4-1
KDE Plasma Version: 6.4.4
KDE Frameworks Version: 6.17.0
Qt Version: 6.9.1

ADDITIONAL INFORMATION
This may be a regression as I think I remember it working fine before, but I have no proof and am not sure if I am remembering correctly. If this is a regression, I also do not know which version of Spectacle this started happening in.
Comment 1 Nate Graham 2025-08-19 19:56:14 UTC
I can reproduce the issue and confirm it's a regression. Likely introduced by the fancy new "open in rectangular region mode" feature.
Comment 2 reonuyt 2025-10-14 10:20:00 UTC
I can confirm, having the same issue here. I'm 100% sure the setting used to work fine some time ago.