[digikam] [Bug 345391] New: digikam does not find the album when there is a bind mount

[alphsteiner]

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

            Bug ID: 345391
           Summary: digikam does not find the album when there is a bind
                    mount
           Product: digikam
           Version: 4.8.0
          Platform: Fedora RPMs
                OS: Linux
            Status: UNCONFIRMED
          Severity: critical
          Priority: NOR
         Component: general
          Assignee: [hidden email]
          Reporter: [hidden email]

Here the problematic configuration:
 - the album is stored in the home directory, say ~/Photos;
 - /home is a standalone partition;
 - another directory of the home (say ~/Shared) is bind mounted in order to be
accessed by others. The command used is 'mount --bind ~/Shared /work/Share1'
 - /work is also a standalone partition.

With this configuration, digikam does not find the album when started and shows
nothing. Worst, after removing the bind mount and restarting digikam, it shows
the photos but *all the data are lost* (titles, legends, labels, etc...). We
can guess that something is wrong since it takes a while to start, like when it
sees a directory for the first time.


Reproducible: Always



Expected Results:  
The album should be found in every situation, and maybe a backup done when it
is not found, otherwise you lost everything.

--
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=345391

Gilles Caulier <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[hidden email]
          Component|general                     |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

[C Doe]

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

C Doe <[hidden email]> changed:

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

--- Comment #1 from C Doe <[hidden email]> ---
I can confirm this bug.  I am experiencing the same problem after setting up a
bind mount.

--
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

[Maik Qualmann]

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

Maik Qualmann <[hidden email]> changed:

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

--- Comment #2 from Maik Qualmann <[hidden email]> ---
I played a little with bind mount and can not reproduce this issue. Which album
directories were added in digiKam? Following the example above ~/Photos and
~/Shared. Right?

Maik

--
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

[C Doe]

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

--- Comment #3 from C Doe <[hidden email]> ---
In my configuration, my digikam root album is the root of my user home
directory, ~.  The bind connects a subdirectory under my home directory,
say ~/foo, to a location on another partition, /var/lib/foobar.  Then it
is remounted read-only.  (Actually, I'm using lvm, so they are lvm
partitions, not physical partitions.)

/etc/fstab:
/home/cdoe/foo /var/lib/foobar none bind       0    0

/etc/rc.local:
mount -o remount,ro /var/lib/foobar

$> mount
/home/cdoe/foo on /var/lib/foobar type none (ro,bind)

On 04/07/2015 03:56 PM, Maik Qualmann wrote:

> https://bugs.kde.org/show_bug.cgi?id=345391
>
> Maik Qualmann <[hidden email]> changed:
>
>            What    |Removed                     |Added
> ----------------------------------------------------------------------------
>                  CC|                            |[hidden email]
>
> --- Comment #2 from Maik Qualmann <[hidden email]> ---
> I played a little with bind mount and can not reproduce this issue. Which album
> directories were added in digiKam? Following the example above ~/Photos and
> ~/Shared. Right?
>
> Maik
>

--
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

[C Doe]

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

--- Comment #4 from C Doe <[hidden email]> ---
...Digikam then magically decides that my Digikam root album is no
longer ~, but instead is /var/lib/foobar/cdoe (which does not exist).

--
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

[C Doe]

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

--- Comment #5 from C Doe <[hidden email]> ---
Maybe it would be helpful if the original poster, alphsteiner, could
check to see if he sees the same behavior:  that Digikam changes the
location of the Digikam root album.  I don't think he mentioned it.  It
can be found under the Settings menu:  Settings --> Configure digiKam.
Then select "Collections" in the left-hand selection pane.

Digikam changes mine from /home/cdoe to /var/lib/foobar/cdoe.

Alphsteiner:  What directory is shown for your 'Local Collections', and
what SHOULD BE your directory shown for your 'Local Collections'??

--
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

[C Doe]

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

--- Comment #6 from C Doe <[hidden email]> ---
BTW, I'm using a different version of Digikam than the OP.  I'm using
3.5.0, which is the version in the Ubuntu Trusty repo.  But I'm using a
more recent version of sqlite3 (3.8.6), because of a problem with
Digikam and the Ubuntu Trusty version of sqlite3 (3.8.2 ??).

--
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

[alphsteiner]

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

--- Comment #7 from [hidden email] ---
> What directory is shown for your 'Local Collections', and what SHOULD BE your directory shown for your 'Local Collections'??

Let me backup the database first before I try....
It is the same as you: the 'Local collection' became the mountpoint of the bind
mount.
It is back the the correct directory when rewoving the bind mount.

--
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

[alphsteiner]

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

--- Comment #8 from [hidden email] ---
I have tried to simplify the problem:
 - the normal photo directory is ~/Photos
 - run the commands:
         mkdir ~/A ~/Z
         mount --bind /home/alphonse/A /home/alphonse/Z
Then the local directory becomes '/home/alphonse/Z/alphonse/Photos'

--
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

[alphsteiner]

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

--- Comment #9 from [hidden email] ---
So, it looks like:
 - digikam tries to resolve /dev/mapper/home+alphonse/Photos
 - mount shows that /dev/mapper/home has two mountpoints, /home &
/home/alphonse/Z
 - digikam is pecking the wrong one.
Is that correct?

--
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

[Maik Qualmann]

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

--- Comment #10 from Maik Qualmann <[hidden email]> ---
Yes, I can reproduce the issue from Comment 8...

Maik

--
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

[Maik Qualmann]

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

--- Comment #11 from Maik Qualmann <[hidden email]> ---
(In reply to alphsteiner from comment #9)
>  - mount shows that /dev/mapper/home has two mountpoints, /home & /home/alphonse/Z
>  - digikam is pecking the wrong one.

Yes, a device has after a bind mount now two mountpoints with the same UUID.
DigiKam get from the Solid API only the wrong mountpoint. At the moment it
looks to me like a bug in Solid from.

Maik

--
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=345391

Gilles Caulier <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Product|digikam                     |kde
            Version|4.8.0                       |unspecified
           Assignee|[hidden email]       |[hidden email]
          Component|setup                       |general

--- Comment #12 from Gilles Caulier <[hidden email]> ---
Thanks Maik for your investigations.

I forward this entry to Solid component.

Gilles

--
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