Bug 489128

Summary:	spectacle create useless subfolder
Product:	[Applications] Spectacle	Reporter:	Cherkah <cherkaba>
Component:	General	Assignee:	Noah Davis <noahadvs>
Status:	RESOLVED NOT A BUG
Severity:	normal	CC:	kde
Priority:	NOR
Version First Reported In:	24.05.1
Target Milestone:	---
Platform:	Arch Linux
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Cherkah 2024-06-24 17:55:30 UTC

***
If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org

If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***

SUMMARY
my settings in spectacle, asks it to put the screenshot to à specific location.
but for each spectacle session(opening/closing), spectacle creats numbered folder named as 'screenshot [XX]' and inside of it an other numbered folder. 
then i can access to my screenshots

STEPS TO REPRODUCE
1. create some screenshot with spectacle
2. observe 2 sub-folder level creation before use them
 

OBSERVED RESULT


EXPECTED RESULT
the screenshot location should respect the settings

SOFTWARE/OS VERSIONS
Operating System: EndeavourOS 
KDE Plasma Version: 6.1.0
KDE Frameworks Version: 6.3.0
Qt Version: 6.7.2
Kernel Version: 6.9.6-arch1-1 (64-bit)
Graphics Platform: Wayland

ADDITIONAL INFORMATION

Comment 1 Noah Davis 2024-06-24 18:39:35 UTC

What are your "Image Saving" settings? Open spectacle and click the "Configure..." button to see the settings dialog.

Comment 2 Cherkah 2024-06-24 19:57:04 UTC

>  What are your "Image Saving" settings? 

/home/GRASD/Images/Copies_d'écran/

what will spectal create?
/home/GRASD/Images/Copies_d'écran/24/06/

Comment 3 Cherkah 2024-06-24 20:00:53 UTC

(In reply to Noah Davis from comment #1)
> What are your "Image Saving" settings? Open spectacle and click the
> "Configure..." button to see the settings dialog.

sorry, ma bad

my file man setting was:  <dd>/<MM>/<yy>_<h>h<mm>
and not <dd>.<MM>.<yy>_<h>h<mm>

you can close this bug.

regards