kmail does not work after latest update or two to slackware64-current
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Problem is akonadi itself, not buggy implementation. During processing it copy mail many times from disk to other place on disk or into db. Split to single words put them into db again and again. It may works for couple of mails, but it will not scale up. Especially when db config setup have very limited resources. This "low speed" processing could be acceptable when akonadi clients are not blocked by it, but they are! When akonadi do any internal processing, kmail became unusable (yes, also kmail 5).
I'm the OP. I tried Alien Bob's suggestion,
but it did not fix the problem. Down in
~/.local/share/akonadi/db_data, I find mysql.err.
Here are the first few lines. Looks like the DB
is missing some tables. Once the repeating lines
begin, they continue to the end of the file.
Kmail is trying to do something, but it's not
working for kmail.
John.
2019-06-28 17:22:13 0 [Note] InnoDB: Using Linux native AIO
2019-06-28 17:22:13 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2019-06-28 17:22:13 0 [Note] InnoDB: Uses event mutexes
2019-06-28 17:22:13 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2019-06-28 17:22:13 0 [Note] InnoDB: Number of pools: 1
2019-06-28 17:22:13 0 [Note] InnoDB: Using SSE2 crc32 instructions
2019-06-28 17:22:13 0 [Note] mysqld: O_TMPFILE is not supported on /tmp (disabling future attempts)
2019-06-28 17:22:13 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
2019-06-28 17:22:13 0 [Note] InnoDB: Completed initialization of buffer pool
2019-06-28 17:22:13 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be
changed. See the man page of setpriority().
2019-06-28 17:22:13 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2019-06-28 17:22:13 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2019-06-28 17:22:13 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please
wait ...
2019-06-28 17:22:13 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
2019-06-28 17:22:13 0 [Note] InnoDB: 10.4.6 started; log sequence number 15108425505; transaction id 27414937
2019-06-28 17:22:13 0 [Note] InnoDB: Loading buffer pool(s) from /home/jkh/.local/share/akonadi/db_data/ib_buffer_poo
l
2019-06-28 17:22:13 0 [Note] Plugin 'FEEDBACK' is disabled.
2019-06-28 17:22:13 5 [Warning] Failed to load slave replication state from table mysql.gtid_slave_pos: 1146: Table '
mysql.gtid_slave_pos' doesn't exist
2019-06-28 17:22:13 0 [Note] Reading of all Master_info entries succeeded
2019-06-28 17:22:13 0 [Note] Added new Master_info '' to hash table
2019-06-28 17:22:13 0 [Note] /usr/libexec/mysqld: ready for connections.
Version: '10.4.6-MariaDB' socket: '/tmp/akonadi-jkh.2pltk5/mysql.socket' port: 0 MariaDB Server
2019-06-28 17:22:13 0 [Note] InnoDB: Buffer pool(s) load completed at 190628 17:22:13
2019-06-28 17:22:13 9 [ERROR] InnoDB: Table `mysql`.`innodb_table_stats` not found.
2019-06-28 17:22:13 10 [ERROR] Transaction not registered for MariaDB 2PC, but transaction is active
2019-06-28 17:22:13 10 [ERROR] Transaction not registered for MariaDB 2PC, but transaction is active
2019-06-28 17:22:13 10 [ERROR] Transaction not registered for MariaDB 2PC, but transaction is active
Missing tables are rather harmless, I have same errors and my ankonadi works.
But "Transaction not registered for MariaDB 2PC, but transaction is active" looks scary. I'm not quite sure what it mean. My only guess is that akonadi tries run SQL transaction query but your db did not support them. This can be true when you have MyISAM tables. You may try change table types to InnoDB (I have that type in my db), but I don't know how to login to akonadi's mysql to do so.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.