[Digikam-devel] [Bug 221887] New: Digikam leaves behind a cifsxxxx file for each image imported from a camera on CIFS mounted volume

[Michael Liddle]

https://bugs.kde.org/show_bug.cgi?id=221887

           Summary: Digikam leaves behind a cifsxxxx file for each image
                    imported from a camera on CIFS mounted volume
           Product: digikam
           Version: 1.0.0
          Platform: unspecified
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: general
        AssignedTo: digikam-devel at kde.org
        ReportedBy: michael at liddle.net.nz


Version:           1.0.0 (using 4.3.4 (KDE 4.3.4) "release 2", KDE:43 /
openSUSE_11.0)
Compiler:          gcc
OS:                Linux (i686) release 2.6.25.20-0.5-default

Steps to reproduce:

1) Mount a CIFS volume, and set it up as an image repository in DK
2) Connect a camera
3) Transfer images to that volume using the camera import wizard
4) Inspect the file-system from the command-line

As well as the imported images, there is then a cifsxxxx file for each
transferred image (but not movie files, based on file counts). For those that
were automatically rotated (via EXIF info), this file will actually be a copy
of the _unrotated_ image. For all others the the cifsxxxx file will be empty (0
bytes).

That is the import proceeds correctly, and the images are transferred fine. But
the existence of cifsxxxx files suggests that in someway DK is not cleaning up
after itself properly (perhaps not closing files properly or something?)

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.