Bug 425641 - Output option in background mode does not save the screenshot as file
Summary: Output option in background mode does not save the screenshot as file
Status: RESOLVED DUPLICATE of bug 424380
Alias: None
Product: Spectacle
Classification: Applications
Component: General (show other bugs)
Version: 20.08.0
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: Boudhayan Gupta
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-08-21 13:55 UTC by duchuy29092000
Modified: 2020-09-07 08:45 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Screenshot is not saved (72.33 KB, image/png)
2020-08-21 13:55 UTC, duchuy29092000 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description duchuy29092000 2020-08-21 13:55:07 UTC 
Created attachment 131076 [details]
Screenshot is not saved

SUMMARY
When I take a screenshot from command line, the image is not saved

STEPS TO REPRODUCE
1. Run command `spectacle -b -n -o test.png`
2. Check the current directory

EXPECTED RESULT
See a screenshot at the working directory.

OBSERVED RESULT
There is no such screenshot or even file with the name.  Instead, the screenshot is saved to the clipboard.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: openSUSE Tumbleweed 20200819
(available in About System)
KDE Plasma Version: 5.19.4
KDE Frameworks Version: 5.73.0
Qt Version: 5.15.0

ADDITIONAL INFORMATION

The GUI mode doesn't suffer this problem.  I still can explicitly save it in GUI mode, which I used to capture the attachment.
Comment 1 Magnus Boman 2020-08-31 13:39:43 UTC 
This appears to be a duplicate of https://bugs.kde.org/show_bug.cgi?id=424380 which is fixed in git master, but has not made it into any release.
Comment 2 duchuy29092000 2020-09-07 08:44:35 UTC 
Yes, it was a duplicate, except the image wasn't saved to ~/Pictures/, maybe because there was no such folder at the first place on my computer. I wasn't able to find that issue before.
Comment 3 duchuy29092000 2020-09-07 08:45:21 UTC 

*** This bug has been marked as a duplicate of bug 424380 ***