[Digikam-devel] [Bug 258409] Tags and TagsTree table is empty after DB migration from sqlite to mysql

Volker neuntoeter at arcor.de
Sun May 8 12:29:39 BST 2011


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





--- Comment #10 from Volker <neuntoeter arcor de>  2011-05-08 13:29:36 ---
Hi Francesco, 

thanks for your detailed howto! 
After some struggle with the dependencies, I managed to install the patched
digikam 2.0 b6 under my home directory.

Digikam starts up fine. I started the db migration tool immediately after
startup. The first connection error (to mysql) I got was due to apparmor (I
have ~/.kde linked to ~/Private/.kde). I disabled the mysqld apparmor profiles
and still got a connection error when clicking on "Check DB connection". 
I then deleted the existing mysql db under ~/.kde/share/apps/digikam.

After clicking "Check DB connection" the mysql database was recreated again
under ~/.kde/share/apps/digikam and the database connection test was
successful.

Unfortunately there is an error when I start the db migration. The progressbar
shows 7% and a message pops up "Error while creating the database schema".

Console output shows the following: 
volker at kiste:~$ digikam_git.sh 
kbuildsycoca4 running...
kbuildsycoca4(2825) KConfigGroup::readXdgListEntry: List entry Categories in
"/usr/share/applications/im-switch.desktop" is not compliant with XDG standard
(missing trailing semicolon). 
kbuildsycoca4(2825) KConfigGroup::readXdgListEntry: List entry Categories in
"/usr/share/applications/gpsdrive.desktop" is not compliant with XDG standard
(missing trailing semicolon). 
kbuildsycoca4(2825) KConfigGroup::readXdgListEntry: List entry Categories in
"/usr/share/applications/cryptkeeper.desktop" is not compliant with XDG
standard (missing trailing semicolon). 
QSqlDatabasePrivate::removeDatabase: connection 'ConnectionTest' is still in
use, all queries will cease to work.
QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: Datei oder
Verzeichnis nicht gefunden
QFileSystemWatcher: failed to add paths: /home/volker/.config/ibus/bus

(digikam:2828): GStreamer-CRITICAL **: gst_debug_add_log_function: assertion
`func != NULL' failed                                                           
digikam(2828)/digikam (core) Digikam::ImageInfoJob::slotResult: Failed to list
url:  ""                                                                        
digikam(2828)/digikam (core) Digikam::ImageInfoJob::slotResult: Failed to list
url:  ""                                                                        
QSqlDatabasePrivate::removeDatabase: connection 'MigrationToDatabase175311056'
is still in use, all queries will cease to work.                                
QSqlDatabasePrivate::removeDatabase: connection 'ConnectionTest' is still in
use, all queries will cease to work.                                            
QSqlDatabasePrivate::removeDatabase: connection 'MigrationToDatabase175311056'
is still in use, all queries will cease to work.                                
QSqlDatabasePrivate::removeDatabase: connection 'ConnectionTest' is still in
use, all queries will cease to work.                                            
QSqlDatabasePrivate::removeDatabase: connection 'ConnectionTest' is still in
use, all queries will cease to work.                                            
QSqlDatabasePrivate::removeDatabase: connection 'ConnectionTest' is still in
use, all queries will cease to work.                                            
QSqlDatabasePrivate::removeDatabase: connection 'ConnectionTest' is still in
use, all queries will cease to work.                                            
QSqlDatabasePrivate::addDatabase: duplicate connection name
'PrivilegesCheckDatabase172208384', old connection removed.                     
QSqlDatabasePrivate::addDatabase: duplicate connection name
'PrivilegesCheckDatabase172208384', old connection removed.                   

Any clue? 

regards, 

Volker

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.



More information about the Digikam-devel mailing list