imgbrd-grabber
imgbrd-grabber copied to clipboard
"No path could be generated for filename" using %md5%.%ext%
Bug description
When I try to download any set of images - either from Get All or Get Selected - I immediately get an error when starting the download: "An error occurred saving the image. Please solve the issue before resuming the download." The images don't download. if I skip or resume, the error recurs I've set the folder to a local hard disk on my machine that has more than enough space and am using the %md5%.%ext% name.
Steps to reproduce
- Search for any tag on Danbooru or Gelbooru - in this case, f-14_tomcat
- Click on Get All
- Click on Downloads tab
- Right-click on the download in question -> click Download
- Error occurs
Expected behavior
Either the download begins and runs or an error message is provided for me to troubleshoot.
Context
- Provide your
main.log
file to see if any obvious error occurred: available at https://anonfiles.com/O1f0maSdyd/main_log - Providing your
settings.ini
file will greatly help maintainers reproduce your problem if it may be caused by your configuration: available at https://anonfiles.com/cagdm5S3y6/settings_ini - If the bug occurred during a download, make sure to provide said download as an
.igl
file that Grabber can generate by clicking theSave
button of theDownloads
tab: available at https://anonfiles.com/8bg4m3S8yf/f14_igl
Note that both main.log
and settings.ini
files can be found in C:/Users/%USERNAME%/AppData/Local/Bionus/Grabber
in Windows, and in the installation directory on Linux.
Screenshots
If applicable, add screenshots to help explain your problem.
System information
- OS: Windows 11
- Grabber version: 7.10.1 x64
Additional context
Add any other context about the bug report here.
I also had this issue today and i fixed it by editing settings.ini and fixing the 2 paths that were there.
They had a double \ in the path, like for ex: "D:\Pics\folder". Changing them to "D:\Pics\folder" allowed me to start downloading without any error.
same here for windows, checked and it was NOT a backslash issue, and the disk is half empty. Thinking there is something about file path parsing that caused this