Created attachment 131030 [details]
screenshot of configuration
Spectacle is configured to
a) Capture a Rectangular Selection upon hotkey press.
b) auto-save the rectangular selection to a predefined location.
c) copy the image to the clipboard.
The previous version of Spectacle worked as expected.
STEPS TO REPRODUCE
1. Configure Spectacle as described above.
2. Press hotkey.
3. Browse autosave location and witness no new file has been saved.
Rectangular Selection is copied to the clipboard, but the image is not saved to the default location.
Rectangular Selection is copied to the clipboard AND the Rectangular Selection is saved to default location.
Linux/KDE Plasma: Linux 5.8.1 / Plasma 5.19.4
(available in About System)
KDE Plasma Version: 5.19.4
KDE Frameworks Version: 5.73.0
Qt Version: 5.15.0
I love KDE! 😊
Same here. Steps to reproduce:
spectacle -n -b -r --output /dev/shm/screenshot.png
Thre should be screenshot in clipboard and on disk. There is only in clipboard.
I confirm this bug as well. It was working properly in earlier versions. Now, when I do this, only clipboard is saved, file on disk does not exist.
But if I launch spectacle manually after clicking the shortcut button, then a file is automatically created but which spans all my monitors.
Created attachment 131619 [details]
output of 'strace spectacle -abno test.png'
Can confirm, The '-o' / '--output' option appears to do nothing in the current version of Spectacle (20.08.1).
In case it helps, I've attached the output of 'strace spectacle -abno test.png'.
Still occurs in the most current version of Spectacle (20.11.70), compiled using kdesrc-build.
Fixed with MR 24:
Git commit 1e7b22b8c60575d4a12c267db818f8a15f17d500 by Antonio Prcela.
Committed on 06/10/2020 at 18:30.
Pushed by ngraham into branch 'master'.
Respect settings and cli parameters
Separate 'if' for doCopyToClipboard() and doSave(), since one can have both active. Adjusted the corresponding notifications.
Related: bug 422148
M +14 -6 src/SpectacleCore.cpp
M +1 -0 src/SpectacleCore.h
*** Bug 428113 has been marked as a duplicate of this bug. ***
*** Bug 429618 has been marked as a duplicate of this bug. ***