https://bugs.kde.org/show_bug.cgi?id=389829
--- Comment #19 from Raúl <rasas...@gmail.com> --- Hello: I think here we are talking about 2 different issues: * Issue reported which is that it is not possible to fetch a specific email from akonadi backend. I think this is related to database engine, database corruption or akonadiserver lack of sync with database. This is what your latest journalctl log (https://bugs.kde.org/attachment.cgi?id=144299) could be related to (or maybe not. I'm not sure) * A permanent deadlock in either the communication from akonadi with the database engine or a problem in the database handling. This is exposed when sending the `show engine innodb status;` sql statement to the database engine. This is also exposed with the error message ` Deadlock found when trying to get lock; try restarting transaction QMYSQL3: Unable to execute statement` I think this problem should be followed up in the proper bug report https://bugs.kde.org/show_bug.cgi?id=434706 This problems prevents going on in the kmail usage as akonadi cannot properly fetch or handle data from database. One workaround for my is killing the mariadb server and letting akonadi to restart it. Regards, -- You are receiving this mail because: You are watching all bug changes.
