https://bugs.kde.org/show_bug.cgi?id=401767
--- Comment #3 from kavol <ka...@seznam.cz> --- (In reply to Maik Qualmann from comment #2) > Using a UUID is not a nonsense but a standard. considering the fact that digikam is the only software that failed, I'd doubt at least the "standard" part ... for example kmail via akonadi had no problem opening ~/.Mail after the disc shuffle > How else should it be detected with removable drives, > if it is the right drive. well, I believe you answer your own question: > One possible way to solve this problem would be to create a UUID and > save it as a file in the root of the collection. - if digikam already puts some metadata into that directory, it can put a signature file into it too in addition, some distros recently started mounting removable devices as /run/media/$USER/$UUID which makes the path pretty unique without having to handle the media id separately plus there is the volume label which might be (ab)used ... or simply asking the user to identify the medium if everything else fails > What do you think what is going on when digiKam destroys the database > because it scans a wrong drive? the database should not be destroyed in any case ... what if it identifies like a right drive but it appears empty due to some other problem? however, let's go back from generic discussion about removable media to what's important here: a) a problem appeared on *non-removable* media that I need fixed (and maybe other users would appreciate not running into it to :-)) - that problem should not have happened in the first place b) I see no way how to convince digikam that it should use that path - in addition to looking into application settings, before finding out my mistake that different UUID changed than I thought, I've even tried to fiddle with sqlite like UPDATE AlbumRoots SET identifier="volumeid:?uuid=..." WHERE id=1; where I had put uuid of the / device, then I also tried if it can just get ignored if I set it to NULL, but nothing helped -- You are receiving this mail because: You are watching all bug changes.
