[digiKam-users] Database schema update problem

classic Classic list List threaded Threaded
7 messages Options
Reply | Threaded
Open this post in threaded view
|

[digiKam-users] Database schema update problem

sse450
Dear all,

I am a happy user of digikam through digikam-7.1.0-x86-64.appimage and
mysql database on network.

I wanted to upgrade to 7.2.0, but all I get is "failed to update the
database schema from version 10 to 11".

Could you please help me sort this issue out.

Thank you

Mufit

Reply | Threaded
Open this post in threaded view
|

Re: Database schema update problem

Maik Qualmann
Post the debug output from the terminal with the debug environment variable
enabled, as described here:

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

Maik

Am Sonntag, 11. April 2021, 08:33:21 CEST schrieb OzyMate:

> Dear all,
>
> I am a happy user of digikam through digikam-7.1.0-x86-64.appimage and
> mysql database on network.
>
> I wanted to upgrade to 7.2.0, but all I get is "failed to update the
> database schema from version 10 to 11".
>
> Could you please help me sort this issue out.
>
> Thank you
>
> Mufit




Reply | Threaded
Open this post in threaded view
|

Re: Database schema update problem

sse450

Dear Maik,

I run with debug switch. Here is the result:

mufit@P17SM:~/Pictures/digikam-mufit$ ./digiKam-7.2.0-x86-64.appimage debug
Setting $HOME to /home/mufit/Pictures/digikam-mufit/digiKam-7.2.0-x86-64.appimage.home
-- 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
Starting digiKam into GDB...
Use 'bt' command on debugger prompt to get a crash backtrace.
Use 'q' command to quit debugger session.
GNU gdb (Ubuntu 9.2-0ubuntu1~20.04) 9.2
Copyright (C) 2020 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
    <http://www.gnu.org/software/gdb/documentation/>.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from digikam...
(No debugging symbols found in digikam)
Starting program: /tmp/.mount_digiKaHP7SAM/usr/bin/digikam
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffd4a5f700 (LWP 94782)]
[New Thread 0x7fffcc423700 (LWP 94783)]
[New Thread 0x7fffcbc22700 (LWP 94784)]
[New Thread 0x7fffcae4a700 (LWP 94785)]
[Thread 0x7fffcae4a700 (LWP 94785) exited]
Digikam::CoreDbAccess::checkReadyForUse: Core database: cannot process schema initialization
[Thread 0x7fffd4a5f700 (LWP 94782) exited]
[Thread 0x7fffcbc22700 (LWP 94784) exited]
[Thread 0x7fffcc423700 (LWP 94783) exited]
--Type <RET> for more, q to quit, c to continue without paging--
[Inferior 1 (process 94778) exited normally]
(gdb) bt
No stack.
(gdb) quit

Two windows pop up:

errordatabase


On 11.04.21 09:51, Maik Qualmann wrote:
Post the debug output from the terminal with the debug environment variable 
enabled, as described here: 

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

Maik

Am Sonntag, 11. April 2021, 08:33:21 CEST schrieb OzyMate:
Dear all,

I am a happy user of digikam through digikam-7.1.0-x86-64.appimage and
mysql database on network.

I wanted to upgrade to 7.2.0, but all I get is "failed to update the
database schema from version 10 to 11".

Could you please help me sort this issue out.

Thank you

Mufit



Reply | Threaded
Open this post in threaded view
|

Re: Database schema update problem

Maik Qualmann
No, the debug mode is not necessary, just set the environment variable to make
digiKam more talkative:

export QT_LOGGING_RULES="digikam*=true"

Maik

Am Sonntag, 11. April 2021, 11:20:52 CEST schrieb OzyMate:

> Dear Maik,
>
> I run with debug switch. Here is the result:
>
> mufit@P17SM:~/Pictures/digikam-mufit$ ./digiKam-7.2.0-x86-64.appimage debug
> Setting $HOME to
> /home/mufit/Pictures/digikam-mufit/digiKam-7.2.0-x86-64.appimage.home
> -- 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
> Starting digiKam into GDB...
> Use 'bt' command on debugger prompt to get a crash backtrace.
> Use 'q' command to quit debugger session.
> GNU gdb (Ubuntu 9.2-0ubuntu1~20.04) 9.2
> Copyright (C) 2020 Free Software Foundation, Inc.
> License GPLv3+: GNU GPL version 3 or later
> <http://gnu.org/licenses/gpl.html>
> This is free software: you are free to change and redistribute it.
> There is NO WARRANTY, to the extent permitted by law.
> Type "show copying" and "show warranty" for details.
> This GDB was configured as "x86_64-linux-gnu".
> Type "show configuration" for configuration details.
> For bug reporting instructions, please see:
> <http://www.gnu.org/software/gdb/bugs/>.
> Find the GDB manual and other documentation resources online at:
>      <http://www.gnu.org/software/gdb/documentation/>.
>
> For help, type "help".
> Type "apropos word" to search for commands related to "word"...
> Reading symbols from digikam...
> (No debugging symbols found in digikam)
> Starting program: /tmp/.mount_digiKaHP7SAM/usr/bin/digikam
> [Thread debugging using libthread_db enabled]
> Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
> [New Thread 0x7fffd4a5f700 (LWP 94782)]
> [New Thread 0x7fffcc423700 (LWP 94783)]
> [New Thread 0x7fffcbc22700 (LWP 94784)]
> [New Thread 0x7fffcae4a700 (LWP 94785)]
> [Thread 0x7fffcae4a700 (LWP 94785) exited]
> Digikam::CoreDbAccess::checkReadyForUse: Core database: cannot process
> schema initialization
> [Thread 0x7fffd4a5f700 (LWP 94782) exited]
> [Thread 0x7fffcbc22700 (LWP 94784) exited]
> [Thread 0x7fffcc423700 (LWP 94783) exited]
> --Type <RET> for more, q to quit, c to continue without paging--
> [Inferior 1 (process 94778) exited normally]
> (gdb) bt
> No stack.
> (gdb) quit
>
> Two windows pop up:
>
> errordatabase
>
> On 11.04.21 09:51, Maik Qualmann wrote:
> > Post the debug output from the terminal with the debug environment
> > variable
> > enabled, as described here:
> >
> > https://www.digikam.org/contribute/
> >
> > Maik
> >
> > Am Sonntag, 11. April 2021, 08:33:21 CEST schrieb OzyMate:
> >> Dear all,
> >>
> >> I am a happy user of digikam through digikam-7.1.0-x86-64.appimage and
> >> mysql database on network.
> >>
> >> I wanted to upgrade to 7.2.0, but all I get is "failed to update the
> >> database schema from version 10 to 11".
> >>
> >> Could you please help me sort this issue out.
> >>
> >> Thank you
> >>
> >> Mufit




Reply | Threaded
Open this post in threaded view
|

Re: Database schema update problem

sse450
Maik, here it is.

I am not sure, but as a guess, I wanted to try mysql root
login/password. But, the problem is I cannot get the digikam window to
change the mysql credentials.

What is your advice, please?

Thank you.

mufit@P17SM:~/Pictures/digikam-mufit$ ./digiKam-7.2.0-x86-64.appimage
Setting $HOME to
/home/mufit/Pictures/digikam-mufit/digiKam-7.2.0-x86-64.appimage.home
-- 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::DXmlGuiWindow::setupIconTheme: Breeze icons resource file found
Digikam::DXmlGuiWindow::setupIconTheme: Breeze-dark icons resource file
found
Digikam::AlbumWatch::AlbumWatch: AlbumWatch is disabled
Digikam::AlbumManager::setDatabase: Database Parameters:
    Type:                     "QMYSQL"
    DB Core Name:             "digikam_mufit"
    DB Thumbs Name:           "digikam_mufit"
    DB Face Name:             "digikam_mufit"
    DB Similarity Name:       "digikam_mufit"
    Connect Options:          ""
    Host Name:                "192.168.2.10"
    Host port:                3306
    Internal Server:          false
    Internal Server Path:     ""
    Internal Server Serv Cmd: ""
    Internal Server Init Cmd: ""
    Username:                 "sse450"
    Password:                 "XXXXXXXX"

Digikam::DbEngineConfigSettingsLoader::readConfig: Loading SQL code from
config file
"/tmp/.mount_digiKawxxUcI/usr/share/digikam/database/dbconfig.xml"
Digikam::DbEngineConfigSettingsLoader::readConfig: Checking XML version
ID => expected:  3  found:  3
Digikam::CoreDbSchemaUpdater::update: Core database: running schema update
Digikam::CoreDbSchemaUpdater::startUpdates: Core database: have a
structure version  10
Digikam::CoreDbSchemaUpdater::makeUpdates: Core database: makeUpdates 
10  to  12
Digikam::BdEngineBackendPrivate::debugOutputFailedQuery: Failure
executing query:
  ""
Error messages: "QMYSQL: Unable to execute query" "You do not have the
SUPER privilege and binary logging is enabled (you *might* want to use
the less safe log_bin_trust_function_creators variable)" "1419" 2
Bound values:  ()
Digikam::BdEngineBackend::execDBAction: Error while executing DBAction [
"UpdateSchemaFromV10ToV11" ] Statement [ "DROP TRIGGER IF EXISTS
temp_insert_tagstree;" ]
Digikam::CoreDbSchemaUpdater::performUpdateToVersion: Core database:
schema update to V 11 failed!
Digikam::CoreDbAccess::checkReadyForUse: Core database: cannot process
schema initialization
Digikam::KMemoryInfo::update: KMemoryInfo: Platform identified :  "LINUX"
Digikam::KMemoryInfo::bytes: KMemoryInfo: TotalRam:  16701681664
Digikam::LoadingCache::setCacheSize: Allowing a cache size of 200 MB
mufit@P17SM:~/Pictures/digikam-mufit$

On 11.04.21 12:52, Maik Qualmann wrote:

> No, the debug mode is not necessary, just set the environment variable to make
> digiKam more talkative:
>
> export QT_LOGGING_RULES="digikam*=true"
>
> Maik
>
> Am Sonntag, 11. April 2021, 11:20:52 CEST schrieb OzyMate:
>> Dear Maik,
>>
>> I run with debug switch. Here is the result:
>>
>> mufit@P17SM:~/Pictures/digikam-mufit$ ./digiKam-7.2.0-x86-64.appimage debug
>> Setting $HOME to
>> /home/mufit/Pictures/digikam-mufit/digiKam-7.2.0-x86-64.appimage.home
>> -- 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
>> Starting digiKam into GDB...
>> Use 'bt' command on debugger prompt to get a crash backtrace.
>> Use 'q' command to quit debugger session.
>> GNU gdb (Ubuntu 9.2-0ubuntu1~20.04) 9.2
>> Copyright (C) 2020 Free Software Foundation, Inc.
>> License GPLv3+: GNU GPL version 3 or later
>> <http://gnu.org/licenses/gpl.html>
>> This is free software: you are free to change and redistribute it.
>> There is NO WARRANTY, to the extent permitted by law.
>> Type "show copying" and "show warranty" for details.
>> This GDB was configured as "x86_64-linux-gnu".
>> Type "show configuration" for configuration details.
>> For bug reporting instructions, please see:
>> <http://www.gnu.org/software/gdb/bugs/>.
>> Find the GDB manual and other documentation resources online at:
>>       <http://www.gnu.org/software/gdb/documentation/>.
>>
>> For help, type "help".
>> Type "apropos word" to search for commands related to "word"...
>> Reading symbols from digikam...
>> (No debugging symbols found in digikam)
>> Starting program: /tmp/.mount_digiKaHP7SAM/usr/bin/digikam
>> [Thread debugging using libthread_db enabled]
>> Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
>> [New Thread 0x7fffd4a5f700 (LWP 94782)]
>> [New Thread 0x7fffcc423700 (LWP 94783)]
>> [New Thread 0x7fffcbc22700 (LWP 94784)]
>> [New Thread 0x7fffcae4a700 (LWP 94785)]
>> [Thread 0x7fffcae4a700 (LWP 94785) exited]
>> Digikam::CoreDbAccess::checkReadyForUse: Core database: cannot process
>> schema initialization
>> [Thread 0x7fffd4a5f700 (LWP 94782) exited]
>> [Thread 0x7fffcbc22700 (LWP 94784) exited]
>> [Thread 0x7fffcc423700 (LWP 94783) exited]
>> --Type <RET> for more, q to quit, c to continue without paging--
>> [Inferior 1 (process 94778) exited normally]
>> (gdb) bt
>> No stack.
>> (gdb) quit
>>
>> Two windows pop up:
>>
>> errordatabase
>>
>> On 11.04.21 09:51, Maik Qualmann wrote:
>>> Post the debug output from the terminal with the debug environment
>>> variable
>>> enabled, as described here:
>>>
>>> https://www.digikam.org/contribute/
>>>
>>> Maik
>>>
>>> Am Sonntag, 11. April 2021, 08:33:21 CEST schrieb OzyMate:
>>>> Dear all,
>>>>
>>>> I am a happy user of digikam through digikam-7.1.0-x86-64.appimage and
>>>> mysql database on network.
>>>>
>>>> I wanted to upgrade to 7.2.0, but all I get is "failed to update the
>>>> database schema from version 10 to 11".
>>>>
>>>> Could you please help me sort this issue out.
>>>>
>>>> Thank you
>>>>
>>>> Mufit
>
>
>
Reply | Threaded
Open this post in threaded view
|

Re: Database schema update problem

Maik Qualmann
See this bug report for the solution:

https://bugs.kde.org/show_bug.cgi?id=435065#c8

Maik

Am Sonntag, 11. April 2021, 15:39:47 CEST schrieb OzyMate:

> Maik, here it is.
>
> I am not sure, but as a guess, I wanted to try mysql root
> login/password. But, the problem is I cannot get the digikam window to
> change the mysql credentials.
>
> What is your advice, please?
>
> Thank you.
>
> mufit@P17SM:~/Pictures/digikam-mufit$ ./digiKam-7.2.0-x86-64.appimage
> Setting $HOME to
> /home/mufit/Pictures/digikam-mufit/digiKam-7.2.0-x86-64.appimage.home
> -- 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::DXmlGuiWindow::setupIconTheme: Breeze icons resource file found
> Digikam::DXmlGuiWindow::setupIconTheme: Breeze-dark icons resource file
> found
> Digikam::AlbumWatch::AlbumWatch: AlbumWatch is disabled
> Digikam::AlbumManager::setDatabase: Database Parameters:
>     Type:                     "QMYSQL"
>     DB Core Name:             "digikam_mufit"
>     DB Thumbs Name:           "digikam_mufit"
>     DB Face Name:             "digikam_mufit"
>     DB Similarity Name:       "digikam_mufit"
>     Connect Options:          ""
>     Host Name:                "192.168.2.10"
>     Host port:                3306
>     Internal Server:          false
>     Internal Server Path:     ""
>     Internal Server Serv Cmd: ""
>     Internal Server Init Cmd: ""
>     Username:                 "sse450"
>     Password:                 "XXXXXXXX"
>
> Digikam::DbEngineConfigSettingsLoader::readConfig: Loading SQL code from
> config file
> "/tmp/.mount_digiKawxxUcI/usr/share/digikam/database/dbconfig.xml"
> Digikam::DbEngineConfigSettingsLoader::readConfig: Checking XML version
> ID => expected:  3  found:  3
> Digikam::CoreDbSchemaUpdater::update: Core database: running schema update
> Digikam::CoreDbSchemaUpdater::startUpdates: Core database: have a
> structure version  10
> Digikam::CoreDbSchemaUpdater::makeUpdates: Core database: makeUpdates
> 10  to  12
> Digikam::BdEngineBackendPrivate::debugOutputFailedQuery: Failure
> executing query:
>   ""
> Error messages: "QMYSQL: Unable to execute query" "You do not have the
> SUPER privilege and binary logging is enabled (you *might* want to use
> the less safe log_bin_trust_function_creators variable)" "1419" 2
> Bound values:  ()
> Digikam::BdEngineBackend::execDBAction: Error while executing DBAction [
> "UpdateSchemaFromV10ToV11" ] Statement [ "DROP TRIGGER IF EXISTS
> temp_insert_tagstree;" ]
> Digikam::CoreDbSchemaUpdater::performUpdateToVersion: Core database:
> schema update to V 11 failed!
> Digikam::CoreDbAccess::checkReadyForUse: Core database: cannot process
> schema initialization
> Digikam::KMemoryInfo::update: KMemoryInfo: Platform identified :  "LINUX"
> Digikam::KMemoryInfo::bytes: KMemoryInfo: TotalRam:  16701681664
> Digikam::LoadingCache::setCacheSize: Allowing a cache size of 200 MB
> mufit@P17SM:~/Pictures/digikam-mufit$
>
> On 11.04.21 12:52, Maik Qualmann wrote:
> > No, the debug mode is not necessary, just set the environment variable to
> > make digiKam more talkative:
> >
> > export QT_LOGGING_RULES="digikam*=true"
> >
> > Maik
> >
> > Am Sonntag, 11. April 2021, 11:20:52 CEST schrieb OzyMate:
> >> Dear Maik,
> >>
> >> I run with debug switch. Here is the result:
> >>
> >> mufit@P17SM:~/Pictures/digikam-mufit$ ./digiKam-7.2.0-x86-64.appimage
> >> debug
> >> Setting $HOME to
> >> /home/mufit/Pictures/digikam-mufit/digiKam-7.2.0-x86-64.appimage.home
> >> -- 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
> >> Starting digiKam into GDB...
> >> Use 'bt' command on debugger prompt to get a crash backtrace.
> >> Use 'q' command to quit debugger session.
> >> GNU gdb (Ubuntu 9.2-0ubuntu1~20.04) 9.2
> >> Copyright (C) 2020 Free Software Foundation, Inc.
> >> License GPLv3+: GNU GPL version 3 or later
> >> <http://gnu.org/licenses/gpl.html>
> >> This is free software: you are free to change and redistribute it.
> >> There is NO WARRANTY, to the extent permitted by law.
> >> Type "show copying" and "show warranty" for details.
> >> This GDB was configured as "x86_64-linux-gnu".
> >> Type "show configuration" for configuration details.
> >> For bug reporting instructions, please see:
> >> <http://www.gnu.org/software/gdb/bugs/>.
> >>
> >> Find the GDB manual and other documentation resources online at:
> >>       <http://www.gnu.org/software/gdb/documentation/>.
> >>
> >> For help, type "help".
> >> Type "apropos word" to search for commands related to "word"...
> >> Reading symbols from digikam...
> >> (No debugging symbols found in digikam)
> >> Starting program: /tmp/.mount_digiKaHP7SAM/usr/bin/digikam
> >> [Thread debugging using libthread_db enabled]
> >> Using host libthread_db library
> >> "/lib/x86_64-linux-gnu/libthread_db.so.1".
> >> [New Thread 0x7fffd4a5f700 (LWP 94782)]
> >> [New Thread 0x7fffcc423700 (LWP 94783)]
> >> [New Thread 0x7fffcbc22700 (LWP 94784)]
> >> [New Thread 0x7fffcae4a700 (LWP 94785)]
> >> [Thread 0x7fffcae4a700 (LWP 94785) exited]
> >> Digikam::CoreDbAccess::checkReadyForUse: Core database: cannot process
> >> schema initialization
> >> [Thread 0x7fffd4a5f700 (LWP 94782) exited]
> >> [Thread 0x7fffcbc22700 (LWP 94784) exited]
> >> [Thread 0x7fffcc423700 (LWP 94783) exited]
> >> --Type <RET> for more, q to quit, c to continue without paging--
> >> [Inferior 1 (process 94778) exited normally]
> >> (gdb) bt
> >> No stack.
> >> (gdb) quit
> >>
> >> Two windows pop up:
> >>
> >> errordatabase
> >>
> >> On 11.04.21 09:51, Maik Qualmann wrote:
> >>> Post the debug output from the terminal with the debug environment
> >>> variable
> >>> enabled, as described here:
> >>>
> >>> https://www.digikam.org/contribute/
> >>>
> >>> Maik
> >>>
> >>> Am Sonntag, 11. April 2021, 08:33:21 CEST schrieb OzyMate:
> >>>> Dear all,
> >>>>
> >>>> I am a happy user of digikam through digikam-7.1.0-x86-64.appimage and
> >>>> mysql database on network.
> >>>>
> >>>> I wanted to upgrade to 7.2.0, but all I get is "failed to update the
> >>>> database schema from version 10 to 11".
> >>>>
> >>>> Could you please help me sort this issue out.
> >>>>
> >>>> Thank you
> >>>>
> >>>> Mufit




Reply | Threaded
Open this post in threaded view
|

Re: Database schema update problem

sse450
All fixed.

Thank you very much.

Mufit

On 11.04.21 17:08, Maik Qualmann wrote:

> See this bug report for the solution:
>
> https://bugs.kde.org/show_bug.cgi?id=435065#c8
>
> Maik
>
> Am Sonntag, 11. April 2021, 15:39:47 CEST schrieb OzyMate:
>> Maik, here it is.
>>
>> I am not sure, but as a guess, I wanted to try mysql root
>> login/password. But, the problem is I cannot get the digikam window to
>> change the mysql credentials.
>>
>> What is your advice, please?
>>
>> Thank you.
>>
>> mufit@P17SM:~/Pictures/digikam-mufit$ ./digiKam-7.2.0-x86-64.appimage
>> Setting $HOME to
>> /home/mufit/Pictures/digikam-mufit/digiKam-7.2.0-x86-64.appimage.home
>> -- 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::DXmlGuiWindow::setupIconTheme: Breeze icons resource file found
>> Digikam::DXmlGuiWindow::setupIconTheme: Breeze-dark icons resource file
>> found
>> Digikam::AlbumWatch::AlbumWatch: AlbumWatch is disabled
>> Digikam::AlbumManager::setDatabase: Database Parameters:
>>      Type:                     "QMYSQL"
>>      DB Core Name:             "digikam_mufit"
>>      DB Thumbs Name:           "digikam_mufit"
>>      DB Face Name:             "digikam_mufit"
>>      DB Similarity Name:       "digikam_mufit"
>>      Connect Options:          ""
>>      Host Name:                "192.168.2.10"
>>      Host port:                3306
>>      Internal Server:          false
>>      Internal Server Path:     ""
>>      Internal Server Serv Cmd: ""
>>      Internal Server Init Cmd: ""
>>      Username:                 "sse450"
>>      Password:                 "XXXXXXXX"
>>
>> Digikam::DbEngineConfigSettingsLoader::readConfig: Loading SQL code from
>> config file
>> "/tmp/.mount_digiKawxxUcI/usr/share/digikam/database/dbconfig.xml"
>> Digikam::DbEngineConfigSettingsLoader::readConfig: Checking XML version
>> ID => expected:  3  found:  3
>> Digikam::CoreDbSchemaUpdater::update: Core database: running schema update
>> Digikam::CoreDbSchemaUpdater::startUpdates: Core database: have a
>> structure version  10
>> Digikam::CoreDbSchemaUpdater::makeUpdates: Core database: makeUpdates
>> 10  to  12
>> Digikam::BdEngineBackendPrivate::debugOutputFailedQuery: Failure
>> executing query:
>>    ""
>> Error messages: "QMYSQL: Unable to execute query" "You do not have the
>> SUPER privilege and binary logging is enabled (you *might* want to use
>> the less safe log_bin_trust_function_creators variable)" "1419" 2
>> Bound values:  ()
>> Digikam::BdEngineBackend::execDBAction: Error while executing DBAction [
>> "UpdateSchemaFromV10ToV11" ] Statement [ "DROP TRIGGER IF EXISTS
>> temp_insert_tagstree;" ]
>> Digikam::CoreDbSchemaUpdater::performUpdateToVersion: Core database:
>> schema update to V 11 failed!
>> Digikam::CoreDbAccess::checkReadyForUse: Core database: cannot process
>> schema initialization
>> Digikam::KMemoryInfo::update: KMemoryInfo: Platform identified :  "LINUX"
>> Digikam::KMemoryInfo::bytes: KMemoryInfo: TotalRam:  16701681664
>> Digikam::LoadingCache::setCacheSize: Allowing a cache size of 200 MB
>> mufit@P17SM:~/Pictures/digikam-mufit$
>>
>> On 11.04.21 12:52, Maik Qualmann wrote:
>>> No, the debug mode is not necessary, just set the environment variable to
>>> make digiKam more talkative:
>>>
>>> export QT_LOGGING_RULES="digikam*=true"
>>>
>>> Maik
>>>
>>> Am Sonntag, 11. April 2021, 11:20:52 CEST schrieb OzyMate:
>>>> Dear Maik,
>>>>
>>>> I run with debug switch. Here is the result:
>>>>
>>>> mufit@P17SM:~/Pictures/digikam-mufit$ ./digiKam-7.2.0-x86-64.appimage
>>>> debug
>>>> Setting $HOME to
>>>> /home/mufit/Pictures/digikam-mufit/digiKam-7.2.0-x86-64.appimage.home
>>>> -- 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
>>>> Starting digiKam into GDB...
>>>> Use 'bt' command on debugger prompt to get a crash backtrace.
>>>> Use 'q' command to quit debugger session.
>>>> GNU gdb (Ubuntu 9.2-0ubuntu1~20.04) 9.2
>>>> Copyright (C) 2020 Free Software Foundation, Inc.
>>>> License GPLv3+: GNU GPL version 3 or later
>>>> <http://gnu.org/licenses/gpl.html>
>>>> This is free software: you are free to change and redistribute it.
>>>> There is NO WARRANTY, to the extent permitted by law.
>>>> Type "show copying" and "show warranty" for details.
>>>> This GDB was configured as "x86_64-linux-gnu".
>>>> Type "show configuration" for configuration details.
>>>> For bug reporting instructions, please see:
>>>> <http://www.gnu.org/software/gdb/bugs/>.
>>>>
>>>> Find the GDB manual and other documentation resources online at:
>>>>        <http://www.gnu.org/software/gdb/documentation/>.
>>>>
>>>> For help, type "help".
>>>> Type "apropos word" to search for commands related to "word"...
>>>> Reading symbols from digikam...
>>>> (No debugging symbols found in digikam)
>>>> Starting program: /tmp/.mount_digiKaHP7SAM/usr/bin/digikam
>>>> [Thread debugging using libthread_db enabled]
>>>> Using host libthread_db library
>>>> "/lib/x86_64-linux-gnu/libthread_db.so.1".
>>>> [New Thread 0x7fffd4a5f700 (LWP 94782)]
>>>> [New Thread 0x7fffcc423700 (LWP 94783)]
>>>> [New Thread 0x7fffcbc22700 (LWP 94784)]
>>>> [New Thread 0x7fffcae4a700 (LWP 94785)]
>>>> [Thread 0x7fffcae4a700 (LWP 94785) exited]
>>>> Digikam::CoreDbAccess::checkReadyForUse: Core database: cannot process
>>>> schema initialization
>>>> [Thread 0x7fffd4a5f700 (LWP 94782) exited]
>>>> [Thread 0x7fffcbc22700 (LWP 94784) exited]
>>>> [Thread 0x7fffcc423700 (LWP 94783) exited]
>>>> --Type <RET> for more, q to quit, c to continue without paging--
>>>> [Inferior 1 (process 94778) exited normally]
>>>> (gdb) bt
>>>> No stack.
>>>> (gdb) quit
>>>>
>>>> Two windows pop up:
>>>>
>>>> errordatabase
>>>>
>>>> On 11.04.21 09:51, Maik Qualmann wrote:
>>>>> Post the debug output from the terminal with the debug environment
>>>>> variable
>>>>> enabled, as described here:
>>>>>
>>>>> https://www.digikam.org/contribute/
>>>>>
>>>>> Maik
>>>>>
>>>>> Am Sonntag, 11. April 2021, 08:33:21 CEST schrieb OzyMate:
>>>>>> Dear all,
>>>>>>
>>>>>> I am a happy user of digikam through digikam-7.1.0-x86-64.appimage and
>>>>>> mysql database on network.
>>>>>>
>>>>>> I wanted to upgrade to 7.2.0, but all I get is "failed to update the
>>>>>> database schema from version 10 to 11".
>>>>>>
>>>>>> Could you please help me sort this issue out.
>>>>>>
>>>>>> Thank you
>>>>>>
>>>>>> Mufit
>
>
>