https://bugs.kde.org/show_bug.cgi?id=451460
--- Comment #3 from Vincent Danjean <vdanjean...@free.fr> ---
```
$ QT_LOGGING_RULES="digikam.*=true" digikam
digikam.widgets: Use installed icons
digikam.general: Switch to widget style: ""
digikam.general: AlbumWatch is disabled
digikam.general: Database Parameters:
Type: "QMYSQL"
DB Core Name: "digikamdb"
DB Thumbs Name: "digikamthumbdb"
DB Face Name: "digikamfaces"
DB Similarity Name: ""
Connect Options: ""
Host Name: "localhost"
Host port: 3306
Internal Server: false
Internal Server Path: ""
Internal Server Admin Cmd: "mysqladmin"
Internal Server Serv Cmd: ""
Internal Server Init Cmd: ""
Username: "digikamuser"
Password: "XXXXXXXX"
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 10
digikam.coredb: Core database: makeUpdates 10 to 15
digikam.dbengine: 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.dbengine: Error while executing DBAction [ "UpdateSchemaFromV10ToV11" ]
Statement [ "CREATE TRIGGER temp_insert_tagstree AFTER INSERT ON temp_Tags\n
FOR EACH ROW INSERT INTO TagsTree SELECT NEW.id, NEW.pid\n
UNION SELECT NEW.id, pid FROM TagsTree WHERE id = NEW.pid;\n
" ]
digikam.coredb: Core database: schema update to V 11 failed!
digikam.coredb: Core database: cannot process schema initialization
==========
digikam.general: KMemoryInfo: Platform identified : "LINUX"
digikam.general: KMemoryInfo: TotalRam: 33504178176
digikam.general: Allowing a cache size of 400 MB
QThreadStorage: Thread 0x7ffff7fc2b00 exited after QThreadStorage 12 destroyed
```
Popups appears where I wrote "========" (not present in the terminal)
--
You are receiving this mail because:
You are watching all bug changes.
