Bug 382231 - First Run wizzard path
Summary: First Run wizzard path
Status: RESOLVED INTENTIONAL
Alias: None
Product: digikam
Classification: Applications
Component: Setup-FirstRun (show other bugs)
Version: 5.6.0
Platform: Microsoft Windows Microsoft Windows
: NOR minor
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-07-11 09:24 UTC by MartyLake
Modified: 2022-01-22 13:56 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In: 7.6.0


Attachments
attachment-24387-0.html (2.29 KB, text/html)
2017-07-11 14:19 UTC, MartyLake
Details
attachment-27496-0.html (2.13 KB, text/html)
2017-07-11 15:21 UTC, MartyLake
Details

Note You need to log in before you can comment on or make changes to this bug.
Description MartyLake 2017-07-11 09:24:10 UTC
Hello,

I switched from mac to windows recently. 

I downloaded the windows installer and entered the location of the old library. In digiKam, no picture was found. I went to the settings, and the path was all scrambled (because of backslashes I suppose).

At this point, I removed the broken library, and add the path again. All is working well so far.

This may not be very clear, but I can provide as much info as possible, if you tell me what you need :)


Best
Comment 1 caulier.gilles 2017-07-11 09:44:42 UTC
You want mean that collection path in First Run wizard is not well decoded from older DK version ?

Which DK version do you use previously ?

Gilles Caulier
Comment 2 MartyLake 2017-07-11 14:19:52 UTC
Created attachment 106559 [details]
attachment-24387-0.html

Hi Gilles,
Sorry, that's not the complete accurate version of what happened.

- I copied the library directory from my old computer to my new one
- I installed digiKam-5.5.0-01-Win64 for the first time in this computer,
and located the library directory with the installer wizzard.
- The library showed no picture
- I installed the latest digiKam-5.6.0-01-Win64 (that automatically
uninstalled the 5.5 DK)
- Still no picture
- I went to the options, saw the "not well decoded" path, deleted it
- I added manually the library path
- Everything works

Is it clearer ?

Le 11 juil. 2017 11:45, <bugzilla_noreply@kde.org> a écrit :

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

caulier.gilles@gmail.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |caulier.gilles@gmail.com
          Component|general                     |setup
            Summary|Installation wizzard path   |First Run wizzard path

--- Comment #1 from caulier.gilles@gmail.com ---
You want mean that collection path in First Run wizard is not well decoded
from
older DK version ?

Which DK version do you use previously ?

Gilles Caulier

--
You are receiving this mail because:
You reported the bug.
Comment 3 caulier.gilles 2017-07-11 14:58:48 UTC
If you have copied the database from older computer (MAcOS) to new one (Windows), the path to collection are different (UNIX -> Windows)

This explain why you need to fix that in setup dialog. This kind of migration is not yet implementation in First Run assistant.

Gilles Caulier
Comment 4 MartyLake 2017-07-11 15:21:00 UTC
Created attachment 106560 [details]
attachment-27496-0.html

Ok !

So there are 3 paths here:

- the one I inputed in the installer wizzard (which I chose manually using
Windows File Picker dialog => good)
- the one in the folder I copied (which format is wrong because it's not
the same folder anymore => bad)
- the one I fixed in the setup dialog (=>good)

Can I do something else to complement this report ?


---
Matthieu TALBOT
neogaldr@gmail.com

+33 629 22 15 70
fr.linkedin.com/in/matthieutalbot
http://www.soundcloud.com/Marty-Lake
http://lifehacker.com/5028808/how-eom-makes-your-email-more-efficient

On 11 July 2017 at 16:58, <bugzilla_noreply@kde.org> wrote:

> https://bugs.kde.org/show_bug.cgi?id=382231
>
> --- Comment #3 from caulier.gilles@gmail.com ---
> If you have copied the database from older computer (MAcOS) to new one
> (Windows), the path to collection are different (UNIX -> Windows)
>
> This explain why you need to fix that in setup dialog. This kind of
> migration
> is not yet implementation in First Run assistant.
>
> Gilles Caulier
>
> --
> You are receiving this mail because:
> You reported the bug.
>
Comment 5 caulier.gilles 2017-07-11 15:23:29 UTC
yes :

- the one in the folder I copied (which format is wrong because it's not
the same folder anymore => bad)

==> Give the exactly the old and the new paths to host collections.

Gilles Caulier
Comment 6 caulier.gilles 2020-01-12 22:40:26 UTC
Matthieu,

Any feedback for this file ?

Best

Gilles Caulier
Comment 7 caulier.gilles 2020-08-04 08:06:47 UTC
digiKam 7.0.0 stable release is now published:

https://www.digikam.org/news/2020-07-19-7.0.0_release_announcement/

We need a fresh feedback on this file using this version.

Best Regards

Gilles Caulier
Comment 8 caulier.gilles 2022-01-09 04:11:26 UTC
Hi Marty and happy new year,

Can you reproduce the problem with digiKam 7.5.0 pre-release installer for
Windows available here :

https://files.kde.org/digikam/

Best regards

Gilles Caulier
Comment 9 MartyLake 2022-01-22 11:51:35 UTC
Dear Gilles Caulier,

There is been a long time since I used Digikam. I am planning to permanently use Ubuntu as my main distro, so I should not encounter any such cross platforme issue anymore. Sorry for missing the notification last years.

Best,
Comment 10 Maik Qualmann 2022-01-22 12:15:09 UTC
@Gilles, we can close this bug. The base path to the image library in the database could not be adjusted, this is now possible. Either way, an existing digikamrc can never be transferred from Unix to Windows or vice versa.

Maik
Comment 11 caulier.gilles 2022-01-22 13:56:13 UTC
Thanks Maik, I close this file now.