[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-bugs-dist
Subject: [Bug 307750] New: No path to mysqld set in server configuration
From: Carsten Pfeiffer <pfeiffer () kde ! org>
Date: 2012-10-02 21:03:01
Message-ID: bug-307750-17878 () http ! bugs ! kde ! org/
[Download RAW message or body]
https://bugs.kde.org/show_bug.cgi?id=307750
Bug ID: 307750
Severity: major
Version: 2.6.0
Priority: NOR
Assignee: digikam-devel@kde.org
Summary: No path to mysqld set in server configuration
Classification: Unclassified
OS: Linux
Reporter: pfeiffer@kde.org
Hardware: Other
Status: NEW
Component: Database
Product: digikam
I cannot use Digikam with mysql anymore. It refuses to start the mysql process.
I suppose this is because of the following code in databaseserver.cpp:
const QString mysqldPath(DatabaseConfigElement::element(dbType).dbServerCmd);
//const QString mysqldPath("/usr/sbin/mysqld");
if ( mysqldPath.isEmpty() || mysqldPath.compare( QLatin1String(
"SERVERCMD_MYSQL-NOTFOUND" ) ))
{
kDebug() << "No path to mysqld set in server configuration!";
return DatabaseServerError(DatabaseServerError::StartError, i18n("No
path to mysqld set in server configuration."));
}
The method always aborts when the mysqldPath is either empty or !=
"SERVERCMD_MYSQL-NOTFOUND". So unless your mysqld binary is named like that,
digikam refuses to start it. You should rather use the == operator than
compare().
Reproducible: Always
Steps to Reproduce:
1. Configure digikam to use an internal mysql server
2. Invoke "Check Database Connection" or just restart digikam
Actual Results:
Digikam is unable to start mysqld and thus cannot connect to the database.
Expected Results:
Digikam starts mysqld properly.
I'd classify this as major, because I cannot access my images from digikam
anymore.
--
You are receiving this mail because:
You are watching all bug changes.
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic