Using either the 'Save New Version As' produces the error 'Unable to determine the format to save the target image with.' This happens no matter what format is explicitly selected. This leaves the user with only the option to save a new version in the current directory. No rename or relocation of the file is allowed. Reproducible: Always Steps to Reproduce: 1. Open image for editing 2. Edit image 3. Select File /Save New Version /Save new version as 4. Accept defaults. Or rename. Or change save as type. Or change path. 5. Select Save. Actual Results: Error box, file not saved. Expected Results: Navigating to a new folder, changing the name, or changing the file type should be successful. Digikam 3.40 Windows 7 x64
Dave, This file still valid using last digiKam 4.2.0 ? Gilles Caulier
New digiKam 4.11.0 is available : https://www.digikam.org/node/740 Can you reproduce the problem with this release ? Gilles Caulier
Unfortunately, I can't test it. This spring I managed to convert my wife to Linux, so I don't have a Windows install to try it on. I'd hate to close this without testing it. If I can get Windows installed somewhere I'll test it, but it won't be anytime soon. For that I apologize. If you want to close the bug I'll understand.
note : 4.11.0 installer will be ready in few days...
digiKam 4.11.0 Windows installer is available for download : http://download.kde.org/stable/digikam/digiKam-installer-4.11.0-win32.exe.mirrorlist
digiKam 4.12.0 is out : https://www.digikam.org/node/741 We need a fresh feedback using this release please... Thanks in advance. Gilles Caulier
With next digiKam 5.0.0, we will provide a fully cross-compiled version Windows under Linux where a lots of problems have been fixed. https://www.flickr.com/photos/digikam/27033685570/in/dateposted-public/ The Windows installer is available here to test : https://drive.google.com/open?id=0B7yq-xFihT0_SzhxVzF1RDhPbFE Gilles Caulier
I'm going to move this to Closed/unmaintained as this references a much older version than is currently available. I'm doing so because no one else has chimed in to report this, and I no longer have a Windows installation upon which to test to see if this is still an issue or not.