[Digikam-devel] [Bug 243696] New: digikam didn't detect my local collection anymore after replacing internal harddisk

[Martin Steigerwald]

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

           Summary: digikam didn't detect my local collection anymore
                    after replacing internal harddisk
           Product: digikam
           Version: 1.2.0
          Platform: Debian unstable
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: NOR
         Component: Database
        AssignedTo: digikam-devel at kde.org
        ReportedBy: Martin at Lichtvoll.de


Version:           1.2.0 (using KDE 4.4.4) 
OS:                Linux

I replaced the internal harddisk of my ThinkPad T42 by a bigger one. Today I
just wanted to import some photos. On start Digikam said it didn't find the
media that stores my internal collection with some UUID anymore.



Reproducible: Didn't try

Steps to Reproduce:
- Create a collection on a local filesystem
- Quit Digikam
- Copy it so somewhere else
- Recreate the filesystem so that it has a different UUID
- Copy the collection back
- Start Digikam again

Actual Results:  
Digikam said my local collection cannot be found since the storage medium with
some UUID is not available anymore. First I thought this was my external
collection thus I marked it as removable medium. But then Digikam asked me
about my external collection - it didn't got that an eSATA disk is a removable
medium which has to do with Solid, Hal, Linux Kernel - here I also said it was
on a removable medium.

Then I wanted to fix this quickly cause I was absolutely not in the mode to
fiddle with software problems: I removed the internal collection and created a
new one, but then Digikam scans in every single image again although they are
in the database.

The current behavior induces data loss due to user mistakes - like the one I
did: Deleting and recreating the collection. I have a backup, but its still
annoying. Especially as I have no idea on how to handle that situation *other*
than to delete the collection and recreate it again since Digikam just didn't
offer me any sensible option.

Expected Results:  
Digikam does not try to be smarter than me. It should not do any UUID checking 
for a collection stored on my *internal* harddisk. If I put a new bigger
internal harddisk into my ThinkPad T42 and make the collection available at the
same path again, Digikam just should *just* use it and *not* bother me about
it.

It might be wise to do UUID checking it for external ones, but even then
Digikam should offer a "I moved my collection somewhere else" and/or "I changed
media or filesystem, please update UUID" option. I can file enhancement
requests for these.

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