I have not been able to work out when it happens, but on occasion a message from an IMAP mail server will come through and, while the header is intact, there is nothing in the body of the message. When this occurs I have sent myself test messages with text in the body and they come up blank, too. Moreover, when I check those messages using the webmail client for the email server, the message there, too, are wiped clean of their body. However, this only happens after they have been pulled down by kmail2. It seems that I can revert back to normal behavior by deleting the IMAP account and creating it anew. I also, in this stage, stop and start akonadi, sometimes deleting the akonadi folder. However, even after doing this, the body of the email messages is lost both in kmail and in the IMAP folder. Reproducible: Sometimes I cannot reproduce the problem as I do not know what action causes it to come about in the first place. I'd be happy to post any logs, etc.
Hi, I've got the same problem. For resolving it I've to delete my IMAP account and recreate it again. I observed error in AKONADI Test 5: ERROR -------- MySQL server log contains errors. Details: The MySQL server error log file '<a href='/home/mdubois/.local/share/akonadi/db_data/mysql.err'>/home/mdubois/.local/share/akonadi/db_data/mysql.err</a>' contains errors. File content of '/home/mdubois/.local/share/akonadi/db_data/mysql.err': 120522 9:44:02 [Note] Plugin 'FEDERATED' is disabled. 120522 9:44:02 InnoDB: The InnoDB memory heap is disabled 120522 9:44:02 InnoDB: Mutexes and rw_locks use GCC atomic builtins 120522 9:44:02 InnoDB: Compressed tables use zlib 1.2.3.4 120522 9:44:02 InnoDB: Initializing buffer pool, size = 80.0M 120522 9:44:02 InnoDB: Completed initialization of buffer pool 120522 9:44:02 InnoDB: highest supported file format is Barracuda. 120522 9:44:04 InnoDB: Waiting for the background threads to start 120522 9:44:05 InnoDB: 1.1.8 started; log sequence number 38694254447 120522 9:44:05 [ERROR] Native table 'performance_schema'.'events_waits_current' has the wrong structure 120522 9:44:05 [ERROR] Native table 'performance_schema'.'events_waits_history' has the wrong structure 120522 9:44:05 [ERROR] Native table 'performance_schema'.'events_waits_history_long' has the wrong structure 120522 9:44:05 [ERROR] Native table 'performance_schema'.'setup_consumers' has the wrong structure 120522 9:44:05 [ERROR] Native table 'performance_schema'.'setup_instruments' has the wrong structure 120522 9:44:05 [ERROR] Native table 'performance_schema'.'setup_timers' has the wrong structure 120522 9:44:05 [ERROR] Native table 'performance_schema'.'performance_timers' has the wrong structure 120522 9:44:05 [ERROR] Native table 'performance_schema'.'threads' has the wrong structure 120522 9:44:05 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_thread_by_event_name' has the wrong structure 120522 9:44:05 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_instance' has the wrong structure 120522 9:44:05 [ERROR] Native table 'performance_schema'.'events_waits_summary_global_by_event_name' has the wrong structure 120522 9:44:05 [ERROR] Native table 'performance_schema'.'file_summary_by_event_name' has the wrong structure 120522 9:44:05 [ERROR] Native table 'performance_schema'.'file_summary_by_instance' has the wrong structure 120522 9:44:05 [ERROR] Native table 'performance_schema'.'mutex_instances' has the wrong structure 120522 9:44:05 [ERROR] Native table 'performance_schema'.'rwlock_instances' has the wrong structure 120522 9:44:05 [ERROR] Native table 'performance_schema'.'cond_instances' has the wrong structure 120522 9:44:05 [ERROR] Native table 'performance_schema'.'file_instances' has the wrong structure 120522 9:44:05 [Note] /usr/sbin/mysqld: ready for connections. Version: '5.5.22-0ubuntu1' socket: '/home/mdubois/.local/share/akonadi/socket-lsdbot/mysql.socket' port: 0 (Ubuntu)
I'm curious to know if some one using kmail2 gets the same results as I (Orang_Gila) get in kmail following the step I layed out in the following bug report: https://bugs.kde.org/show_bug.cgi?id=210590
Hi Orang_Gila, Seems the same, but anybody din't check the akanodi database in your prupose # 210590. I'm uder Kubuntu 12.04 with KDE version 4.8.3 (4.8.3). I installed the newest version of KDE as recommanded in the ubuntu forum and I'm still with the same problem. I 'm going to follow you bug too for knowing the problem solved.
These are basically the only recent errors I constantly see in the mysql.err or mysql.err.old files located in Akonadi MySQL server directory you mentioned. akonadi-server 1.6.2-2+b1 mate-desktop 1.2.0-3+wheezy (a GNOME 2.3 fork) kontact not installed -------------- 120531 14:10:08 [Note] Plugin 'FEDERATED' is disabled. 120531 14:10:08 InnoDB: Initializing buffer pool, size = 80.0M 120531 14:10:08 InnoDB: Completed initialization of buffer pool InnoDB: The log sequence number in ibdata files does not match InnoDB: the log sequence number in the ib_logfiles! 120531 14:10:08 InnoDB: Database was not shut down normally! InnoDB: Starting crash recovery. InnoDB: Reading tablespace information from the .ibd files... InnoDB: Restoring possible half-written data pages from the doublewrite InnoDB: buffer... InnoDB: Last MySQL binlog file position 0 923, file name ./mysql-bin.000909 120531 14:10:08 InnoDB: Started; log sequence number 0 20302258 120531 14:10:08 [Note] /usr/sbin/mysqld: ready for connections. Version: '5.1.61-2-log' socket: '/home/username/.local/share/akonadi/socket-hostname/mysql.socket' port: 0 (Debian)
*** Bug 302228 has been marked as a duplicate of this bug. ***
For me all incoming mails were truncated as described in this bug report. But not only when kmail2 was running also when only akonadi was running. Stopping akonadi also stopped the truncating.
Which exact Kmail version is this report about and is this reproducible with version 4.8.5 or later? Please set the version field accordingly.
*** Bug 210590 has been marked as a duplicate of this bug. ***
I have the same problem with Kmai 4.8.5 on Fedora 17 (i686). The source of this truncated messages contains only this: From MY_EMAIL Wed, 22 Aug 2012 21:19:35 +0200 (GMT+02:00) To: MY_EMAIL Subject: L'indirizo From: MY_FRIEND_EMAIL Message-ID: <OF6501FBAF.81F7A820-ONC1257A61.003AC57C-C1257A61.003AE73D@it.ibm.com> Date: Tue, 21 Aug 2012 12:43:16 +0200 X-Spambayes-Classification: spam; 1.00 MIME-Version: 1.0 This is the header of the source of all the truncated emails. For now I use Thunderbird, but I don't like it.
Thank you for the feedback.
same here, archlinux, kde 4.9.2
Occurred to me on kde 4.9.3 on kubuntu 12.10 on a fresh install.
Problem vanished after deleting and recreating the imap account.
This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present? If noone confirms this bug for a Framework-based version of kmail2 (version 5.0 or later, as part of KDE Applications 15.12 or later), it gets closed in about three months.
Created attachment 101268 [details] snapshot
I am experiencing this issue with Kmail 5.1.3/KDE Framework 5.23.0/Qt 5.5.1
Frederick, thank you for your screenshot and feedback. I noticed that your folder list is empty, which doesn't quite match the bug summary. Do you have at least one account set up? Also, reassigning to Akonadi.
Hi Denis, I've got 4 accounts in my Kmail and this just happens from time to time (approx 1 out of 10 boots I will bump into this issue), and I have to reboot my machine to fix it... ...but yes, it seems that this is a quite different from the description. I deem that I've seen a similar issue here and this should be the reply to a wrong thread however I can't find it...
Frederick, since mixing up different bugs in one bug report makes it harder to locate them in the code, I don't take your observations as confirmation for this bug. If you cannot find a report for the bug you encountered, you might consider opening a new bug for this.
(In reply to Denis Kurz from comment #20) > Frederick, since mixing up different bugs in one bug report makes it harder > to locate them in the code, I don't take your observations as confirmation > for this bug. > > If you cannot find a report for the bug you encountered, you might consider > opening a new bug for this. I've opened a new one, thanks.
(In reply to Frederick Zhang from comment #21) > (In reply to Denis Kurz from comment #20) > > Frederick, since mixing up different bugs in one bug report makes it harder > > to locate them in the code, I don't take your observations as confirmation > > for this bug. > > > > If you cannot find a report for the bug you encountered, you might consider > > opening a new bug for this. > > I've opened a new one, thanks. Forgot to paste the link, https://bugs.kde.org/show_bug.cgi?id=369372
Frederick, thanks a lot for your efforts. Since this bug seems to be resolved, I close here.