Bug 312553 - No further updates to and from IMAP account [regression]
Summary: No further updates to and from IMAP account [regression]
Status: RESOLVED WORKSFORME
Alias: None
Product: kmail2
Classification: Applications
Component: general (show other bugs)
Version: 4.9.95 RC1
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords: regression
Depends on:
Blocks: 295700
  Show dependency treegraph
 
Reported: 2013-01-03 16:29 UTC by Rolf Eike Beer
Modified: 2013-01-23 17:46 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Rolf Eike Beer 2013-01-03 16:29:33 UTC
Since I upgraded to 4.10rc1 KMail does not show new mails anymore, i.e. all mails I see are those received before the update. I have 3 unread mails in one folder, where I can't change their status to read. I can see the mails, but neither are the mails automatically marked as read as usual nor can I manually mark them as read.

Reproducible: Always
Comment 1 Rolf Eike Beer 2013-01-23 16:43:19 UTC
Somehow the "binlog_format=row" that was the fix for bug 289097 got lost from the config file during the upgrade (it wasn't me!). This then leads to error messages like this:

Error during executing query "INSERT INTO CollectionTable (remoteId, remoteRevision, name, resourceId, cachePolicyInherit, cachePolicyCheckInterval, cachePolicyCacheTimeout, cachePolicySyncOnDemand, cachePolicyLocalParts) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8)" :  "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"

Those can only be observed if starting KMail from a terminal and akonadi not already running. Adding back the binlog_format=row to the config file fixed my problem.