[digiKam-users] Using Digikam after a long, long time and launching error

Marie-Noëlle Augendre mnaugendre at gmail.com
Tue Jan 28 14:19:20 GMT 2020


Oups, sorry!

That should be this:
[marie-noelle at new-host-2 ~]$ export QT_LOGGING_RULES="digikam*=true"
[marie-noelle at new-host-2 ~]$ digikam
Attribute Qt::AA_ShareOpenGLContexts must be set before QCoreApplication is
created.
digikam.widgets: Use installed icons
digikam.general: AlbumWatch is disabled
digikam.general: Database Parameters:
   Type:                     "QSQLITE"
   DB Core Name:             "/home/marie-noelle/DK-fixe/digikam4.db"
   DB Thumbs Name:
"/home/marie-noelle/DK-fixe/thumbnails-digikam.db"
   DB Face Name:             "/home/marie-noelle/DK-fixe/recognition.db"
   DB Similarity Name:       "/home/marie-noelle/DK-fixe/similarity.db"
   Connect Options:          ""
   Host Name:                ""
   Host port:                -1
   Internal Server:          false
   Internal Server Path:     ""
   Internal Server Serv Cmd: ""
   Internal Server Init Cmd: ""
   Username:                 ""
   Password:                 ""

digikam.dbengine: Loading SQL code from config file
"/usr/share/digikam/database/dbconfig.xml"
digikam.dbengine: Checking XML version ID => expected:  3  found:  3
digikam.coredb: Core database: running schema update
digikam.coredb: Core database: have a structure version  9
digikam.coredb: Core database: makeUpdates  9  to  10
digikam.dbengine: Failure executing query:
 ""
Error messages: "Unable to execute statement" "duplicate column name:
manualOrder" "1" 2
Bound values:  ()
digikam.dbengine: Error while executing DBAction [
"UpdateSchemaFromV9ToV10" ] Statement [ "ALTER TABLE Images ADD manualOrder
INTEGER;" ]
digikam.coredb: Core database: schema update to V 10 failed!
digikam.coredb: Core database: cannot process schema initialization
digikam.general: Allowing a cache size of 195 MB
QThreadStorage: Thread 0x7f1796f640e0 exited after QThreadStorage 12
destroyed
[marie-noelle at new-host-2 ~]$

Marie-Noëlle


Le mar. 28 janv. 2020 à 15:08, Gilles Caulier <caulier.gilles at gmail.com> a
écrit :

> Thanks Marie Noel,
>
> By debug trace on the console, i want mean the trace printed by digiKam
> while running, not the gdb backtrace (in your case, there is nothing to
> read, as the application do not crash).
>
> Gilles
>
> --
  <http://marie-noelle-augendre.com>
Découvrez mes photos sur mon site <http://marie-noelle-augendre.com> ou ma
page Facebook <https://www.facebook.com/PhotographeEnCevennes?ref=bookmarks>

<http://www.blurb.fr/user/mnaugendre> <http://marie-noelle-augendre.com>
<http://www.blurb.fr/user/mnaugendre>

et tous mes livres-photos sur le site Blurb
<http://www.blurb.fr/user/mnaugendre>
<http://www.blurb.fr/user/mnaugendre>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/digikam-users/attachments/20200128/3eeab7d9/attachment.html>


More information about the Digikam-users mailing list