Bug 365313

Summary: SETUP : Selecting location for pictures during initial setup results in wrong collection path
Product: [Applications] digikam Reporter: Alain Goossens <me>
Component: Setup-DatabaseAssignee: Digikam Developers <digikam-bugs-null>
Status: RESOLVED FIXED    
Severity: normal CC: caulier.gilles, ian
Priority: NOR    
Version: 5.0.0   
Target Milestone: ---   
Platform: Microsoft Windows   
OS: Microsoft Windows   
URL: https://1drv.ms/i/s!AlFEff9VyWPMi4tg1wrKJ5rxHXv3fg
Latest Commit: Version Fixed In: 5.4.0

Description Alain Goossens 2016-07-10 05:13:49 UTC 
During initial setup / configuration it detect correctly my pictures on \\server\share.
** Firts it gives me a warning message saying that I don't have write rights on that folder wihch is wrong but this doesn't stop the config.

When initial setup completed it didn't fin any images, checking the config it changed the \ to %2F and now don't recognize the location. %2F%2F\Server%2FShare

See attached screenshot Col.0 is the initial setup line where you see the Hex code the second one has been added after.


Reproducible: Didn't try
Comment 1 caulier.gilles 2016-07-16 12:40:50 UTC 
Maik,

You don't have fixed this problem before 5.0.0 release ?

Gilles
Comment 2 caulier.gilles 2016-07-23 09:46:14 UTC 
This problem do not touch only Windows but OSX, with local collection set in older version of digiKam (sqlite).
Comment 3 caulier.gilles 2016-07-27 07:42:06 UTC 
Maik,

Your previous fixes done here :

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

Sound like not complete after all...

Gilles
Comment 4 caulier.gilles 2016-08-06 05:36:01 UTC 
*** Bug 366446 has been marked as a duplicate of this bug. ***
Comment 5 caulier.gilles 2016-11-28 14:06:43 UTC 
Can you reproduce the problem using digiKam Linux AppImage bundle ? The last
bundle is available at this url:

https://drive.google.com/drive/folders/0BzeiVr-byqt5Y0tIRWVWelRJenM

Gilles Caulier
Comment 6 caulier.gilles 2016-12-29 11:40:33 UTC 
Can you reproduce the problem with 5.4.0-pre release installer for Windows,
available here :

https://drive.google.com/drive/folders/0BzeiVr-byqt5Y0tIRWVWelRJenM
Comment 7 Alain Goossens 2017-01-01 16:16:01 UTC 
Removed v5.0.0 and installed v5.4.0 successfully not sure if this would reproduce the original situation but no problem detected.