Bug 450504 - No longer possible to capture and copy to clipboard *without* saving to a file
Summary: No longer possible to capture and copy to clipboard *without* saving to a file
Status: RESOLVED WORKSFORME
Alias: None
Product: Spectacle
Classification: Applications
Component: General (other bugs)
Version First Reported In: 21.12.2
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Boudhayan Gupta
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-02-18 07:25 UTC by Frederick Zhang
Modified: 2022-05-02 08:14 UTC (History)
2 users (show)

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

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Frederick Zhang 2022-02-18 07:25:45 UTC 
SUMMARY
No longer possible to capture and copy to clipboard *without* saving to a file, unless I clear out Configure -> Save -> Save Location (but setting it to empty string breaks Save button).

These days I paste screenshots directly into browser/IM a lot more often than saving them as files, so being able to only copying to clipboard is extremely handy.


STEPS TO REPRODUCE
1. Run `spectacle -bcri`
2. Take a screenshot

OBSERVED RESULT
Screenshot is copied to clipboard and saved to file.

EXPECTED RESULT
Screenshot is copied to clipboard only.

SOFTWARE/OS VERSIONS
Operating System: Arch Linux
KDE Plasma Version: 5.24.1
KDE Frameworks Version: 5.91.0
Qt Version: 5.15.2
Kernel Version: 5.16.10-arch1-1 (64-bit)
Graphics Platform: X11

ADDITIONAL INFORMATION
Comment 1 Salvatore 2022-04-07 06:02:48 UTC 
I have the same problem

I often use the shortcut "Capture rectangular region", after capturing the image the notification comes out that it has been copied to the clipboard, but then I go to the folder and it was saved without me doing anything

Spectacle version: 21.12.3-1
Operating System: Arch Linux
KDE Plasma Version: 5.24.4
KDE Frameworks Version: 5.92.0
Qt Version: 5.15.3
Comment 2 Frederick Zhang 2022-05-02 08:14:03 UTC 
This appears to have been fixed in 22.04.0.