No subject

[YGPC]

Sent on:  15 March 2017, at 05:03 pm

Hello again

Got back sooner than I thought. Attached is the screen shot you asked 
for. This comes up as soon as Digikam starts

When you email me back, in addition to your helpful suggestion/s to fix 
the problem, can you tell me where on my computer all these "Photos" 
folder/files are, then I can go there and delete. If I try and delete 
within Digikam, I get a grayed computer screen on and off (slowly) but 
no deletions

Await your reply with interest, many thanks


On 15/03/17 16:22, Andrey Goreev wrote:
> If you could record your screen and share the video with us that would 
> help to understand the issue.
>
> I have never seen anything like that.
>
> Sent from my Samsung Galaxy smartphone.
>
> -------- Original message --------
> From: YGPC <ygpc at hushmail.com>
> Date: 2017-03-14 6:16 PM (GMT-07:00)
> To: digiKam - Home Manage your photographs as a professional with the 
> power of open source <digikam-users at kde.org>
> Subject: Re:
>
> Sent on:  15 March 2017, at 01:16 pm
>
> Hi Andrew
>
> I diduse the "Collection" way but all I go was the 'head" folder so to 
> speak, none of the sub-folders or individual photo/image files, any 
> suggestions on why this happened
>
> Gregory
>
>
>
> On 15/03/17 12:26, Andrew Goodbody wrote:
>> OK, this sounds like you are trying to do the wrong thing. For photos 
>> on the computer, you add that location as a 'Collection' to digiKam, 
>> you do not 'Import' them. Importing will make a copy of the images 
>> and is used to bring in photos from an external source eg camera or 
>> flash card etc.
>>
>> Andrew
>>
>> On 14/03/17 22:58, YGPC wrote:
>>> Hi
>>>
>>> I do have all the required permissions, like can read and write to all
>>> drives, so can't be that. I did in between writing back and forth get
>>> Digikam to find the Photos folder, click to import and all that was
>>> imported was the main folder, "Photos" no sub folders and it has
>>> duplicated the Photos folder about 40 times, each folder called photos
>>> being a sub folder of the previous!
>>>
>>> Have spent hours on this and about ready to just delete all and
>>> everything associated with DigiKam and look for something that works,
>>> unless you can convince me otherwise. I see I am not alone with this
>>> same problem
>>>
>>> Gregory
>>>
>>>
>>>
>>> On 15/03/17 11:48, Andreas T. Ege wrote:
>>>> Hello,
>>>>
>>>> On 14.03.2017 22:05, YGPC wrote:
>>>>> Hi
>>>>> Have just installed Digikam 5 on Ubuntu, my photo folder in on a
>>>>> separate drive (within the computer, not external USB etc) and 
>>>>> Digikam
>>>>> can't "see" the other drive, just only sees the system drive so can't
>>>>> import. Any chance of a suggestion, if so, greatly appreciated
>>>>> Have tried ALL found suggestions, nothing works for me!
>>>>> Gregory
>>>>>
>>>> maybe some more information about the hard drive(s), system setup and
>>>> what "ALL found suggestions" that are not working are?
>>>>
>>>> Besides the suggested mount possibility I would think about 
>>>> permissions
>>>> as a first step. You might have tried that, if running digikam as root
>>>> does find the drive/ folders it would suggest a permission problem.
>>>> Another try is to right click on one of the images in your folder and
>>>> "open with" digikam. At least you'd then know whether digikam can
>>>> actually "see" the images or not.
>>>>
>>>>
>>>
>>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/digikam-users/attachments/20170315/629e2c53/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Signature - 01.jpg
Type: image/jpeg
Size: 12328 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/digikam-users/attachments/20170315/629e2c53/attachment.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Screenshot from 2017-03-15 16-57-34.png
Type: image/png
Size: 298035 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/digikam-users/attachments/20170315/629e2c53/attachment.png>