digikam.dbengine: Error while opening the database. Error was QSqlError("", "Driver not loaded", "Driver not loaded") QSqlDatabase: driver not loaded QSqlDatabase: available drivers: QSQLITE3 QMYSQL QMYSQL3 SKGSQLCIPHER .... digikam.facedb: No Sqlite3 driver available. List of QSqlDatabase drivers: ("QSQLITE3", "QMYSQL", "QMYSQL3", "SKGSQLCIPHER") digikam.facesengine: Failed to initialize face database
Is qt5-database-plugin-sqlite installed on your system?
CC: (none) => geiger.david68210Assignee: bugsquad => anaselli
CC: (none) => mageia
(In reply to David GEIGER from comment #1) > Is qt5-database-plugin-sqlite installed on your system? Well done : I had only the i586 version. So this is a bad requires in digikam x86_64 digikam : urpme libqt5-database-plugin-sqlite-5.6.0-10.mga6 Para satisfazer as dependências, os seguintes 2 pacotes serão removidos (17MB): digikam-5.0.0-0.beta6.3.mga6.x86_64 (devido a faltar qt5-database-plugin-sqlite) libqt5-database-plugin-sqlite-5.6.0-10.mga6.i586
I do not think it's a bad requires in digikam: $ urpmq --requires digikam |grep 'database-plugin' qt5-database-plugin-sqlite $ So the requires on "qt5-database-plugin-sqlite" seems correct here.
So a bad provides in qtbase5 ? 273 %package -n %{_lib}qt5-database-plugin-sqlite 274 Summary: Qt%{qtmajor} SQLITE Database Plugin 275 Group: Databases 276 BuildRequires: sqlite3-devel 277 Provides: qt5-database-plugin-sqlite = %version-%release 278 Obsoletes: qt5-database-plugin-sqlite 279 280 Provides: qtbase5-database-plugin-sqlite = %version-%release 281 Obsoletes: qtbase5-database-plugin-sqlite < 5.5.1-2
Maybe digikam should require %{_lib}qt5-database-plugin-sqlite instead of qtbase5-database-plugin-sqlite. This way we would be sure that the good arch is installed.
(In reply to Nicolas Lécureuil from comment #5) > Maybe digikam should require %{_lib}qt5-database-plugin-sqlite instead of > qtbase5-database-plugin-sqlite. > > This way we would be sure that the good arch is installed. Indeed. Here the i586 version was either installed manually, or via an i586 package that requires it, and digikam's RPM incorrectly assumes that the dependency is fulfilled.
This was fixed.
Status: NEW => RESOLVEDResolution: (none) => FIXED