Bug 176972 - Using create "Date-based sub-albums" makes import fail
Summary: Using create "Date-based sub-albums" makes import fail
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Import-Albums (show other bugs)
Version: 0.10.0
Platform: Mandriva RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-12-05 14:04 UTC by Jean-Marc Temmos
Modified: 2018-09-02 15:18 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In: 0.10.0


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jean-Marc Temmos 2008-12-05 14:04:16 UTC
I still have the problem with 0.10.0beta5 and kde 4.1.3 (mandriva 2009).
I also have the 1TB display pb for cards of 2Gb (see below).

Deleting the digikam4.db is not an acceptable solution for me (I do not want to lose all info).


+++ This bug was initially created as a clone of Bug #171953 +++

Version:           0.10.0-beta3 (using KDE 4.1.1)
OS:                Linux
Installed from:    Fedora RPMs

In the past, I have successfully used the option to create sub-albums based on date (ISO-date) when importing images from my memory card (through the internal card reader in my laptop).

This feature stopped working in version 0.10.0-beta2 (I think), and is still not working in 0.10.0-beta3. 

If the option to create sub-albums based on date is active, the import process fails with an error message saying "Failed to find album for path '/my/full/album/path'". I have tried to create a new album database, but that doesn't help. If I turn off "Date-based sub-albums" and choose the very same album, the import succeeds.

(By the way - the size of my cards as reported in parenthesis in "Import"/"USB Storage devices" and "Card readers" are both "1 TB", although the actual size in both cases is 2 GB)
Comment 1 Marcel Wiesweg 2008-12-05 19:41:10 UTC
The size display issue is fixed I think in beta6.
The failure to create albums is as well reported in 175322.

*** This bug has been marked as a duplicate of bug 175322 ***