SUMMARY When exporting image to jpg, from menu or button, does not create file. STEPS TO REPRODUCE 1. File / export 2. filename: test.jpg (name does not matter) 3. save 4. settings for saving image file: default 5. ok - no file anywhere 6. if you use exist file, it will overwrite OBSERVED RESULT no file EXPECTED RESULT nice to have file saved :-) SOFTWARE/OS VERSIONS DISTRIB_ID=Ubuntu DISTRIB_RELEASE=20.04 DISTRIB_CODENAME=focal DISTRIB_DESCRIPTION="Ubuntu 20.04.2 LTS" NAME="Ubuntu" VERSION="20.04.2 LTS (Focal Fossa)" KDE Frameworks 5.79.0 Qt 5.15.2 (built against 5.15.2) The xcb windowing system ADDITIONAL INFORMATION no problem with version 6.x
Cannot be reproduced here with pre-release digiKam-7.3.0. Please post the debug output in the terminal with activated debug variable as described here: https://www.digikam.org/contribute/ Maik
Tested with logging and following show up. when startig digikam from commandline, bug does not exists! When started from desktop-icon, bug exists.
The behavior that it works from the command line and not from the icon, I have no explanation for that. Does Ubuntu start programs in a sandbox? Or do you use the Flatpak? Maik
No idea how to use sandbox or flatbak?
If I see it correctly, there is no native digiKam version for Ubuntu. A snap package will be installed with sandbox. There is probably the possibility to install the application in "--classic" mode for access to the entire system. In my honest opinion, use a Linux distribution that provides a current native digiKam version. Maik
*** This bug has been marked as a duplicate of bug 439587 ***
*** Bug 439587 has been marked as a duplicate of this bug. ***
Created attachment 139923 [details] installation source
yep, snapcraft.io seems to be source for os distribution package
I removed package from "Ubuntu Software" and installed again from command line with apt install digikam - got version 6.4.0 and there is no problem. Then is run 7.3.0 appimage, which now started ok and both problems are gone. Have to say, I'm quite confusing, how installation packages are handled, but it's dikikam case :-)
Ubuntu have been always a problem. It's the best Linux distro so far... Gilles Caulier
*** Bug 440197 has been marked as a duplicate of this bug. ***
Same happened with newer ubuntu. picture seems to export ok, but no files anywhere. I have tryed with snap-pacgae and with apt-package - same behaviour. Current Digikam version on my instalation is 7.8.0 DISTRIB_ID=Ubuntu DISTRIB_RELEASE=22.04 DISTRIB_CODENAME=jammy DISTRIB_DESCRIPTION="Ubuntu 22.04.1 LTS" PRETTY_NAME="Ubuntu 22.04.1 LTS" NAME="Ubuntu" VERSION_ID="22.04" VERSION="22.04.1 LTS (Jammy Jellyfish)" VERSION_CODENAME=jammy ID=ubuntu ID_LIKE=debian
This is not a digiKam problem. Snap uses a sandbox, so there is no access outside of the home directory. Ubuntu Snap packages are useless. Reports the problem to Ubuntu and forces them to provide native digiKam packages. Maik
*** Bug 464276 has been marked as a duplicate of this bug. ***
@webpalaute@ajl.fi digiKam 8.0.0 is out. This problem still reproducible with this release ? Best regards Gilles Caulier
Tested with digiKam-8.0.0-x86-64.appimage No difference. Works same way. No exported files anywhere
It's not reproducible at all here under Ubuntu 22.04 and later release. Do you use versioning feature from Image Editor ? Look in digiKam/Setup/Editor/Versioning page for details. Gilles Caulier
It's really hard to imagine that no new file is created with the AppImage when exporting. Please set the Qt debug variable in the terminal: export QT_LOGGING_RULES="digikam*=true" Then start the AppImage in the terminal, export a JPG and post the output in the terminal. Maik
Created attachment 159413 [details] versioning feature I'm not sure, what settings do you mean with "versioning feature". I haven't changed anything and here attached settings page
Created attachment 159414 [details] console log as file Here is all logging from running appimage on console, when export QT_LOGGING_RULES="digikam*=true" has been set. After starting I found out, that some export of image editor works! If I try again, it does not save file. Even restart of image editor does not help. I restarted whole digikam, no help - cannot export anymore.
@webpalaute@ajl.fi I cannot reproduce this problem at all. Here i use Kubuntu 22.04 and 23.04 What's about this file using current 8.2.0 AppImage Linux bundle ? It's reproducible ? https://files.kde.org/digikam/ Thanks in advance Gilles Caulier
Umm, this is the first I am seeing of this. I am now maintaining snaps. I am working on a new release and will make sure this is in order...
Same with version 8.2.0 appimage. I attached video, where you can see, files not saved.
Sorry - cannot attach - too big
Which protocol did you use to integrate your Buffalo NAS? Maik
I'm using samba. I have tried also on local disk and behaving is the same.
Hi Scarlett, There are plenty of rights access problem when digiKam from Snap is used.
Scarlett, all Snap problem can be wrapped around using the AppImage bundle. For ex this one : https://bugs.kde.org/show_bug.cgi?id=453905 The problem is the same with the FlatPak version which have also many rights access limitations. Gilles Caulier
@webpalaute: When I look at the log from Comment 21, the file "denleu.jpg" was definitely created, the item scanner found it and a thumbnail was created, it must exist. When creating "denleu2.jpg" you seem to have aborted the process and exited digiKam. Maik
As you noticed, sometimes exporting is successful. I made a new logging with 8.2.0. before start on terminal: `export QT_LOGGING_RULES="digikam*=true"` What I have made: - open image thru samba with buffalo - export with name ajl1.jpg = ok - export with name ajl2.jpg = ok - export with name ajl3.jpg = no file anywhere - export with name ajl3.jpg = no file anywhere (note same same) - export with name ajl4.jpg = no file anywhere - exit from image-editor and digikam Attachment follows
Created attachment 162252 [details] digikam log latest log today from appimage 8.2.0
(In reply to caulier.gilles from comment #29) > Scarlett, > > all Snap problem can be wrapped around using the AppImage bundle. For ex > this one : > > https://bugs.kde.org/show_bug.cgi?id=453905 > > The problem is the same with the FlatPak version which have also many rights > access limitations. > > Gilles Caulier Ok, thank you! I will follow the appimage and get the snap all fixed up.
Scarlett, Note that the official digiKam AppImage is not one build with Craft. We written own bash/Cmake script build on XUBuntu 18.04. All is here : https://invent.kde.org/graphics/digikam/-/tree/master/project/bundles/appimage?ref_type=heads The stable use Qt 5.15.11 + KF5 5.111. The unstable not yet fully finalized is now ported to Qt 6.5.3 + KF6 (master). Gilles
(In reply to caulier.gilles from comment #34) > Scarlett, > > Note that the official digiKam AppImage is not one build with Craft. We > written own bash/Cmake script build on XUBuntu 18.04. All is here : > > https://invent.kde.org/graphics/digikam/-/tree/master/project/bundles/ > appimage?ref_type=heads > > The stable use Qt 5.15.11 + KF5 5.111. > The unstable not yet fully finalized is now ported to Qt 6.5.3 + KF6 > (master). > > Gilles Wonderful thank you, no worries, I am not ready with Qt6 in snaps either.
*** Bug 477467 has been marked as a duplicate of this bug. ***
*** Bug 478038 has been marked as a duplicate of this bug. ***