[Digikam-devel] [Bug 175923] New: digikam uses wrong album root path/wrong disk uuid
Roland Wolters
wolters.liste at gmx.net
Sun Nov 23 18:37:58 GMT 2008
http://bugs.kde.org/show_bug.cgi?id=175923
Summary: digikam uses wrong album root path/wrong disk uuid
Product: digikam
Version: unspecified
Platform: Fedora RPMs
OS/Version: unspecified
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: general
AssignedTo: digikam-devel at kde.org
ReportedBy: wolters.liste at gmx.net
Version: (using KDE 4.1.3)
Installed from: Fedora RPMs
Digikam only shows the included albums when I have my backup disk attached -
although all paths in digikamrc and even in the digikam4.db-file are set right.
When I start Digikam without the external disk I simply get an empty digikam.
If I remove the folder in the settings and re-add it, the problem persists. I
have to remove the database file to get rid of this problem.
Background information:
My files are in /home/liquidat/Bilder/Photoalben/* (several folders). I have an
additional external usb disk with a backup of these data under
/media/BackupDisk/Backup/Bilder/Photoalben/*.
My guess:
I opened the database file and looked around, and finally found this:
sqlite> select * from AlbumRoots;
id = 1
label =
status = 0
type = 1
identifier = volumeid:?uuid=313804a2-7421-49cd-a6be-b689886a4dea
specificPath = /home/liquidat/Bilder/Photoalben
The uuid is in fact the one of my external hard disk - my local hard disk is
bound in by VolumeManagement:
$ mount
...
/dev/mapper/VolGroup00-LogVol01 on /home type jfs (rw)
...
So, first of all, how could it ever happen that the wrong uuid was ever chosen?
And how can I correct it now - a VM ususally does not has a uuid.
--
Configure bugmail: http://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
More information about the Digikam-devel
mailing list