[Digikam-devel] [Bug 216502] New: import errors are not reported

[Marc Finet]

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

           Summary: import errors are not reported
           Product: digikam
           Version: 0.10.0
          Platform: Gentoo Packages
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: general
        AssignedTo: digikam-devel at kde.org
        ReportedBy: mdreadlock at gmail.com


Version:           0.10.0 (using KDE 4.3.3)
Compiler:          x86_64-pc-linux-gnu-gcc (Gentoo 4.3.4 p1.0, pie-10.1.5) 4.3. 
OS:                Linux
Installed from:    Gentoo Packages

I used the import (Ixus 55 but it doesn't matter i think) with filename rename
and because i switched version I used 'ISO'. Unfortunately, my filesystem where
images are stored is FAT32 and filename with ':' is forbidden on such FS. I saw
that transfer failed but didn't find any hint about problem that occurred.
I had to strace digikam, that gave me the clue:
stat("/mnt/images/voyages/2009-irlande/2009-07-31/photo-2009-07-31T18:13:02.JPG",
0x4f5e4b8) = -1 ENOENT (No such file or directory)
lstat("/mnt/images/voyages/2009-irlande/2009-07-31/photo-2009-07-31T18:13:02.JPG",
0x7ffff83b6090) = -1 ENOENT (No such file or directory)
rename("/mnt/images/voyages/2009-irlande/2009-07-31/.digikam-camera-tmp1-2734IMG_0992.JPG",
"/mnt/images/voyages/2009-irlande/2009-07-31/photo-2009-07-31T18:13:02.JPG") =
-1 EINVAL (Invalid argument)
unlink("/mnt/images/voyages/2009-irlande/2009-07-31/.digikam-camera-tmp1-2734IMG_0992.JPG")
= 0

It's ok for me (i switched to Advanced and choose format suitable for this FD)
but i think that a 'normal user' would not strace digikam to find what the
problem is.

The idea behind this bug report is to show/explain user errors that occurred
during import (could be interesting to test with more common failures, such as
FS full, but it might occur before rename). I could take a look at code if my
case is just related to rename(), that is, lacking a report, a catch or
something like this and all the architecture is ready (i.e. opening window,
filename list, and error type...).

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