[Digikam-devel] [Bug 236730] Collection path is interpreted differently

[Aditya Bhatt]

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





--- Comment #1 from Aditya Bhatt <adityabhatt1991 gmail com>  2010-05-07 19:16:05 ---
You might want to upgrade to digiKam 1.2.0, that is the newest stable
version.

On Fri, May 7, 2010 at 10:15 PM, dotCOMmie <bugs at dotcommie.net> wrote:

> https://bugs.kde.org/show_bug.cgi?id=236730
>
>           Summary: Collection path is interpreted differently
>           Product: digikam
>           Version: unspecified
>          Platform: Debian testing
>        OS/Version: Linux
>            Status: UNCONFIRMED
>          Severity: normal
>          Priority: NOR
>         Component: general
>        AssignedTo: digikam-devel at kde.org
>        ReportedBy: bugs at dotcommie.net
>
>
> Version:           2:1.1.0-1 (using KDE 4.3.4)
> OS:                Linux
> Installed from:    Debian testing/unstable Packages
>
> I last fired up digikam last month and it worked fine then. Today I start
> digikam and it complains that it cannot find my collection in
> "/media/Pictures"
> this is weird as I have always used "~/media/Pictures" as my collection.
> Not
> much has changed in the interrim, I did do a few safe-upgrades through
> debian
> but logs don't show any changes for digikam but some libraries have been
> updated.
>
> Removing this broken collection and re-adding the valid path resolves this
> warning but as a result a lot of meta-data is lost. Not an acceptable work
> around.
>
> Taking a look at the digikam4.db the "specificPath" column in the
> AlbumRoots
> path is set to "/media/Pictures" and not to "/home/USER/media/Pictures."
> Comparing this entry in the DB to a backup copy of the database from before
> this issue was encountered reveals that it has not changed! It appears that
> somehow the interpretation of the specificPath has changed in a way could
> possibly loose a collection. Work around is opening the database and
> changing
> this field as the option to do this in digikam is not presented.
>
> --
> Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
> ------- You are receiving this mail because: -------
> You are the assignee for the bug.
> _______________________________________________
> Digikam-devel mailing list
> Digikam-devel at kde.org
> https://mail.kde.org/mailman/listinfo/digikam-devel
>

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