[digiKam-users] No selectable folders for root path

[Edoardo]

Dear all,

I'm running digiKam 7.1 on elementary os 5.1.7.

On the guided setup, I selected my Images folder as root folder for digiKam.

Now I want to add my Documents folder to my albums in digiKam too... but none of my home folders show up in the "add albums" dialog except Images (already imported).

I'm attaching images where my folders are visible (Files app) and not visible (digiKam). I looked for them everywhere on digiKam, but can't find them.

This is quite weird, as you can tell I'm new to digiKam, and I have no idea what's going on.

Kindly,

Edoardo

[Maik Qualmann]

Look in the digiKam settings under Collections. There you can set up your
document folder as an additional collection.
With all other import functions the content of documents would be copied into
the image folder.

Maik

Am Sonntag, 17. Januar 2021, 01:36:40 CET schrieb Edoardo Milan:

> Dear all,
>
> I'm running digiKam 7.1 on elementary os 5.1.7.
> On the guided setup, I selected my Images folder as root folder for
> digiKam.
> Now I want to add my Documents folder to my albums in digiKam too...
> but none of my home folders show up in the "add albums" dialog except
> Images (already imported).
> I'm attaching images where my folders are visible (Files app) and not
> visible (digiKam). I looked for them everywhere on digiKam, but can't
> find them.
> This is quite weird, as you can tell I'm new to digiKam, and I have no
> idea what's going on.
>
> Kindly,
>
> Edoardo

[MatthiasLaeufer]

Dear Edoardo,

Although I don't see the attached Screenshots I know what you're talking about. I have the same issue with digikam 7.1 (flathub) and Mint 20.
Additionally I tried the following: When adding a collection I was given the option to create a new folder, what I did. The the new collection appeared in DK. In that collection I can create a new album and copy pistures from the old collection to the new one.
But on the Filesystem there's no new folder.

When trying to add an existing folder, I even set the permissions to 777 and changed the user and group to my user for that folder as well as for the parent folder.

@Edoardo: How did you install DK? Also via flathub?

Kind regards
Matthias

Am 17.01.21, 01:37 schrieb [hidden email]:

Send Digikam-users mailing list submissions to
[hidden email]

To subscribe or unsubscribe via the World Wide Web, visit
https://mail.kde.org/mailman/listinfo/digikam-users
or, via email, send a message with subject or body 'help' to
[hidden email]

You can reach the person managing the list at
[hidden email]

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Digikam-users digest..."


Today's Topics:

1. Re: Migrating from Digikam 4 to 6 (Andrew Goodbody)
2. Re: Migrating from Digikam 4 to 6 (Rob Dueckman)
3. No selectable folders for root path (Edoardo Milan)


----------------------------------------------------------------------

Message: 1
Date: Sat, 16 Jan 2021 18:42:52 +0000
From: Andrew Goodbody <[hidden email]>
To: [hidden email]
Subject: Re: [digiKam-users] Migrating from Digikam 4 to 6
Message-ID: <[hidden email]>
Content-Type: text/plain; charset=utf-8; format=flowed

No, the migration tool will not move or copy your picture files. At
least not unless you are doing something unusual that you have not told
us about.

I suspect that you may be suffering from the change in location of where
the digikamrc file was stored, so the new version of digikam is not
aware of where the old version kept its settings. That may not be well
dealt with as you are leaping over a major release, ie digikam 5. But
then I do not remember precisely when that happened, so maybe not.

But you are moving from a very old and obsolete version of digikam to an
old and obsolete version of digikam. You would do better to follow
Giles' advice and download the latest release appimage for digikam 7.

If there is anything you are not sure about please ask a specific
question with as much detail as possible. Explain what you see and why
it concerns you. I do not remember ever needing to run any sort of
migration so I cannot guide you on it with the question you have asked.
You are assuming a level of familiarity with a once in a lifetime task
that we simply do not have nor should we be expected to have.

Andrew

On 16/01/2021 15:18, J D wrote:
> Does the migration tool move the picture files or make copies of them?
> Is it possible to do the migration in-place?
>
> BR,
> angrdtsk
>
> la 16. tammik. 2021 klo 15.40 Gilles Caulier ([hidden email]
> <mailto:[hidden email]>) kirjoitti:
>
> Le sam. 16 janv. 2021 à 14:25, J D <[hidden email]
> <mailto:[hidden email]>> a écrit :
> >
> > Hi, and thanks for quick reply,
> >
> > I got Digikam 6.4 along with a Linux distro, so updating it may
> not be that simple.
>
> We provide an universal Linux AppImage bundle. There is nothing to
> install, it does not install anything. AppImage is just a simple
> executable which uncompresses the whole dependencies in a virtual disk
> in memory and runs the application using chroot.
>
> It's simple to use.
>
> Just to be sure, backup all your database files previously, in case
> of...
>
> >
> > Do I have any options in addition to using the migration tool?
>
> No, because we have fixed more than 1300 bugs since the 6.x release,
> so it will be complicated to resume all problems from previous
> releases.
>
> >
> > What would be the preferred (hopefully future-proof) solution for
> this case?
> >
>
> This kind of huge migration must be performed carefully. This is my
> recommandations:
>
> 1/ Backup databases in all cases.
> 2/ Change Setup/metadata/xmp sidecar option and create a new XMP
> sidecar file for all images. Use Maintenance tool.
> 3/ Stop digiKam and remove your previous database.
> 4/ start the new 7.2.0 appimage. It will ask to recreate the database
> from scratch scanning collection (especially XMP sidecar).
> 5/ Let's start the scan and take a coffee.
>
> Alternative, more faster of course :
>
> 1/ Backup databases in all cases.
> 2/ run migration database tool
> 3/ setup original DB and target DB.
> 4/ process migration and take a coffee.
>
> I always processed the first solution with my huge familly collection
> (250Mb on SSD with sqlite).
>
> Best
>
> Gilles Caulier
>



------------------------------

Message: 2
Date: Sat, 16 Jan 2021 15:17:19 -0500
From: Rob Dueckman <[hidden email]>
To: [hidden email]
Subject: Re: [digiKam-users] Migrating from Digikam 4 to 6
Message-ID: <[hidden email]>
Content-Type: text/plain; charset="utf-8"

There are many ways to skin a cat when it comes to upgrading your copy
of Digikam.

As you are upgrading from a pretty old version, these are the steps >I<
would do things in:

1) make sure you have a current backup of your photos.  From your
earlier messages, it appears you don't like to write the metadata to
your photos as it messes with your backups, so I imagine you are doing
incremental backups.  Just make sure everything is up do date with your
backup first

2)  configure Digikam to write all metadata into sidecar files (.xmp)
 Once done, sync the metadata for all your photos to disk.  This will
take a bit of time, and will write a .xmp file for every photo

3)  MOVE your digikam database files and digikam settings folder to a
safe place.  You want these to be re-created when you run digikam the
next time

4) download the appimage for the current 7.2 release candidate for
Digikam and mark it executable (either command line or viewing the
properties from the desktop) 
     You can find the latest release candidate at
  https://files.kde.org/digikam/    You will want the X86-64 file as
you are running a current linux distribution

5) Run the appimage (double click on the appimage icon from your file
browser on the desktop) and perform the first run configuration
pointing digikam at your photo library.  Once it starts scanning
photos, take a break. It might take a while

6) if everything looks good, uninstall your old copy of digikam, and
remove the old database files and settings folder.

7) In case things don't work, restore your original database files and
digikam settings folder and appimage file  to revert back to the old
version.  

8) configure Digikam settings and update for your preferred metadata
settings.  As .xmp files are quite small, it might be acceptable to
write to .xmp files in addition to the database in the future as it
won't affect your backup size too dramatically.

9) for bonus points and if you're bored enduring a COVID lockdown, scan
your entire collecton for faces and be prepared to name a lot of
people.


Again, this is how I would upgrade my digikam as it gives the ability
to roll back at any point until you remove the old database and
configuration files. 

Rob


On Sat, 2021-01-16 at 15:25 +0200, J D wrote:
> Hi, and thanks for quick reply,
>
> I got Digikam 6.4 along with a Linux distro, so updating it may not
> be that simple.
>
> Do I have any options in addition to using the migration tool?
>
> What would be the preferred (hopefully future-proof) solution for
> this case?
>
> BR,
> angrdtsk
>
> la 16. tammik. 2021 klo 15.13 Gilles Caulier
> ([hidden email]) kirjoitti:
> > Le sam. 16 janv. 2021 à 14:01, J D <[hidden email]> a écrit :
> > >
> > > Hi,
> > >
> > > I lately installed a new Linux distribution, and along with that
> > change, got new version of Digikam (4 -> 6.4). How can I import the
> > meta-data created using the old one to the new one?
> > >
> > > The meta-data is in a database file. I don't like the idea of
> > embedding it into the picture files because that way, changes in
> > meta-data would mean changes in picture files, and that would
> > complicate making back ups.
> >
> > If you use XMP sidecar files (See option in DK/Setup/Metadata
> > panel),
> > you will not touch image files as well.
> >
> > >
> > > I found a dialog for migration in the new Digikam, but got
> > immediately confused, as it seems to require me to move (or copy,
> > that was unclear) the pictures from a directory to another along
> > with the migration. There are roughly 35000 pictures taking 475 GB
> > of space so proceeding with that dialog is not something I will try
> > before I know better what is going happen and why.
> >
> > In all cases, if you use database migration tool, do not migrate to
> > 6.4 release, but to 7.2. release candidate available here :
> >
> > https://files.kde.org/digikam/
> >
> > Best
> >
> > Gilles Caulier
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/digikam-users/attachments/20210116/2088f39c/attachment-0001.htm>

------------------------------

Message: 3
Date: Sun, 17 Jan 2021 01:36:40 +0100
From: Edoardo Milan <[hidden email]>
To: [hidden email]
Subject: [digiKam-users] No selectable folders for root path
Message-ID: <[hidden email]>
Content-Type: text/plain; charset="utf-8"; Format="flowed"

Dear all,

I'm running digiKam 7.1 on elementary os 5.1.7.
On the guided setup, I selected my Images folder as root folder for
digiKam.
Now I want to add my Documents folder to my albums in digiKam too...
but none of my home folders show up in the "add albums" dialog except
Images (already imported).
I'm attaching images where my folders are visible (Files app) and not
visible (digiKam). I looked for them everywhere on digiKam, but can't
find them.
This is quite weird, as you can tell I'm new to digiKam, and I have no
idea what's going on.

Kindly,

Edoardo







-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/digikam-users/attachments/20210117/1abcf8a7/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Schermata da 2021-01-17 01-20-16.png
Type: image/png
Size: 55448 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/digikam-users/attachments/20210117/1abcf8a7/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Schermata da 2021-01-17 01-18-48.png
Type: image/png
Size: 24909 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/digikam-users/attachments/20210117/1abcf8a7/attachment-0001.png>

------------------------------

Subject: Digest Footer

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users


------------------------------

End of Digikam-users Digest, Vol 188, Issue 20
**********************************************

[MatthiasLaeufer]

Dear Edoardo,

Although I don't see the attached Screenshots I know what you're talking about. I have the same issue with digikam 7.1 (flathub) and Mint 20.
Additionally I tried the following: When adding a collection I was given the option to create a new folder, what I did. The the new collection appeared in DK. In that collection I can create a new album and copy pistures from the old collection to the new one.
But on the Filesystem there's no new folder.

When trying to add an existing folder, I even set the permissions to 777 and changed the user and group to my user for that folder as well as for the parent folder.

@Edoardo: How did you install DK? Also via flathub?

Kind regards
Matthias

[brownphotographic]

If you installed digital with flatpak option (elementary supports flatpak
their app store), then try downloading Flatseal app (also available on the
app store). Then in flatseal, scroll down to the section where you see
folder paths. Add your home folder there.

FYI I have had all kinds of problems with flatpak apps. When I was running
digikam flatpak I had that same problem, plus issues accessing other
programs (e.g. open a file in a separate raw converter), and issues with
multimedia support (movies and thumbnails for them were broken). In my
experience, I consider flatpak and specifically the way in which operating
systems integrate support for it, to be an early days experiment that hasn't
really been full thought out and executed.

Instead, I would recommend going to the digital.org website and downloading
the appimage. That will download an executable file, which is similar to
Windows exe or Mac DMG. All dependencies are contained within it and it
works great. This recommendation comes from recent experimentation with apps
that are flatpak, snap and OS repository based that are available in the app
store. I found none of the above worked well with digikam.

If you haven't ever run from an appimage before, once you download the
appimage, right click, select properties and change permissions to allow it
to be executable.

To make appimage even more usable I suggest downloading / installing
https://github.com/TheAssassin/AppImageLauncher



--
Sent from: http://digikam.1695700.n4.nabble.com/digikam-users-f1735189.html

[Edoardo]

Dear Matthias and dear Maik,

thanks a lot for your answers.

Look in the digiKam settings under Collections. There you can set up your document folder as an additional collection.

@Maik I think that's what I was doing actually (unfortunately my embedded screenshot got lost I think, but it showed I was under settings > collections).

How did you install DK? Also via flathub?

@Matthias yes, indeed! I too started thinking that could be the problem, due to sandboxing or something so maybe.

I installed DK through appimage now and it looks like the problem isn't there this way.

Unfortunately appimage breaks a bit my UX (e.g. I can't seem to be able to get system icons on it), so it isn't a perfect solution either, but it's better than being limited to only having the initially selected folder as root.

Best,

Edoardo



17 gennaio 2021 12:07, "Matthias Läufer" <[hidden email]> wrote:

Dear Edoardo,

Although I don't see the attached Screenshots I know what you're talking about. I have the same issue with digikam 7.1 (flathub) and Mint 20.
Additionally I tried the following: When adding a collection I was given the option to create a new folder, what I did. The the new collection appeared in DK. In that collection I can create a new album and copy pistures from the old collection to the new one.
But on the Filesystem there's no new folder.

When trying to add an existing folder, I even set the permissions to 777 and changed the user and group to my user for that folder as well as for the parent folder.

@Edoardo: How did you install DK? Also via flathub?

Kind regards
Matthias

Am 17.01.21, 01:37 schrieb [hidden email]:

Send Digikam-users mailing list submissions to
[hidden email]

To subscribe or unsubscribe via the World Wide Web, visit
https://mail.kde.org/mailman/listinfo/digikam-users
or, via email, send a message with subject or body 'help' to
[hidden email]

You can reach the person managing the list at
[hidden email]

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Digikam-users digest..."


Today's Topics:

1. Re: Migrating from Digikam 4 to 6 (Andrew Goodbody)
2. Re: Migrating from Digikam 4 to 6 (Rob Dueckman)
3. No selectable folders for root path (Edoardo Milan)


----------------------------------------------------------------------

Message: 1
Date: Sat, 16 Jan 2021 18:42:52 +0000
From: Andrew Goodbody <[hidden email]>
To: [hidden email]
Subject: Re: [digiKam-users] Migrating from Digikam 4 to 6
Message-ID: <[hidden email]>
Content-Type: text/plain; charset=utf-8; format=flowed

No, the migration tool will not move or copy your picture files. At
least not unless you are doing something unusual that you have not told
us about.

I suspect that you may be suffering from the change in location of where
the digikamrc file was stored, so the new version of digikam is not
aware of where the old version kept its settings. That may not be well
dealt with as you are leaping over a major release, ie digikam 5. But
then I do not remember precisely when that happened, so maybe not.

But you are moving from a very old and obsolete version of digikam to an
old and obsolete version of digikam. You would do better to follow
Giles' advice and download the latest release appimage for digikam 7.

If there is anything you are not sure about please ask a specific
question with as much detail as possible. Explain what you see and why
it concerns you. I do not remember ever needing to run any sort of
migration so I cannot guide you on it with the question you have asked.
You are assuming a level of familiarity with a once in a lifetime task
that we simply do not have nor should we be expected to have.

Andrew

On 16/01/2021 15:18, J D wrote:

> Does the migration tool move the picture files or make copies of them?
> Is it possible to do the migration in-place?
>
> BR,
> angrdtsk
>
> la 16. tammik. 2021 klo 15.40 Gilles Caulier ([hidden email]
> <[hidden email]>) kirjoitti:
>
> Le sam. 16 janv. 2021 à 14:25, J D <[hidden email]
> <[hidden email]>> a écrit :
> >
> > Hi, and thanks for quick reply,
> >
> > I got Digikam 6.4 along with a Linux distro, so updating it may
> not be that simple.
>
> We provide an universal Linux AppImage bundle. There is nothing to
> install, it does not install anything. AppImage is just a simple
> executable which uncompresses the whole dependencies in a virtual disk
> in memory and runs the application using chroot.
>
> It's simple to use.
>
> Just to be sure, backup all your database files previously, in case
> of...
>
> >
> > Do I have any options in addition to using the migration tool?
>
> No, because we have fixed more than 1300 bugs since the 6.x release,
> so it will be complicated to resume all problems from previous
> releases.
>
> >
> > What would be the preferred (hopefully future-proof) solution for
> this case?
> >
>
> This kind of huge migration must be performed carefully. This is my
> recommandations:
>
> 1/ Backup databases in all cases.
> 2/ Change Setup/metadata/xmp sidecar option and create a new XMP
> sidecar file for all images. Use Maintenance tool.
> 3/ Stop digiKam and remove your previous database.
> 4/ start the new 7.2.0 appimage. It will ask to recreate the database
> from scratch scanning collection (especially XMP sidecar).
> 5/ Let's start the scan and take a coffee.
>
> Alternative, more faster of course :
>
> 1/ Backup databases in all cases.
> 2/ run migration database tool
> 3/ setup original DB and target DB.
> 4/ process migration and take a coffee.
>
> I always processed the first solution with my huge familly collection
> (250Mb on SSD with sqlite).
>
> Best
>
> Gilles Caulier
>

------------------------------

Message: 2
Date: Sat, 16 Jan 2021 15:17:19 -0500
From: Rob Dueckman <[hidden email]>
To: [hidden email]
Subject: Re: [digiKam-users] Migrating from Digikam 4 to 6
Message-ID: <[hidden email]>
Content-Type: text/plain; charset="utf-8"

There are many ways to skin a cat when it comes to upgrading your copy
of Digikam.

As you are upgrading from a pretty old version, these are the steps >I<
would do things in:

1) make sure you have a current backup of your photos. From your
earlier messages, it appears you don't like to write the metadata to
your photos as it messes with your backups, so I imagine you are doing
incremental backups. Just make sure everything is up do date with your
backup first

2) configure Digikam to write all metadata into sidecar files (.xmp)
Once done, sync the metadata for all your photos to disk. This will
take a bit of time, and will write a .xmp file for every photo

3) MOVE your digikam database files and digikam settings folder to a
safe place. You want these to be re-created when you run digikam the
next time

4) download the appimage for the current 7.2 release candidate for
Digikam and mark it executable (either command line or viewing the
properties from the desktop)
You can find the latest release candidate at
https://files.kde.org/digikam/ You will want the X86-64 file as
you are running a current linux distribution

5) Run the appimage (double click on the appimage icon from your file
browser on the desktop) and perform the first run configuration
pointing digikam at your photo library. Once it starts scanning
photos, take a break. It might take a while

6) if everything looks good, uninstall your old copy of digikam, and
remove the old database files and settings folder.

7) In case things don't work, restore your original database files and
digikam settings folder and appimage file to revert back to the old
version.

8) configure Digikam settings and update for your preferred metadata
settings. As .xmp files are quite small, it might be acceptable to
write to .xmp files in addition to the database in the future as it
won't affect your backup size too dramatically.

9) for bonus points and if you're bored enduring a COVID lockdown, scan
your entire collecton for faces and be prepared to name a lot of
people.


Again, this is how I would upgrade my digikam as it gives the ability
to roll back at any point until you remove the old database and
configuration files.

Rob


On Sat, 2021-01-16 at 15:25 +0200, J D wrote:

> Hi, and thanks for quick reply,
>
> I got Digikam 6.4 along with a Linux distro, so updating it may not
> be that simple.
>
> Do I have any options in addition to using the migration tool?
>
> What would be the preferred (hopefully future-proof) solution for
> this case?
>
> BR,
> angrdtsk
>
> la 16. tammik. 2021 klo 15.13 Gilles Caulier
> ([hidden email]) kirjoitti:
> > Le sam. 16 janv. 2021 à 14:01, J D <[hidden email]> a écrit :
> > >
> > > Hi,
> > >
> > > I lately installed a new Linux distribution, and along with that
> > change, got new version of Digikam (4 -> 6.4). How can I import the
> > meta-data created using the old one to the new one?
> > >
> > > The meta-data is in a database file. I don't like the idea of
> > embedding it into the picture files because that way, changes in
> > meta-data would mean changes in picture files, and that would
> > complicate making back ups.
> >
> > If you use XMP sidecar files (See option in DK/Setup/Metadata
> > panel),
> > you will not touch image files as well.
> >
> > >
> > > I found a dialog for migration in the new Digikam, but got
> > immediately confused, as it seems to require me to move (or copy,
> > that was unclear) the pictures from a directory to another along
> > with the migration. There are roughly 35000 pictures taking 475 GB
> > of space so proceeding with that dialog is not something I will try
> > before I know better what is going happen and why.
> >
> > In all cases, if you use database migration tool, do not migrate to
> > 6.4 release, but to 7.2. release candidate available here :
> >
> > https://files.kde.org/digikam/
> >
> > Best
> >
> > Gilles Caulier

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/digikam-users/attachments/20210116/2088f39c/attachment-0001.htm>

------------------------------

Message: 3
Date: Sun, 17 Jan 2021 01:36:40 +0100
From: Edoardo Milan <[hidden email]>
To: [hidden email]
Subject: [digiKam-users] No selectable folders for root path
Message-ID: <[hidden email]>
Content-Type: text/plain; charset="utf-8"; Format="flowed"

Dear all,

I'm running digiKam 7.1 on elementary os 5.1.7.
On the guided setup, I selected my Images folder as root folder for
digiKam.
Now I want to add my Documents folder to my albums in digiKam too...
but none of my home folders show up in the "add albums" dialog except
Images (already imported).
I'm attaching images where my folders are visible (Files app) and not
visible (digiKam). I looked for them everywhere on digiKam, but can't
find them.
This is quite weird, as you can tell I'm new to digiKam, and I have no
idea what's going on.

Kindly,

Edoardo







-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/digikam-users/attachments/20210117/1abcf8a7/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Schermata da 2021-01-17 01-20-16.png
Type: image/png
Size: 55448 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/digikam-users/attachments/20210117/1abcf8a7/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Schermata da 2021-01-17 01-18-48.png
Type: image/png
Size: 24909 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/digikam-users/attachments/20210117/1abcf8a7/attachment-0001.png>

------------------------------

Subject: Digest Footer

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users


------------------------------

End of Digikam-users Digest, Vol 188, Issue 20
**********************************************

[Edoardo]

Dear brownphotographic,

thanks a lot for your answer! It's very kind of you to share all of these informations and I really appreciate it, I wasn't aware of any of the software you're pointing out.

Yes, I did install DK through flatpak (and through elementary's app center itself) and I'm convinced now that that was the cause of my issue.

By now I have already installed the appimage (and manually added it to the apps menu), so I couldn't test Flatseal or AppImageLauncher out, but I'm sure they will come in handy in the future.

I certainly agree flatpak apps are still quite clumsy to seamlessly blend in the system, at least on elementary (although at least they give the option to run more recent software).

AppImage, as I was saying, looks more solid -- but lacks native UX integration for what I can see (It's like suddenly jumping from Pantheon to KDE).

Thanks again for your help,

E.

Il giorno dom 17 gen 2021 alle 13:45, brownphotographic <[hidden email]> ha scritto:

If you installed digital with flatpak option (elementary supports flatpak their app store), then try downloading Flatseal app (also available on the app store). Then in flatseal, scroll down to the section where you see folder paths. Add your home folder there. FYI I have had all kinds of problems with flatpak apps. When I was running digikam flatpak I had that same problem, plus issues accessing other programs (e.g. open a file in a separate raw converter), and issues with multimedia support (movies and thumbnails for them were broken). In my experience, I consider flatpak and specifically the way in which operating systems integrate support for it, to be an early days experiment that hasn't really been full thought out and executed. Instead, I would recommend going to the digital.org website and downloading the appimage. That will download an executable file, which is similar to Windows exe or Mac DMG. All dependencies are contained within it and it works great. This recommendation comes from recent experimentation with apps that are flatpak, snap and OS repository based that are available in the app store. I found none of the above worked well with digikam. If you haven't ever run from an appimage before, once you download the appimage, right click, select properties and change permissions to allow it to be executable. To make appimage even more usable I suggest downloading / installing https://github.com/TheAssassin/AppImageLauncher -- Sent from: http://digikam.1695700.n4.nabble.com/digikam-users-f1735189.html