Bug 415873 - Database Path wrong after adaption (/ instead of \)
Summary: Database Path wrong after adaption (/ instead of \)
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Setup-Database (show other bugs)
Version: 6.4.0
Platform: Microsoft Windows Microsoft Windows
: NOR normal
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-01-04 14:54 UTC by blaubaer65
Modified: 2020-07-25 14:22 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In: 7.1.0


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description blaubaer65 2020-01-04 14:54:52 UTC
SUMMARY
When using the setuo assistent, database path is the same as picture collection path. After change, the new path does contain a slash instead of a backslash.

STEPS TO REPRODUCE
1. Run Setup assistant
2. Choose specific new database path (for instance pictures on drive D. , database on drive c: as this is an SSD)
3. After confirming the new database path, path is shown correctly (eg c:\digicam, bt when clicking next, digikam states, missing write permission on database folder, c:/digicam.

OBSERVED RESULT
Seems the new setting is not updated correctly so that the new path cannot be found as it contains Unix Slash instead of backslash

EXPECTED RESULT


SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
Comment 1 caulier.gilles 2020-01-04 14:58:58 UTC
Maik, I think this problem was fixed with 6.X. Right ?

Blaubaer65,

Can you check with official 6.4.0 Windows installer.

You can also test with the current 7.0.0-beta2 Windows installer available here:

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

Gilles Caulier
Comment 2 blaubaer65 2020-01-04 15:17:39 UTC
   Hello Gilles,I checked with the following download :
   digiKam-6.4.0-Win64.exeBest regardsUli *Gesendet:* Samstag, 04. Januar
   2020 um 15:58 Uhr
   *Von:* bugzilla_noreply@kde.org
   *An:* blaubaer65@gmx.de
   *Betreff:* [digikam] [Bug 415873] Database Path wrong after adaption
   (/ instead of \)https://bugs.kde.org/show_bug.cgi?id=415873

   caulier.gilles@gmail.com changed:

   What |Removed |Added
   ----------------------------------------------------------------------------
   Summary|Datapoase Path wrong after |Database Path wrong after
   |adaption (/ instead of \) |adaption (/ instead of \)
   CC| |caulier.gilles@gmail.com

   --- Comment #1 from caulier.gilles@gmail.com ---
   Maik, I think this problem was fixed with 6.X. Right ?

   Blaubaer65,

   Can you check with official 6.4.0 Windows installer.

   You can also test with the current 7.0.0-beta2 Windows installer
   available
   here:

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

   Gilles Caulier

   --
   You are receiving this mail because:
   You reported the bug.
Comment 3 blaubaer65 2020-01-04 15:51:02 UTC
Hello Gilles,
I checked with the following download : digiKam-6.4.0-Win64.exe. I did not want to use a beta for "production" use. But I can tsest, if you can please provide a download link, I only find 6.4.0 on the website.

Best regards
Uli
Comment 4 Maik Qualmann 2020-01-04 16:07:30 UTC
This is not a bug and not the cause of the problem. We correctly display the path for the user under Windows as "\". Internally, we and Qt always use "/". I can even use the "/" via the Windows API. DigiKam has no rights to write in a directory under C:\. Only in the user directory or under a drive other than the system drive. We can not change that, programs must be certified in newer Windows versions to write in C:\.

Maik
Comment 5 Maik Qualmann 2020-01-04 16:20:37 UTC

*** This bug has been marked as a duplicate of bug 398288 ***
Comment 6 caulier.gilles 2020-01-04 16:28:50 UTC
Weekly build of digiKam pre-version for testing :

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

Gilles Caulier
Comment 7 blaubaer65 2020-01-04 16:35:23 UTC
Hi Maik,
even if I change to G:\Digikam I get the same message and error randomly.

Edit: G: was my former Windows partition on Windoiws 7, seems thats the issue. When using another drive it works fine. Thanks a lot for your support.

Maybe it is an idea to put a hint on the screen that no Windows partioon should be used.

Best regards
Uli
Comment 8 caulier.gilles 2020-07-25 14:22:30 UTC
Fixed with #398288