Kmail stops showing messages and download new

Ole Jacob Taraldset <[email protected]>
Newsgroups gmane.comp.kde.users.pim
Message-ID <CACGj6CEEp0OdngD8FjBnMx9Yh-+hmBx1tZzO5jH0mamCRoBG=A@mail.gmail.com> 
After upgrading to KDE 4.8.3 from 4.8.1 Kmail stopped working. It no longer
shows message texts when I click an email, and it doesn't download new
massages.
OpenSuse 12.1

Regards,
Ole Jacob

I get the following from akonadi:
/home/ojt> Known subscriber "kmail2" subscribes again
Known subscriber "kmail2" subscribes again
akonadi_pop3_resource_4(6964)/kio (KIOJob) KIO::TransferJob::slotData:
mimeType() not emitted when sending first data!; job URL = KUrl("pop3s://
olebjerkeas%[email protected]:995/index") data size = 0
Error during executing query "UPDATE PimItemTable SET atime = :0 WHERE (
collectionId = :1 )" :  "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"
Unable to update item access time
akonadi_pop3_resource_4(6964)/kio (KIOJob) KIO::TransferJob::slotData:
mimeType() not emitted when sending first data!; job URL = KUrl("pop3s://
olebjerkeas%[email protected]:995/uidl") data size = 0
akonadi_pop3_resource_4(6964)/kio (KIOJob) KIO::TransferJob::slotData:
mimeType() not emitted when sending first data!; job URL = KUrl("pop3s://
olebjerkeas%[email protected]:995/download/") data size = 0
Error during executing query "UPDATE PimItemTable SET atime = :0 WHERE (
collectionId = :1 )" :  "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"
Unable to update item access time
akonadi_pop3_resource_3(6963)/kio (KIOJob) KIO::TransferJob::slotData:
mimeType() not emitted when sending first data!; job URL = KUrl("pop3s://
bergentriathlon%[email protected]:995/index") data size = 0
Error during executing query "UPDATE PimItemTable SET atime = :0 WHERE (
collectionId = :1 )" :  "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"
Unable to update item access time
posting retrieval request for item 85819  there are  1  queues and  0
items in mine
request for item 85819 still pending - waiting
processing retrieval request for item 85819  parts: ("RFC822", "HEAD")  of
resource: "akonadi_maildir_resource_2"
Error during executing query "UPDATE PimItemTable SET atime = :0 WHERE ( (
PimItemTable.id = :1 ) )" :  "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"
Unable to update item access time
Error during updating record with id 254508  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"
continuing
request for item 85819 "1336167375.R65.zappa" failed: "Resource was unable
to deliver item"
ItemRetrieverException :  Resource was unable to deliver item
posting retrieval request for item 85819  there are  1  queues and  0
items in mine
request for item 85819 still pending - waiting
processing retrieval request for item 85819  parts: ("RFC822", "HEAD")  of
resource: "akonadi_maildir_resource_2"
Error during executing query "UPDATE PimItemTable SET atime = :0 WHERE ( (
PimItemTable.id = :1 ) )" :  "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"
Unable to update item access time
Error during updating record with id 254508  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"
continuing
request for item 85819 "1336167375.R65.zappa" failed: "Resource was unable
to deliver item"
ItemRetrieverException :  Resource was unable to deliver item
posting retrieval request for item 85819  there are  1  queues and  0
items in mine
request for item 85819 still pending - waiting
processing retrieval request for item 85819  parts: ("RFC822", "HEAD")  of
resource: "akonadi_maildir_resource_2"
Error during executing query "UPDATE PimItemTable SET atime = :0 WHERE ( (
PimItemTable.id = :1 ) )" :  "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"
Unable to update item access time
Error during updating record with id 254508  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"
continuing
request for item 85819 "1336167375.R65.zappa" failed: "Resource was unable
to deliver item"
ItemRetrieverException :  Resource was unable to deliver item
akonadi_pop3_resource_3(6963)/kio (KIOJob) KIO::TransferJob::slotData:
mimeType() not emitted when sending first data!; job URL = KUrl("pop3s://
bergentriathlon%[email protected]:995/uidl") data size = 0
akonadi_pop3_resource_3(6963)/kio (KIOJob) KIO::TransferJob::slotData:
mimeType() not emitted when sending first data!; job URL = KUrl("pop3s://
bergentriathlon%[email protected]:995/download/") data size = 0
akonadi_pop3_resource_1(6961)/kio (KIOJob) KIO::TransferJob::slotData:
mimeType() not emitted when sending first data!; job URL = KUrl("pop3s://
taraldset%[email protected]:995/index") data size = 8
akonadi_pop3_resource_1(6961)/kio (KIOJob) KIO::TransferJob::slotData:
mimeType() not emitted when sending first data!; job URL = KUrl("pop3s://
taraldset%[email protected]:995/uidl") data size = 27
Error during executing query "INSERT INTO PimItemTable (rev,
remoteRevision, collectionId, mimeTypeId, atime, dirty, size) VALUES (:0,
:1, :2, :3, :4, :5, :6)" :  "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"
Error during insertion into table "PimItemTable" "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"
akonadi_pop3_resource_1(6961)/akonadiresource (pop3)
POP3Resource::cancelSync: ============== ERROR DURING POP3 SYNC
==========================
akonadi_pop3_resource_1(6961)/akonadiresource (pop3)
POP3Resource::cancelSync: "Unable to store downloaded mails.
Unknown error. (Append failed)"
akonadi_pop3_resource_4(6964)/kio (KIOJob) KIO::TransferJob::slotData:
mimeType() not emitted when sending first data!; job URL = KUrl("pop3s://
olebjerkeas%[email protected]:995/index") data size = 0
akonadi_pop3_resource_4(6964)/kio (KIOJob) KIO::TransferJob::slotData:
mimeType() not emitted when sending first data!; job URL = KUrl("pop3s://
olebjerkeas%[email protected]:995/uidl") data size = 0
akonadi_pop3_resource_4(6964)/kio (KIOJob) KIO::TransferJob::slotData:
mimeType() not emitted when sending first data!; job URL = KUrl("pop3s://
olebjerkeas%[email protected]:995/download/") data size = 0
akonadi_pop3_resource_1(6961)/kio (KIOJob) KIO::TransferJob::slotData:
mimeType() not emitted when sending first data!; job URL = KUrl("pop3s://
taraldset%[email protected]:995/index") data size = 8
akonadi_pop3_resource_1(6961)/kio (KIOJob) KIO::TransferJob::slotData:
mimeType() not emitted when sending first data!; job URL = KUrl("pop3s://
taraldset%[email protected]:995/uidl") data size = 27
Error during executing query "INSERT INTO PimItemTable (rev,
remoteRevision, collectionId, mimeTypeId, atime, dirty, size) VALUES (:0,
:1, :2, :3, :4, :5, :6)" :  "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"
Error during insertion into table "PimItemTable" "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"
akonadi_pop3_resource_1(6961)/akonadiresource (pop3)
POP3Resource::cancelSync: ============== ERROR DURING POP3 SYNC
==========================
akonadi_pop3_resource_1(6961)/akonadiresource (pop3)
POP3Resource::cancelSync: "Unable to store downloaded mails.
Unknown error. (Append failed)"
posting retrieval request for item 85819  there are  1  queues and  0
items in mine
request for item 85819 still pending - waiting
processing retrieval request for item 85819  parts: ("RFC822", "HEAD")  of
resource: "akonadi_maildir_resource_2"
Error during executing query "UPDATE PimItemTable SET atime = :0 WHERE ( (
PimItemTable.id = :1 ) )" :  "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"
Unable to update item access time
Error during updating record with id 254508  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"
continuing
request for item 85819 "1336167375.R65.zappa" failed: "Resource was unable
to deliver item"
ItemRetrieverException :  Resource was unable to deliver item
posting retrieval request for item 85819  there are  1  queues and  0
items in mine
request for item 85819 still pending - waiting
processing retrieval request for item 85819  parts: ("RFC822", "HEAD")  of
resource: "akonadi_maildir_resource_2"
Error during executing query "UPDATE PimItemTable SET atime = :0 WHERE ( (
PimItemTable.id = :1 ) )" :  "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"
Unable to update item access time
Error during updating record with id 254508  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"
continuing
request for item 85819 "1336167375.R65.zappa" failed: "Resource was unable
to deliver item"
ItemRetrieverException :  Resource was unable to deliver item
posting retrieval request for item 85819  there are  1  queues and  0
items in mine
request for item 85819 still pending - waiting
processing retrieval request for item 85819  parts: ("RFC822", "HEAD")  of
resource: "akonadi_maildir_resource_2"
Error during executing query "UPDATE PimItemTable SET atime = :0 WHERE ( (
PimItemTable.id = :1 ) )" :  "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"
Unable to update item access time
Error during updating record with id 254508  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"
continuing
request for item 85819 "1336167375.R65.zappa" failed: "Resource was unable
to deliver item"
ItemRetrieverException :  Resource was unable to deliver item
akonadi_pop3_resource_4(6964)/kio (KIOJob) KIO::TransferJob::slotData:
mimeType() not emitted when sending first data!; job URL = KUrl("pop3s://
olebjerkeas%[email protected]:995/index") data size = 0
akonadi_pop3_resource_4(6964)/kio (KIOJob) KIO::TransferJob::slotData:
mimeType() not emitted when sending first data!; job URL = KUrl("pop3s://
olebjerkeas%[email protected]:995/uidl") data size = 0
akonadi_pop3_resource_4(6964)/kio (KIOJob) KIO::TransferJob::slotData:
mimeType() not emitted when sending first data!; job URL = KUrl("pop3s://
olebjerkeas%[email protected]:995/download/") data size = 0
akonadi_pop3_resource_1(6961)/kio (KIOJob) KIO::TransferJob::slotData:
mimeType() not emitted when sending first data!; job URL = KUrl("pop3s://
taraldset%[email protected]:995/index") data size = 8
akonadi_pop3_resource_1(6961)/kio (KIOJob) KIO::TransferJob::slotData:
mimeType() not emitted when sending first data!; job URL = KUrl("pop3s://
taraldset%[email protected]:995/uidl") data size = 27
Error during executing query "INSERT INTO PimItemTable (rev,
remoteRevision, collectionId, mimeTypeId, atime, dirty, size) VALUES (:0,
:1, :2, :3, :4, :5, :6)" :  "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"
Error during insertion into table "PimItemTable" "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"
akonadi_pop3_resource_1(6961)/akonadiresource (pop3)
POP3Resource::cancelSync: ============== ERROR DURING POP3 SYNC
==========================
akonadi_pop3_resource_1(6961)/akonadiresource (pop3)
POP3Resource::cancelSync: "Unable to store downloaded mails.
Unknown error. (Append failed)"

_______________________________________________
KDE PIM users mailing list
Subscription management: https://mail.kde.org/mailman/listinfo/kdepim-users
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.