[Bug 500581] Re: Add collection error message

Wed Jun 27 22:29:53 UTC 2012

Launchpad has imported 13 comments from the remote bug at
https://bugs.kde.org/show_bug.cgi?id=221155.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.

------------------------------------------------------------------------
On 2010-01-03T21:27:58+00:00 Luka Renko wrote:

Version:            (using KDE 4.3.4)
OS:                Linux
Installed from:    Ubuntu Packages

Report from Ubuntu bug:

I have 2 collections :
- ~/Images/apn
- ~/Images/apn-reflex

If I add the apn one first, then I have an error message when adding
apn-reflex : "you already added a collection which contains apn-reflex"
(my own translation), while apn-reflex is not a subfolder of apn…

If I add the second first, it works…

I have reproduced the problem with digikam 1.0.0 and it seems the
problem is that the function that checks the directory name wrongly
identify similarly named directory as duplicate collection.

Reply at: https://bugs.launchpad.net/digikam/+bug/500581/comments/4

------------------------------------------------------------------------
On 2010-01-03T21:55:13+00:00 Caulier-gilles-9 wrote:

Message error is this one ?

http://lxr.kde.org/source/extragear/graphics/digikam/utilities/setup/setupcollectionview.cpp#466

Gilles Caulier

Reply at: https://bugs.launchpad.net/digikam/+bug/500581/comments/5

------------------------------------------------------------------------
On 2010-01-03T23:05:59+00:00 Luka Renko wrote:

Created attachment 39536
screenshot of the error

No, it is the error as shown in attachment.

Reply at: https://bugs.launchpad.net/digikam/+bug/500581/comments/6

------------------------------------------------------------------------
On 2010-01-21T19:17:59+00:00 Marcel-wiesweg wrote:

rootPath = ~/Images/apn
filePath = ~/Images/apn-reflex/xyz

if (filePath.startsWith(rootPath))
{
    ...
}

That's the current code. The mistake is obvious, you already point to it above.
I want to avoid accessing the filesystem here, just compare strings.

Reply at: https://bugs.launchpad.net/digikam/+bug/500581/comments/7

------------------------------------------------------------------------
On 2010-01-21T19:23:26+00:00 Marcel-wiesweg wrote:

SVN commit 1078190 by mwiesweg:

Add extra check to compare directories

CCBUG: 221155

 M  +7 -3      collectionmanager.cpp

WebSVN link: http://websvn.kde.org/?view=rev&revision=1078190

Reply at: https://bugs.launchpad.net/digikam/+bug/500581/comments/8

------------------------------------------------------------------------
On 2010-01-21T19:24:17+00:00 Marcel-wiesweg wrote:

Luka, would you like to test?

Reply at: https://bugs.launchpad.net/digikam/+bug/500581/comments/9

------------------------------------------------------------------------
On 2010-01-26T22:27:09+00:00 Marcel-wiesweg wrote:

*** Bug 216017 has been marked as a duplicate of this bug. ***

Reply at: https://bugs.launchpad.net/digikam/+bug/500581/comments/10

------------------------------------------------------------------------
On 2010-02-04T09:52:26+00:00 Luka Renko wrote:

Marcel, I tested it now with 1.1, and the problem is not fixed. :-(

Reply at: https://bugs.launchpad.net/digikam/+bug/500581/comments/12

------------------------------------------------------------------------
On 2010-02-04T19:58:19+00:00 Marcel-wiesweg wrote:

Ok I see. It does not work when you add the two collections in one go, does it? Didn't test that case. When you close the dialog in between, it works. And at least you get now a meaningful error message ;-)
Will fix this.
Or did you test another case?

Reply at: https://bugs.launchpad.net/digikam/+bug/500581/comments/13

------------------------------------------------------------------------
On 2010-02-05T09:02:00+00:00 Luka Renko wrote:

Marcel, you are correct:
- if I add both collections in one go (same dialog) -> fail
- add first collection, close, add second connection -> OK

A side note: when adding directories of local FS (it is on dm-crypt+LVM volume), I get the following warning:
It is not possible on your system to identify the storage medium of this path. It will be added using the file path as the only identifier. This will work well for your local disk.

Since this is the local disk, I think this warning will just confuse the
user...

Reply at: https://bugs.launchpad.net/digikam/+bug/500581/comments/15

------------------------------------------------------------------------
On 2010-02-05T17:01:47+00:00 N7DR wrote:

(In reply to comment #9)

> 
> A side note: when adding directories of local FS (it is on dm-crypt+LVM
> volume), I get the following warning:
> It is not possible on your system to identify the storage medium of this path.
> It will be added using the file path as the only identifier. This will work
> well for your local disk.
> 
> Since this is the local disk, I think this warning will just confuse the
> user...

I agree that I always find this a very odd warning. Basically it seems
to say "here's a problem -- although what the problem is isn't at all
obvious -- but you can ignore this message if you're using a local
disk".

I've always ignored it, but also every time I see it I wonder "what
would I do if I received this message but was using a FUSE filesystem
that was physically remote but appeared as a local disk to the system?"
There doesn't seem to be any advice given as to what to do if you're not
using a local disk. So, yes, all-in-all, the user is left with no clear
idea what the message means, nor whether it really affects him, nor what
to do about it. So anything you can do to improve this situation would
be A Good Thing.

Reply at: https://bugs.launchpad.net/digikam/+bug/500581/comments/16

------------------------------------------------------------------------
On 2010-02-05T19:23:55+00:00 Marcel-wiesweg wrote:

Any better suggestions for the message?
The technical background is that Solid does not provide information for such storage devices, so in fact we dont now what it is and fall back to the mount path.
This can happen is Solid/HAL does not support the local setup - as I would suspect for the LVM mentioned above. This should be fixed in HAL.
The problem can also happen when Solid is not working correctly, which is a platform or installation issue.
It also covers all other cases, which we did not expect and which I dont mention here therefore.

Reply at: https://bugs.launchpad.net/digikam/+bug/500581/comments/17

------------------------------------------------------------------------
On 2010-02-06T14:41:11+00:00 Marcel-wiesweg wrote:

SVN commit 1086098 by mwiesweg:

Apply the same fix as for CollectionManager in the setup code as well
(this code test not-yet-added collections, which are unknown to collectionmanager)

BUG: 221155

 M  +2 -1      NEWS  
 M  +10 -5     utilities/setup/setupcollectionview.cpp  

WebSVN link: http://websvn.kde.org/?view=rev&revision=1086098

Reply at: https://bugs.launchpad.net/digikam/+bug/500581/comments/18

-- 
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to digikam in Ubuntu.
https://bugs.launchpad.net/bugs/500581

Title:
  Add collection error message

To manage notifications about this bug go to:
https://bugs.launchpad.net/digikam/+bug/500581/+subscriptions