Version: 1.2.0 (using KDE 4.4.3) OS: Linux Installed from: openSUSE RPMs digikam looks for a collection on the wrong disk partition under following circumstances: I've my pictures stored on /home/path/to/collection. /home is a separate partition (sda3) So far, so good, everything works fine. Now I mount my second hard disk (partition sdb3) to /data. digikam now looks for the collection in /data/path/to/collection !!! (which does not exist of course) It's impossible to add the collection under /home in the settings dialogue, I get an error message dialogue. I checked the digikamrc file, it contains the correct path to the collection. Now I reformatted the second harddisk and have just one big partition (sdb1) which I mount to /data. There's no problem in this case. The problem seems that digikam confuses the partitions sda3 with sdb3.
Note that the collection is stored in the database, not in the settings file any more. The partition will be referenced by its UUID. It doesn't care at all about mount path or device name. That means partitions can normally not be mixed up, unless something special went wrong or Solid/HAL provided wrong information. But now, you have changed your setup, so we probably cannot investigate this any further?
Unfortunately, yes, I changed my setup, otherwise I couldn't have been sure that it really had to do with the disk partions. Good for me on the other hand, because the problem is gone now ;-) During my investigation I also deleted the digikam data base, so digikam couldn't remember some old stuff. But here's some more info about the hard disks. They are of absolutely identical type and they had exactly the same partitioning. I even mirrored some partions. I don't know if that could have confused my system to generate the same uuids. Now they are all different at any rate. /Gerhard
Ok, I bet they had the same UUID!