https://bugs.kde.org/show_bug.cgi?id=388867
--- Comment #27 from Ian Robertson <irobe...@narian.org.uk> --- Nice one Simon. [ianrob01@nova ~]$ export QT_LOGGING_RULES="digikam.*=true" [ianrob01@nova ~]$ digikam digikam.general: AlbumWatch use QFileSystemWatcher digikam.general: Database Parameters: Type: "QMYSQL" DB Core Name: "digikam5" DB Thumbs Name: "digikam5" DB Face Name: "digikam5" Connect Options: "" Host Name: "pro.barony.loc" Host port: 3306 Internal Server: false Internal Server Path: "" Internal Server Serv Cmd: "" Internal Server Init Cmd: "" Username: "digikam5" 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 8 digikam.coredb: Core database: makeUpdates 8 to 9 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 [ "UpdateSchemaFromV7ToV9" ] Statement [ "DROP TRIGGER IF EXISTS delete_image;" ] digikam.coredb: Core database: schema update to V 9 failed! digikam.coredb: Core database: cannot process schema initialization --- Odd as have granted ALL on digikam5.* to 'digikam5'@'%' - disable binary logging ( mariadb ) Ian -- You are receiving this mail because: You are watching all bug changes.
