[Bug 295700] After upgrade to 4.8.1: QMYSQL3 is unable to execute statement due to BINLOG_FORMAT = STATEMENT

[Franz Häuslschmid]

https://bugs.kde.org/show_bug.cgi?id=295700

--- Comment #1 from Franz Häuslschmid <lukrez at gmx.at> ---
After having updated to 4.8.1 I added an IMAP resource for a dovecot2 mail
server. After that process I was trying to load messages (read and unread) from
that server. I assume I was hit by the bug of
<https://bugs.kde.org/show_bug.cgi?id=295484> as the only unread message in the
inbox lost its body.  At some point Kmail2 crashed and I rebooted my computer.

Kmail2 then listed my mail hierarchy, but didn't show the mail contents.  I
looked into .xsession-errors and observed many occurrences like

found 1 item parts to expire in collection "INBOX" 
Error during updating record with id 11438  in table "PartTable" "Cannot
execute statement: impossible to write to binary log since BINLOG_FORMAT =
STATEMENT and at least one table uses a storage engine limited to row-based
logging. InnoDB is limited to row-logging when transaction isolation level is
READ COMMITTED or READ UNCOMMITTED. QMYSQL3: Unable to execute statement" 
failed to update item part 11438 

Decided to recreate Akonadi's database, deleted "~/.local/share/akonadi" and
started the command "akonadictl start".  There still was a problem regarding
the setting for locking database objects:
Database "akonadi" opened using driver "QMYSQL" 
DbInitializer::run() 
checking table  "SchemaVersionTable" 
"INSERT INTO SchemaVersionTable (version) VALUES (20)" 
"Unable to add initial data to table 'SchemaVersionTable'.
Query error: 'Cannot execute statement: impossible to write to binary log since
BINLOG_FORMAT = STATEMENT and at least one table uses a storage engine limited
to row-based logging. InnoDB is limited to row-logging when transaction
isolation level is READ COMMITTED or READ UNCOMMITTED. QMYSQL: Unable to
execute query'
Query was: INSERT INTO SchemaVersionTable (version) VALUES (20)"
Unable to initialize database.
"[
0: akonadiserver(_Z11akBacktracev+0x35) [0x453ba5]
1: akonadiserver() [0x453e6c]
2: /lib64/libc.so.6(+0x34e10) [0x7f91cd1b2e10]
3: /lib64/libc.so.6(gsignal+0x35) [0x7f91cd1b2d95]
4: /lib64/libc.so.6(abort+0x17b) [0x7f91cd1b42ab]
5: /usr/lib64/libQtCore.so.4(_Z17qt_message_output9QtMsgTypePKc+0x74)
[0x7f91cec79c84]
6: akonadiserver(_ZN15FileDebugStream9writeDataEPKcx+0x92) [0x456142]
7: /usr/lib64/libQtCore.so.4(_ZN9QIODevice5writeEPKcx+0xaf) [0x7f91ced1482f]
8: /usr/lib64/libQtCore.so.4(+0x11de02) [0x7f91ced1fe02]
9: /usr/lib64/libQtCore.so.4(_ZN11QTextStreamD1Ev+0x39) [0x7f91ced28c99]
10: akonadiserver() [0x45abd8]
11: akonadiserver(_ZN7Akonadi13AkonadiServer8instanceEv+0x35) [0x45bd45]
12: akonadiserver(main+0x1ea) [0x44c0da]
13: /lib64/libc.so.6(__libc_start_main+0xed) [0x7f91cd19f23d]
14: akonadiserver() [0x44c871]
]
"
ProcessControl: Application 'akonadiserver' returned with exit code 255
(Unknown error)

After that I explicitly added "binlog_format=mixed" to
"~/.config/akonadi/mysql-local.conf".  Akonadi and Kmail2 now work as expected.

-- 
You are receiving this mail because:
You are the assignee for the bug.