Version: (using KDE 4.4.3) Installed from: openSUSE RPMs I can't copy images from a local collection to a CIFS-mounted network collection. This problem has been present quite some time. I store my images on a network harddisk mounted this way: //192.168.178.1/WD-10Harddisk/ on /media/net-harddisk type cifs (rw,mand) This is an external, NTFS-formatted harddisk connected to a so-called "Fritz!Box" router. The Fritz!Box runs an embedded Linux and therefore uses Samba in order to provide network access to this drive. Any other program can tranparently read/write to this share, however, this might be connected, (only) Dolphin complains after every write that the permissions could not be set (all selected files are copied, however). Digikam interrupts after the first picture to be copied and says "the process for protocol digikams:/ has been terminated unexpectedly" (rough translation from German). The first selected picture has been copied (if you selected "move", the original picture has, however, not yet been deleted). No further pictures will be copied afterwards.
Which digiKam version you use ? Please test with last 1.2.0 release Gilles Caulier
Created attachment 47845 [details] Error message (in German) The problem still persists with 1.2.0 (using openSUSE packages). The screenshot shows the KDE progress dialog and Digikam's error message. The error message occurs after each single picture to be copied if severals photos have been selected. If the photos are supposed to be moved (not copied) to the CIFS-share, the original pic has not yet been deleted when this message occurs, however, the pic already exists at the destination drawer. Digikam's database is not located on the CIFS-share, but on the local harddisk.
Please check for error messages in your ~/.xsession-errors file while these errors are produced.
OK, I e.g. try to copy the picture "DSC_0003.JPG" from a local folder to the remote folder mounted below "/media/network", the album (i.e. remote drawer) is "Meine Fotos/test". This is what happens in .xsession: kdeinit4: preparing to launch /usr/lib64/kde4/kio_digikamalbums.so ...then several entries like this: digikam(8321)/digikam (core) Digikam::CollectionScanner::scanAlbum: Folder does not exist or is not readable: "/media/network/Meine Fotos/test/DSC_0003.JPG" ...then kdeinit4: preparing to launch /usr/lib64/kde4/kio_digikamdates.so ...then again several entries of digikam(8321)/digikam (core) Digikam::CollectionScanner::scanAlbum: Folder does not exist or is not readable: "/media/network/Meine Fotos/test/DSC_0003.JPG" ...then QWidget: Cannot create a QWidget when no GUI is being used kioslave: ####### CRASH ###### protocol = kio_digikamalbums pid = 9923 signal = 6 QSocketNotifier: Invalid socket 12 and type 'Read', disabling... kio_file(8393) FileProtocol::copy: "Couldn't preserve access and modification time for /media/network/Meine Fotos/test/DSC_0003.JPG" I have to add that Dolphin also complains about not being able to preserve file attributes when copying to the mounted network drive. However, Dolphin does not crash.
Small addition: Network paths have changed since my original bug report because I set up the system anew.
Is the remote folder added as a collection to digikam? That is, you copy by drag and drop inside digikam?
Yes, I drag and drop inside Digikam.
I now also played around with the CIFS-mount option "nobrl" which is supposed to cure problems with OpenOffice. Didn't help for Digikam. The CIFS-option "noperm" at least helped with the problem concerning the permission settings Dolphin always complained about - Dolphin works much more flawlessly now - however the Digikam problem persists.
It seems that the kioslave is crashing, seemingly because something tries to create a widget. It is a cumbersome process to get a backtrace from an ioslave, explaing here: http://techbase.kde.org/Development/Tutorials/Debugging/Debugging_IOSlaves The service name for the crashing ioslaves is probably "digikamalbums". I dont have a CIFS mount available for testing atm.
Larx, This file still valid with 2.x serie ? Gilles Caulier
As I no longer use the setup in which the problem occured,I unfortunately can no longer give any details.