Bug 389505 - Database port reset to 3306 when oppening digiKam setup (working with maiaDB10)
Summary: Database port reset to 3306 when oppening digiKam setup (working with maiaDB10)
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Setup-Database (show other bugs)
Version: 5.7.0
Platform: Microsoft Windows Microsoft Windows
: NOR normal
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-01-27 12:21 UTC by Heinz Schütz
Modified: 2018-08-30 20:48 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In: 6.0.0

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Heinz Schütz 2018-01-27 12:21:10 UTC 
Using a mariaDB 10, Host Port set to 3307.
Initial setup and start of digiKam is ok, working wit digiKam is possible.

When "digikam setup" is saved (closed with OK / even without any modification) this causes an Error Message "Cant't connect to MySQL server on 'xxx' (10061) QMYSQL Unable to connect.

Reason: Database Hostport setings are loaded with an altered port value set to "3306" (default) into the setup panel, instaed with the one used with the instalation and used when digikam starts.

When seting the port in the databse setings to the right value Prior confirming wih OK (needed for any setting change, eg. adding a albumpath) the use of the DB continues to be OK.

Might or may be not resolved with https://bugs.kde.org/show_bug.cgi?id=384366
Comment 1 Heinz Schütz 2018-01-27 13:08:50 UTC 
digiKam was mot installed in the default path but on
E:\appl\digiKam
All other DB settings where read correctly
Comment 2 Maik Qualmann 2018-01-27 18:36:58 UTC 
Look in the bug 384366, this bug was finally fixed in digiKam-5.8.0. You are using digiKam-5.7.0. I can not reproduce the problem here either.

Maik
Comment 3 caulier.gilles 2018-01-27 19:19:48 UTC 
You can try with last 5.9.0 pre release installer, just recompiled today :

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

Gilles Caulier
Comment 4 Maik Qualmann 2018-02-04 11:56:45 UTC 

*** This bug has been marked as a duplicate of bug 384366 ***
Comment 5 caulier.gilles 2018-08-30 20:48:13 UTC 
Not reproducible with 6.0.0