[Bug 215486] New: collection not found in location on disk with uuid (lvm volume)

[Marcel Wiesweg]

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





--- Comment #16 from Marcel Wiesweg <marcel wiesweg gmx de>  2009-12-27 21:23:16 ---
I only see the 5f5fb... partition, no 16013... partition in the output. Look
for "StorageAccess". So it seems that Solid does not understand the disk
layout.
I dont know how to fix this.
In the dialog, maybe we can offer an option to switch to identification by
filepath, to make things work then at least.

--
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
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

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


Matthieu Pupat <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[hidden email]




--- Comment #17 from Matthieu Pupat <mpupat free fr>  2010-12-05 16:57:20 ---
I have  the same issue. I moved my pictures from a ext4 on LUKS partition to an
ext4 on LUKS on RAID1 partition.

After that move, digikam would complain about not finding the ols collections
although they are still under the same absolute path and under the same
relative path under the new partition.

Additionally when I create a new collection I have a warning message: "It is
not possible on your system to identify the storage medium of this path".

--
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
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

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


igor <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[hidden email]




--- Comment #18 from igor <igor47 moomers org>  2011-03-08 22:48:36 ---
ditto. i migrated to a new computer by copying over my  /home folder. this
obviously resulted in a different uuid for the disk. my photos are currently
inaccessible, and i'm trying to look up complicated steps to edit the sqlite db
to find them again.

pretty terrible.

--
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
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

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





--- Comment #19 from igor <igor47 moomers org>  2011-03-08 23:04:23 ---
in fact, the solution suggested here:
http://ubuntuforums.org/showthread.php?t=1192655

does not work for me on ubuntu 10.10. i've tried every uuid my system has, and
digikam still can't find my photos, which are nontheless still there in the
same path they've always been -- /home/igor47/photos

is there an interim solution while this bug is fixed that will get me my data
back?

--
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
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

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





--- Comment #20 from Matthieu Pupat <kde pupat-ghestem net>  2011-06-03 05:15:13 ---
The issues with LVM and RAID should be fixed by the fix for #273369. Not sure
if that fixes the original problem though.

--
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
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Gilles Caulier-4]

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


Gilles Caulier <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[hidden email]
            Summary|collection not found in     |collection not found in
                   |location on disk with uuid  |location on disk with UUID
                   |(lvm volume)                |(lvm volume)




--- Comment #21 from Gilles Caulier <caulier gilles gmail com>  2011-12-15 08:27:35 ---
Simon,

This file still valid using digiKam 2.4 ?

Gilles Caulier

--
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
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

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





--- Comment #22 from Simon Oosthoek <s oosthoek xs4all nl>  2011-12-15 20:39:05 ---
Hi Gilles

it's very hard to reproduce this bug on a voluntary basis ;-)

I've had some issues upgrading to 2.1 I think, but I don't remember if I
had problems or what the outcome was. (Well, the outcome is that digikam
still has pictures, but I haven't been able to spend quality time with
digikam much, lately)

As for database problems, there's now another one, every time I start
digikam (2.1 and 2.4 now) I get an error that the path to mysqld isn't
set, but I'm not using mysql, so that shouldn't matter to me.

From the comments I see there were quite some a few other people with
the same type of problems, so perhaps someone else can confirm this in a
recent release.

Cheers

Simon

--
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
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Gilles Caulier-4]

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

--- Comment #23 from Gilles Caulier <[hidden email]> ---
Do you experience this kind of problem with more recent digiKam release, as
4.2.0 ?

Gilles Caulier

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Gilles Caulier-4]

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

Gilles Caulier <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|collection not found in     |Collection not found in
                   |location on disk with UUID  |location on disk with UUID
                   |(lvm volume)                |(LVM volume)

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Gilles Caulier-4]

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

Gilles Caulier <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|Collection not found in     |SCAN : Collection not found
                   |location on disk with UUID  |in location on disk with
                   |(LVM volume)                |UUID (LVM volume)

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Gilles Caulier-4]

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

Gilles Caulier <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|SCAN : Collection not found |CORE : collection not found
                   |in location on disk with    |in location on disk with
                   |UUID (LVM volume)           |UUID (LVM volume)

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Mike]

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

Mike <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[hidden email]

--- Comment #24 from Mike <[hidden email]> ---
I experience this problem with digikam 4.2 and right now I lost my 80.000 pics
and tags it seems :-( after changing the filesystem from NTFS to ext4. The
database is in my /home directory but the image colleactions reside on a second
disk.
Now I can see the configured collections in the config-dialogue of digikam but
I can't edit them. Where is the path located ?  in the database only ?  And how
to change that ? What if I want to move to another disk ...I would run in the
same problem.

My system ist Manjaro 0.8.10 and right now I cant get access to my pics ,
although i see my tags...but no pics...;

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Mike]

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

--- Comment #25 from Mike <[hidden email]> ---
Ok I could solve the problem with the help of the sqlite browser modifying the
uuid entries in the database. Now everything is working again. HolyJesus...
pheww....

But I can't understand why that has to be done this unpracticable. That is NOT
userfriendly :-)) Just editing the path insider the config dialogue would be so
much better and doable by a "normal" user. Why rely on the UUID ?  Yeah I read
it has to do with the KDE API blabla. But for a user that is totally
impractical. The UUID is something I dont want to handle... ; I have path's and
data. And I want to change that easily..;  If I will change my drives I will
have the same problem again.. and again.. ;  Just a hint to think about in the
settings. Why not implementing a switch to let the user decide HOW to handle to
path to the collections ?   I thought LINUX is the system who does what tghe
user wants ?  ;-)

However:   thanks fo the great program... even if we have to fiddle with
it...its superb ! :-)

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Marcel Wiesweg]

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

--- Comment #26 from Marcel Wiesweg <[hidden email]> ---
Hm initially, UUID was needed to support removable media.
With hardwired disks, you can either change the UUID or the path.
If you change the mount path, the partition will be found via UUID and you dont
notice it.
If you change the UUID and keep the path, there should be a short dialog asking
you if this is still the same media etc. and all should be handled well if you
press Ok.
If you change the pah and the UUID, it cannot be expected to be handled
automatically.
If you have network shares, there will be only the mount path to work with, no
UUID here.

I cannot tell you what went wrong on your setup.

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Mike]

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

--- Comment #27 from Mike <[hidden email]> ---
Hmm.. couldnt remember correctly: it could be that I also changed the diskname
slightly. But nothing changed on the path's for the pictures. So I think it
would be very good to add the possibility to change the location of the
collection in the setup menu for the case that it could not be found. And there
are several reasons why that could happen:
- the user accidentally didnt click "yes" in the daialogue after a change of
ONE parameter ( UUID or mount path)
- the user changed several things like possibly me

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Mike]

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

--- Comment #28 from Mike <[hidden email]> ---
ups... acidentally "saved changes" while i was writing.. :-/.  
So I mean adding an edit-field in the setup of the collection-location would be
a real enhancement. Because right now you see the "old" collections and you
cant even see the location nor can you change it !   Thats not so good. Normaly
there should be the option to change the collection and/ or its location. My
opinion ;-)

Thanks for your comments Marcel and your hard work !
Mike

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Alex Merry]

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

Alex Merry <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[hidden email]

--- Comment #29 from Alex Merry <[hidden email]> ---
I just ran into an issue where, moving to a new laptop, I had a different disk
layout. Instead of having /home mounted separately, it is just a directory in
my root partition.

Because the database stored the paths relative to the mount point, I had a
collection recorded as being at /alex/Photos, so Digikam didn't give me the
option of using the new location. If went into the database, and changed it to
/home/alex/Photos, and then Digikam allowed me to say that it had just moved to
a local disk.

I think that local collections should either be stored differently (absolute
paths or relative to the database file), or the option to say where a
collection moved to should be given when it can't be found (so as not to lose
metadata).

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[bugzilla_noreply]

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

[hidden email] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|CORE : collection not found |Collection not found in
                   |in location on disk with    |location on disk with UUID
                   |UUID (LVM volume)           |(LVM volume)

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[bugzilla_noreply]

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

[hidden email] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[hidden email]

--- Comment #30 from [hidden email] ---
Simon,

Is the file still valid using digiKam 5.1.0?
Please test and provide feedback.

--
You are receiving this mail because:
You are the assignee for the bug.

[bugzilla_noreply]

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

[hidden email] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
          Component|Database                    |Database-Media

--
You are receiving this mail because:
You are the assignee for the bug.