Bug 287851

Summary:	KMail2 is not able to show the content of received e-mails anymore
Product:	[Applications] kmail2	Reporter:	Roland Wolters <bugs>
Component:	general	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED WORKSFORME
Severity:	normal
Priority:	NOR
Version:	4.7
Target Milestone:	---
Platform:	Fedora RPMs
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Roland Wolters 2011-11-29 16:55:39 UTC

Version:           4.7 (using KDE 4.7.3) 
OS:                Linux

Hej,

while the initial import of all my e-mails (locally stored as maildir, I use several POP3 accounts) did work, kmail2 is not able to show these data anymore. While I am still able to download e-mails from my various pop3 accounts, they cannot be opened.

As a result, I am *not* able to read my e-mails!

Reproducible: Always

Steps to Reproduce:
1. Open kmail2
2. Click on any e-mail

Actual Results:  
The preview window shows the statement, that the mail is about to load, but nothing else. The content of the actual e-mail is not shown.

A double click does not open any window.

Expected Results:  
The preview window should show me the e-mail, the double click should bring up a window with the e-mail.

If I open up kmail, in the right lower corner I can see the progress bar for "messages are being filtered".

But the progress bar does not move. If I click on the red dash to cancel that, it says (translated) "cancel is in progress".

Comment 1 Roland Wolters 2011-11-29 17:02:15 UTC

I checked the Akonadi error protocol and found the following errors:

111129 18:00:25 [Note] Plugin 'FEDERATED' is disabled.
111129 18:00:25 InnoDB: The InnoDB memory heap is disabled
111129 18:00:25 InnoDB: Mutexes and rw_locks use GCC atomic builtins
111129 18:00:25 InnoDB: Compressed tables use zlib 1.2.5
111129 18:00:25 InnoDB: Using Linux native AIO
111129 18:00:25 InnoDB: Initializing buffer pool, size = 8.0M
111129 18:00:25 InnoDB: Completed initialization of buffer pool
111129 18:00:25 InnoDB: highest supported file format is Barracuda.
111129 18:00:26  InnoDB: Warning: allocated tablespace 20, old maximum was 0
111129 18:00:26  InnoDB: Waiting for the background threads to start
111129 18:00:27 InnoDB: 1.1.8 started; log sequence number 371391105
111129 18:00:27 [ERROR] Native table 'performance_schema'.'events_waits_current' has the wrong structure
111129 18:00:27 [ERROR] Native table 'performance_schema'.'events_waits_history' has the wrong structure
111129 18:00:27 [ERROR] Native table 'performance_schema'.'events_waits_history_long' has the wrong structure
111129 18:00:27 [ERROR] Native table 'performance_schema'.'setup_consumers' has the wrong structure
111129 18:00:27 [ERROR] Native table 'performance_schema'.'setup_instruments' has the wrong structure
111129 18:00:27 [ERROR] Native table 'performance_schema'.'setup_timers' has the wrong structure
111129 18:00:27 [ERROR] Native table 'performance_schema'.'performance_timers' has the wrong structure
111129 18:00:27 [ERROR] Native table 'performance_schema'.'threads' has the wrong structure
111129 18:00:27 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_thread_by_event_name' has the wrong structure
111129 18:00:27 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_instance' has the wrong structure
111129 18:00:27 [ERROR] Native table 'performance_schema'.'events_waits_summary_global_by_event_name' has the wrong structure
111129 18:00:27 [ERROR] Native table 'performance_schema'.'file_summary_by_event_name' has the wrong structure
111129 18:00:27 [ERROR] Native table 'performance_schema'.'file_summary_by_instance' has the wrong structure
111129 18:00:27 [ERROR] Native table 'performance_schema'.'mutex_instances' has the wrong structure
111129 18:00:27 [ERROR] Native table 'performance_schema'.'rwlock_instances' has the wrong structure
111129 18:00:27 [ERROR] Native table 'performance_schema'.'cond_instances' has the wrong structure
111129 18:00:27 [ERROR] Native table 'performance_schema'.'file_instances' has the wrong structure
111129 18:00:27 [Note] /usr/libexec/mysqld: ready for connections.
Version: '5.5.17'  socket: '/home/liquidat/.local/share/akonadi/socket-lowangen/mysql.socket'  port: 0  MySQL Community Server (GPL)

Comment 2 Roland Wolters 2011-11-29 19:02:47 UTC

I was able to fix the database errors by:

mysql_upgrade --socket=~/.local/share/akonadi/socket-XXXXX/mysql.socket

Hower, I am still not able to view a single E-Mail.

Maybe that is of interest:
The akonadi system tray tells me about the local ressource:
"is in sync 0%" (roughly translated)

Comment 3 Roland Wolters 2011-12-02 09:43:03 UTC

After playing around with deleting akonadi caches, databases, trying to re-import the data, creating new ressources, and so on I am still not able to open any mail.
Additionally, I realized that moving mails is painfully slow (roughly 2 minutes for each mail), and I lost for sure at least one e-mail.

Thus I moved my mails on my private machine over to another e-mail client which was able to read the maildir without any problem. After 7 or more years of using kmail. :/

I close the bug as wontfix.

Comment 4 Christophe Marin 2011-12-08 12:17:49 UTC

Using a better resolution