I am not able to delete photos stored on a NAS even though I can delete them using file browser. I am using Ubuntu 16.10 and have mounted the NAS from the fstab like this - //192.168.10.107/photo /media/photos cifs username=username,password=password,iocharset=utf8,sec=ntlm,users 0 0
When you delete a file, please post the message from the console. Maik
Created attachment 102371 [details] Screenshot of error message Screenshot of the error message I get when trying to delete. Not very informative.
No. Maik, ask you to run digiKam from a console and report all debug statements printed inside while you try to delete file. Gilles Caulier
Created attachment 102478 [details] digikam Console debug report
This might be a bit more informative.
There is no explicit error message visible from the console trace... Can you reproduce the problem using digiKam Linux AppImage bundle ? The last bundle is available at this url: https://drive.google.com/drive/folders/0BzeiVr-byqt5Y0tIRWVWelRJenM Gilles Caulier
Hi, I tried the appimage, but haven't been able to test yet. Digikam does not show any menues and it defaulted to scan my whole collection. This will take some time, but I will report back when it is done and tested. Thanks
Hi, I could not figure out why digikam could not get access to trash and I am not even quite sure which trash it wants access to. Is it trash on my NAS or laptop? If it is trash on my laptop, I am wondering if digikam knows where Ubuntus' trash is located in the file system.
(In reply to dajomu from comment #8) > Hi, > > I could not figure out why digikam could not get access to trash and I am > not even quite sure which trash it wants access to. Is it trash on my NAS or > laptop? If it is trash on my laptop, I am wondering if digikam knows where > Ubuntus' trash is located in the file system. digiKam does not access the trash of your OS. It creates its own trash - according to your log in folder /media/photos/.dtrash . When you "delete" an image and go to the trash in digiKam, are the "deleted" images listed there?
new 5.6.0 pre-release as bundle is available here : https://drive.google.com/drive/folders/0BzeiVr-byqt5Y0tIRWVWelRJenM Please check if this problem still reproducible with these versions. Thanks in advance Gilles Caulier
digiKam 5.6.0 is now released and available as bundle for Linux, MacOS and Windows. https://www.digikam.org/news/2017-06-21-5.6.0-release-announcement/ Can you check if problem still exists with this version ? Thanks in advance Gilles Caulier
Can you reproduce the dysfunction using digiKam 6.0.0 pre-release bundle available here : https://files.kde.org/digikam/
Can you reproduce the dysfunction using the last digiKam 6.0.0-beta3 just released ? https://www.digikam.org/news/2018-12-30-6.0.0-beta3_release_announcement/