Bug 225759 - jpg image size = 0 byte, when transfer occurs from my camera to my NAS
Summary: jpg image size = 0 byte, when transfer occurs from my camera to my NAS
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Import-MainView (show other bugs)
Version: 1.0.0
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-02-06 21:21 UTC by goretux
Modified: 2012-06-27 10:19 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In: 2.1.0
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description goretux 2010-02-06 21:21:17 UTC
Version:           1.0.0 (using KDE 4.3.5)
OS:                Linux
Installed from:    Ubuntu Packages

When I transfer some jpg photos from my camera (Canon Ixus 800 - PTP mode) to my NAS (Qnap TS-219P) which is mounted as a CIFS volume, the downloaded files on the NAS are unreadable. They have a size of 0 byte.
(Note that the database file is stored on a local partition.)

However, the problem doesn't happen when (avi) video files are transfered from my camera to my NAS ?!

Note that when jpg files are transfered to a local partition, there is no problem.
Comment 1 goretux 2010-05-15 15:03:35 UTC
I want to update my report as the "bug" is still present with digikam 1.2.0 (with kde 4.4.3 on Kubuntu 10.04).

Moreover, I was able to test another device which is an Iphone 3GS.
I experienced _exactly_ the same behavior (except that video files are .mov).

Note : when I download from the Iphone (or Canon Ixus) to a local store (my local HDD), then copy (within digikam) the images from that location to my NAS, there is no problem.
So it consolidate the position that the bug may live inside the "import files from devices" code.

Thanks in advance for your support. Don't hesitate to ask me more information.

Eric
Comment 2 caulier.gilles 2011-08-04 14:16:39 UTC
Can you reproduce the problem with digiKam 2.0.0 ?

Gilles Caulier
Comment 3 goretux 2011-08-10 06:28:02 UTC
The problem seems resoved. I can't reproduce the problem with digiKam 1.9.0.
(Maybe the problem was resolved before this version.)