SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Select PSD files 2. Click "export to google photos 3. OBSERVED RESULT It fails with "an error occured, continue?" prompt EXPECTED RESULT They should be converted to JPEG (I guesss) and uploaded to selected album SOFTWARE/OS VERSIONS Windows: Windows 11 22000.708 macOS: Linux/KDE Plasma: current openSUSE Tumbleweed Digikam and Plasma (should be latest) (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION I have installed openSUSE Tumbleweed to a seperate partition and tried the same action. Surprisingly it worked. Same Digikam version, slightly older (1 version behind I guess) Firefox default browser. I can provide an example PSD file if needed.
Hi, Because it miss certain a Qt image IO plugin to process PSD under Windows. This one is used by Google webservice plugin to convert PSD to JPEG before to upload images. Best Gilles Caulier
I cannot reproduce the problem with my available PSD files on Windows. The error message indicates that you are trying to upload the file to a locked (not created by digiKam) album. The Google API prohibits uploaders from uploading to "foreign" albums. It doesn't look like Google will change that. We have bug reports on Google and also a bug report on digiKam. Check that the album has no locked lock icon in the list of albums in digiKam Google Photo uploader. Maik
(In reply to Maik Qualmann from comment #2) > I cannot reproduce the problem with my available PSD files on Windows. The > error message indicates that you are trying to upload the file to a locked > (not created by digiKam) album. The Google API prohibits uploaders from > uploading to "foreign" albums. It doesn't look like Google will change that. > We have bug reports on Google and also a bug report on digiKam. Check that > the album has no locked lock icon in the list of albums in digiKam Google > Photo uploader. > > Maik I am aware of "locked album" issue and I made sure I am not uploading to any album with lock sign on left. Here is one of the files to test, it is saved with "maximize compatibility" setting enabled under current Photoshop. No copyright of course. https://drive.google.com/file/d/19i1hqCAuqzthJmEZSoSJGDz8UfROJcAS/view?usp=sharing
The link to the PSD file is not public, I submitted an access request via Google Drive. Maik
(In reply to Maik Qualmann from comment #4) > The link to the PSD file is not public, I submitted an access request via > Google Drive. > > Maik Hello Maik Absolutely sorry for that, Google has "enhanced" things again. Here is the fixed link https://drive.google.com/file/d/19i1hqCAuqzthJmEZSoSJGDz8UfROJcAS/view?usp=sharing
Thanks for the sample PSD file. Yes, loading the image fails on Windows. The QImage Loader only returns that the image cannot be loaded. So the problem is related to the KImageFormat plugins. Difficult to say what is the problem with this PSD file and what is missing when compiling the KImageFormat plugins on Windows. My other test PSD files even have layers and load on Windows. Maik
This is dependent on the KImageFormatPlugins version. We are currently on KF-5.92 in the Windows bundle. There were many improvements on KF-5.93. In our MSVC build of digiKam with KF-5.95, the PSD image is displayed without any problems. Maik
A new 7.7.0 pre-release installer for Windows is available here : https://files.kde.org/digikam/ It's based on KF5 5.95 and this must solve your problem. Please test and report Gilles Caulier
The corresponding sample PSD image can now be loaded with digiKam-7.7.0. Maik
(In reply to caulier.gilles from comment #8) > A new 7.7.0 pre-release installer for Windows is available here : > > https://files.kde.org/digikam/ > > It's based on KF5 5.95 and this must solve your problem. > > Please test and report > > Gilles Caulier Hello, Thank you. It is all fine now, I tested other images too and also made a "test" album to be sure. It is fixed.