[digiKam-users] Error updating from 7.1 to 7.2.0

[trparks1]

I am a new user (Windows 10) who uploaded/installed 7.1.? about two weeks ago.  I uninstalled that version and installed 7.2.0 this morning per the prompts under the Install 7.2.0 executable.  I uploaded the binary files associated with redeye and facial recognition – all per the prompts and automated process.  The program seemed to be working normally but when I scrolled though the open folder I was in (Timeline sort mode), the program locked.  I waited a few minutes then force quit.  I now get the following messages when I try to restart it (the Red X message overlays the Scanning Collections one).  Please help.

\Thanks,

Tom

 

 

From: Digikam-users <[hidden email]> On Behalf Of Chris Poldervaart
Sent: Tuesday, March 30, 2021 7:55 AM
To: digiKam - Home Manage your photographs as a professional with the power of open source <[hidden email]>
Subject: [digiKam-users] Sync of new files isn't happening (7.2.0)

 

I fully admit it could be a setting or configuration I have messed up.  I have a very large library, if that helps understand.  

 

Problem: 

 

Use Import feature to import files from memory card. After downloading to the album(folder) I have selected. I can not see the images in the digiKam at all.  Previously, when I downloaded files, I would immediately be able to find them in the folder I saved them to.  They exist in the filesystem, but the DK database isn't reflecting they are there.  I even accidentally downloaded them twice so now I have duplicates of each one. 

 

Is there not a way to selectively look for new items in a specific album?  When I close and re-open digikam, it starts a new item search... but my library is pretty massive, so I don't know where it is searching..but it sits on 0% for a very long time. (I haven't seen it move yet).  Meanwhile, I still cannot access the files I just downloaded using digiKam without going straight to them in the filesystem and opening them in my external editor. 

 

Is this a bug, or am I missing something?

 

 

[mippo]

I get the same error (Failed to upload the database schema ...), with the new
7.2.0
digiKam 7.1.0 still works fine





-----
x
--
Sent from: http://digikam.1695700.n4.nabble.com/digikam-users-f1735189.html

[Maik Qualmann]

Post the DebugView log when starting digiKam-7.2.0 as described here for
Windows:

https://www.digikam.org/contribute/

Don't forget to set the environment variable.

Maik

Am Dienstag, 30. März 2021, 22:59:26 CEST schrieb mippo:

> I get the same error (Failed to upload the database schema ...), with the
> new 7.2.0
> digiKam 7.1.0 still works fine
>
>
>
>
>
> -----
> x
> --
> Sent from: http://digikam.1695700.n4.nabble.com/digikam-users-f1735189.html

[trparks1]

Thanks, Here's what I got.  
Tom
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

00000001 0.00000000 [3064] ComputerStatus - ClientRect height
361 and width 726 are NOT within 1% of screen height/width (2160,3840).
Foreground application is NOT FullScreen(window title: DebugView on
\\DESKTOP-KJBTAOE (local))
00000002 0.70061940 [3064] ComputerStatus - ClientRect height
361 and width 726 are NOT within 1% of screen height/width (2160,3840).
Foreground application is NOT FullScreen(window title: DebugView on
\\DESKTOP-KJBTAOE (local))
00000003 2.26719165 [12488] Type of item #0 of subgroup #0:
image
00000004 2.26723313 [12488] Type of item #0 of subgroup #1:
image
00000005 5.04513979 [3064] ComputerStatus - ClientRect height
960 and width 1176 are NOT within 1% of screen height/width (2160,3840).
Foreground application is NOT FullScreen(window title: Search)
00000006 5.75124598 [3064] ComputerStatus - ClientRect height
960 and width 1176 are NOT within 1% of screen height/width (2160,3840).
Foreground application is NOT FullScreen(window title: Search)
00000007 10.08820915 [3064] ComputerStatus - ClientRect height
960 and width 1176 are NOT within 1% of screen height/width (2160,3840).
Foreground application is NOT FullScreen(window title: Search)
00000008 10.79214478 [3064] ComputerStatus - ClientRect height
960 and width 1176 are NOT within 1% of screen height/width (2160,3840).
Foreground application is NOT FullScreen(window title: Search)
00000009 15.13353634 [3064] ComputerStatus - ClientRect height 0
and width 0 are NOT within 1% of screen height/width (2160,3840). Foreground
application is NOT FullScreen(window title: )
00000010 15.65248775 [22148] digikam.general: Loading DrMinGw
run-time...
00000011 15.84002113 [22148] digikam.general: DrMinGw run-time
loaded.
00000012 15.84008312 [22148] digikam.general: DrMinGw crash-file
will be located at:  "C:\\Users\\trpar\\AppData\\Local\\digikam_crash.log"

00000013 15.84726048 [22148] digikam.widgets: Breeze icons
resource file found
00000014 15.85902691 [3064] ComputerStatus - ClientRect height 0
and width 0 are NOT within 1% of screen height/width (2160,3840). Foreground
application is NOT FullScreen(window title: )
00000015 15.85928154 [22148] digikam.widgets: Breeze-dark icons
resource file found
00000016 15.87006092 [22148] QCommandLineParser: already having
an option named "?"
00000017 15.87010098 [22148] QCommandLineParser: already having
an option named "help-all"
00000018 15.87013721 [22148] QCommandLineParser: already having
an option named "v"
00000019 15.96701241 [22148] digikam.general: Switch to widget
style:  "Fusion"
00000020 15.96724033 [22148] digikam.general: AlbumWatch is
disabled
00000021 16.02808571 [22148] digikam.general: Database
Parameters:
00000022 16.02808571 [22148]    Type:
"QMYSQL"
00000023 16.02808571 [22148]    DB Core Name:
"digikam"
00000024 16.02808571 [22148]    DB Thumbs Name:
"digikam"
00000025 16.02808571 [22148]    DB Face Name:
"digikam"
00000026 16.02808571 [22148]    DB Similarity Name:
"digikam"
00000027 16.02808571 [22148]    Connect Options:          ""
00000028 16.02808571 [22148]    Host Name:
"localhost"
00000029 16.02808571 [22148]    Host port:                3307

00000030 16.02808571 [22148]    Internal Server:          true

00000031 16.02808571 [22148]    Internal Server Path:
"C:/Users/trpar/OneDrive/Documents/TRP/DIgikam Working Archive"
00000032 16.02808571 [22148]    Internal Server Serv Cmd:
"C:/Program Files/MariaDB 10.5/bin/mysqld.exe"
00000033 16.02808571 [22148]    Internal Server Init Cmd:
"C:/Program Files/MariaDB 10.5/bin/mysql_install_db.exe"
00000034 16.02808571 [22148]    Username:                 "root"

00000035 16.02808571 [22148]    Password:                 ""
00000036 16.02808571 [22148]
00000037 16.08827591 [22148] digikam.databaseserver: Database
Parameters:
00000038 16.08827591 [22148]    Type:
"QMYSQL"
00000039 16.08827591 [22148]    DB Core Name:
"digikam"
00000040 16.08827591 [22148]    DB Thumbs Name:
"digikam"
00000041 16.08827591 [22148]    DB Face Name:
"digikam"
00000042 16.08827591 [22148]    DB Similarity Name:
"digikam"
00000043 16.08827591 [22148]    Connect Options:          ""
00000044 16.08827591 [22148]    Host Name:
"localhost"
00000045 16.08827591 [22148]    Host port:                3307

00000046 16.08827591 [22148]    Internal Server:          true

00000047 16.08827591 [22148]    Internal Server Path:
"C:/Users/trpar/OneDrive/Documents/TRP/DIgikam Working Archive"
00000048 16.08827591 [22148]    Internal Server Serv Cmd:
"C:/Program Files/MariaDB 10.5/bin/mysqld.exe"
00000049 16.08827591 [22148]    Internal Server Init Cmd:
"C:/Program Files/MariaDB 10.5/bin/mysql_install_db.exe"
00000050 16.08827591 [22148]    Username:                 "root"

00000051 16.08827591 [22148]    Password:                 ""
00000052 16.08827591 [22148]
00000053 16.08830643 [22148] digikam.databaseserver: Internal
Server data path: "C:/Users/trpar/OneDrive/Documents/TRP/DIgikam Working
Archive/.mysql.digikam/db_data"
00000054 16.09058952 [22148] digikam.databaseserver: The mysql
configuration was already up-to-date:
"C:/Users/trpar/AppData/Local/digikam/mysql.conf"
00000055 16.12656593 [22148] digikam.databaseserver: Database
server: "C:/Program Files/MariaDB 10.5/bin/mysqld.exe"
("--defaults-file=C:\\Users\\trpar\\AppData\\Local\\digikam\\mysql.conf",
"--datadir=C:\\Users\\trpar\\OneDrive\\Documents\\TRP\\DIgikam Working
Archive\\.mysql.digikam\\db_data", "--skip-networking=0", "--port=3307")

00000056 17.20185661 [22148] digikam.databaseserver: Internal
database server started
00000057 17.20248604 [22148] digikam.databaseserver: Running 0
seconds...
00000058 19.36081696 [22148] digikam.dbengine: Loading SQL code
from config file "C:/Program
Files/digiKam/data/digikam/database/dbconfig.xml"
00000059 19.37292099 [22148] digikam.dbengine: Checking XML
version ID => expected:  3  found:  3
00000060 19.38085747 [22148] digikam.coredb: Core database:
running schema update
00000061 20.06405830 [22148] digikam.coredb: Core database: have
a structure version  10
00000062 20.06412888 [22148] digikam.coredb: Core database:
makeUpdates  10  to  12
00000063 20.11470795 [22148] digikam.dbengine: Failure executing
query:
00000064 20.11470795 [22148]  ""
00000065 20.11470795 [22148] Error messages: "QMYSQL: Unable to
execute query" "Table 'tags' is marked as crashed and should be repaired"
"1194" 2
00000066 20.11470795 [22148] Bound values:  ()
00000067 20.11476326 [22148] digikam.dbengine: Error while
executing DBAction [ "UpdateSchemaFromV10ToV11" ] Statement [ "DROP TRIGGER
IF EXISTS insert_tagstree;" ]
00000068 20.11480331 [22148] digikam.coredb: Core database:
schema update to V 11 failed!
00000069 20.12067413 [22148] digikam.coredb: Core database:
cannot process schema initialization
00000070 20.19192123 [3064] ComputerStatus - ClientRect height 0
and width 0 are NOT within 1% of screen height/width (2160,3840). Foreground
application is NOT FullScreen(window title: )
00000071 20.92267609 [3064] ComputerStatus - ClientRect height
195 and width 334 are NOT within 1% of screen height/width (2160,3840).
Foreground application is NOT FullScreen(window title: digiKam)
00000072 25.23541641 [3064] ComputerStatus - ClientRect height
195 and width 334 are NOT within 1% of screen height/width (2160,3840).
Foreground application is NOT FullScreen(window title: digiKam)
00000073 25.96375275 [3064] ComputerStatus - ClientRect height
195 and width 334 are NOT within 1% of screen height/width (2160,3840).
Foreground application is NOT FullScreen(window title: digiKam)
00000074 26.48803711 [22148] digikam.general: KMemoryInfo:
Platform identified :  "WINDOWS"
00000075 26.48828888 [22148] digikam.general: KMemoryInfo:
TotalRam:  16976605184
00000076 26.49112892 [22148] digikam.general: Allowing a cache
size of 200 MB
00000077 28.33336258 [22148] digikam.databaseserver: Shutting
down database server
00000078 28.33432388 [22148] digikam.databaseserver: Internal
database server stopped
00000079 28.41195488 [22148] QThreadStorage: Thread 0x9b96250
exited after QThreadStorage 7 destroyed
00000080 28.41222382 [22148] QWaitCondition: Destroyed while
threads are still waiting

-----Original Message-----
From: Digikam-users <[hidden email]> On Behalf Of Maik
Qualmann
Sent: Tuesday, March 30, 2021 2:07 PM
To: digiKam - Home Manage your photographs as a professional with the power
of open source <[hidden email]>
Subject: Re: [digiKam-users] Error updating from 7.1 to 7.2.0

Post the DebugView log when starting digiKam-7.2.0 as described here for
Windows:

https://www.digikam.org/contribute/

Don't forget to set the environment variable.

Maik

Am Dienstag, 30. März 2021, 22:59:26 CEST schrieb mippo:

> I get the same error (Failed to upload the database schema ...), with
> the new 7.2.0 digiKam 7.1.0 still works fine
>
>
>
>
>
> -----
> x
> --
> Sent from:
> http://digikam.1695700.n4.nabble.com/digikam-users-f1735189.html

[Maik Qualmann]

You use digiKam's internal MySQL server. In digiKam-7.1.0, when exiting
digiKam, the internal server was not shut down correctly under Windows. This
could damage the database. This is the case with you, therefore the schema
update to a new structure does not work:

-----------------------------------------
> Error messages: "QMYSQL: Unable to
> execute query" "Table 'tags' is marked as crashed and should be repaired"
> "1194" 2

> digikam.dbengine: Error while
> executing DBAction [ "UpdateSchemaFromV10ToV11" ] Statement [ "DROP TRIGGER
> IF EXISTS insert_tagstree;" ]
-----------------------------------------

The best way is to start with a new database. To do this, you have to delete
the "C:\Users\trpar\OneDrive\Documents\TRP\DIgikam Working
Archive\.mysql.digikam" folder.

Rescuing the database is more difficult. With digiKam-7.1.0 you would have to
copy the database with the migration tool into an SQLite database and then
back again later.

Maik

Am Dienstag, 30. März 2021, 23:56:51 CEST schrieb [hidden email]:
> Thanks, Here's what I got.
> Tom

> 00000065 20.11470795 [22148] Error messages: "QMYSQL: Unable to
> execute query" "Table 'tags' is marked as crashed and should be repaired"
> "1194" 2
> 00000066 20.11470795 [22148] Bound values:  ()
> 00000067 20.11476326 [22148] digikam.dbengine: Error while
> executing DBAction [ "UpdateSchemaFromV10ToV11" ] Statement [ "DROP TRIGGER
> IF EXISTS insert_tagstree;" ]

> -----Original Message-----
> From: Digikam-users <[hidden email]> On Behalf Of Maik
> Qualmann
> Sent: Tuesday, March 30, 2021 2:07 PM
> To: digiKam - Home Manage your photographs as a professional with the power
> of open source <[hidden email]>
> Subject: Re: [digiKam-users] Error updating from 7.1 to 7.2.0
>
> Post the DebugView log when starting digiKam-7.2.0 as described here for
> Windows:
>
> https://www.digikam.org/contribute/
>
> Don't forget to set the environment variable.
>
> Maik
>
> Am Dienstag, 30. März 2021, 22:59:26 CEST schrieb mippo:
> > I get the same error (Failed to upload the database schema ...), with
> > the new 7.2.0 digiKam 7.1.0 still works fine
> >
> >
> >
> >
> >
> > -----
> > x
> > --
> > Sent from:
> > http://digikam.1695700.n4.nabble.com/digikam-users-f1735189.html

[mippo]

Maik,
I get the following:

-- digiKam Linux AppImage Bundle
-- Use 'help' as CLI argument to know all available options for digiKam
application.
-- Notes: to integrate this bundle to your desktop, use AppImageLauncher.
--        to enable all debug messages on the console, use 'export
QT_LOGGING_RULES="digikam*=true"'.
libudev.so.0
libxcb-dri3.so.0
-- Preloading shared libs: :/usr/lib/x86_64-linux-gnu/libxcb-dri3.so.0
Digikam::CoreDbAccess::checkReadyForUse: Core database: cannot process
schema initialization

running KDE Neon and MariaDB on NAS




-----
x
--
Sent from: http://digikam.1695700.n4.nabble.com/digikam-users-f1735189.html

[trparks1]

Maik or anybody,
I continue to have database problems with MySQL server under windows 10
after migrating from 7.1 to 7.2.0.  I had followed your instructions below
and it worked (apparently, the program re-installed MYSQL after deleting it)
for maybe a half dozen sessions with no noticeable problems.  Then it
started freezing again on startup with the DebugView log showing database
server errors.  I am a new user and have just started to build my database
and so it wouldn't be a huge loss to replace it with SQLite if that would be
more robust (from what I've read I suspect it would be).  I had initialized
the program with MYSQL as the documentation indicated it may be better
suited for large archives, but I think mine will eventually top out at
something like 100-150 images and suspect that won't overburden SQLite.  I
am no power user and don't want to have ongoing issues with a finicky
system.

If you don't see any problems with this could you please point me to
instructions on how I switch to Lite?

Thanks,
Tom

-----Original Message-----
From: Digikam-users <[hidden email]> On Behalf Of Maik
Qualmann
Sent: Tuesday, March 30, 2021 10:40 PM
To: digiKam - Home Manage your photographs as a professional with the power
of open source <[hidden email]>
Subject: Re: [digiKam-users] Error updating from 7.1 to 7.2.0

You use digiKam's internal MySQL server. In digiKam-7.1.0, when exiting
digiKam, the internal server was not shut down correctly under Windows. This
could damage the database. This is the case with you, therefore the schema
update to a new structure does not work:

-----------------------------------------
> Error messages: "QMYSQL: Unable to
> execute query" "Table 'tags' is marked as crashed and should be repaired"
> "1194" 2

> digikam.dbengine: Error while
> executing DBAction [ "UpdateSchemaFromV10ToV11" ] Statement [ "DROP
> TRIGGER IF EXISTS insert_tagstree;" ]
-----------------------------------------

The best way is to start with a new database. To do this, you have to delete
the "C:\Users\trpar\OneDrive\Documents\TRP\DIgikam Working
Archive\.mysql.digikam" folder.

Rescuing the database is more difficult. With digiKam-7.1.0 you would have
to copy the database with the migration tool into an SQLite database and
then back again later.

Maik

Am Dienstag, 30. März 2021, 23:56:51 CEST schrieb [hidden email]:
> Thanks, Here's what I got.
> Tom

> 00000065 20.11470795 [22148] Error messages: "QMYSQL: Unable to
> execute query" "Table 'tags' is marked as crashed and should be repaired"
> "1194" 2
> 00000066 20.11470795 [22148] Bound values:  ()
> 00000067 20.11476326 [22148] digikam.dbengine: Error while
> executing DBAction [ "UpdateSchemaFromV10ToV11" ] Statement [ "DROP
> TRIGGER IF EXISTS insert_tagstree;" ]

> -----Original Message-----
> From: Digikam-users <[hidden email]> On Behalf Of Maik
> Qualmann
> Sent: Tuesday, March 30, 2021 2:07 PM
> To: digiKam - Home Manage your photographs as a professional with the
> power of open source <[hidden email]>
> Subject: Re: [digiKam-users] Error updating from 7.1 to 7.2.0
>
> Post the DebugView log when starting digiKam-7.2.0 as described here
> for
> Windows:
>
> https://www.digikam.org/contribute/
>
> Don't forget to set the environment variable.
>
> Maik
>
> Am Dienstag, 30. März 2021, 22:59:26 CEST schrieb mippo:
> > I get the same error (Failed to upload the database schema ...),
> > with the new 7.2.0 digiKam 7.1.0 still works fine
> >
> >
> >
> >
> >
> > -----
> > x
> > --
> > Sent from:
> > http://digikam.1695700.n4.nabble.com/digikam-users-f1735189.html

[mippo]

hello,
I would attempt the "more difficult" solution, the migration from MySQL
server into an SQLite, that should be the original internal DB.
After 5 hours working, it only creates a 170MB file, named digikam4.db into
the destination folder.
But nothing else, everything remain the same, digiKam still working in the
remote MySQL server, instead of SQlite.


My idea, is to import databases, into digiKam 7.1 SQlite, update to digiKam
7.2, update to MariaDB 10.5.9, update phpMyAdmin (or DBeaver), and then move
Databases again in MySQL (MariaDB).


do you believe this possible ...?


thanks
mippo




-----
x
--
Sent from: http://digikam.1695700.n4.nabble.com/digikam-users-f1735189.html