Hello. I tried to install kmail on my linux. Was installed without problems, but when i tried to execute it, I found the next problems that don't allow its use.

1- MySQL server log contains errors
2- MySQL server custom configuration not available
3- Akonadi control process not registered at D-Bus
4- Akonadi server process not registered at D-Bus
5- Nepomuk search service not registered at D-Bus
6- No resource agents found
7- Currently Akonadi server error log found
8- Previous Akonadi server error log found

I would like to use kmail, but i don't have enough knowledge to do.

Can anyone help me a bit? Thanks forward


The extended error report

Akonadi Server Self-Test Report
===============================

Test 1: ERROR
--------

Database driver not found.
Details: The QtSQL driver 'QMYSQL' is required by your current Akonadi server configuration.
The following drivers are installed: QSQLITE, QSQLITE3.
Make sure the required driver is installed.

File content of '/home/enigma/.config/akonadi/akonadiserverrc':
[%General]
Driver=QMYSQL

[QMYSQL]
Name=akonadi
Host=
Options="UNIX_SOCKET=/home/enigma/.local/share/akonadi/socket-minienigma/mysql.socket"
ServerPath=/usr/sbin/mysqld
StartServer=true


Test 2: SUCCESS
--------

Akonadi is not running as root
Details: Akonadi is not running as a root/administrator user, which is the recommended setup for a secure system.

Test 3: SUCCESS
--------

MySQL server found.
Details: You have currently configured Akonadi to use the MySQL server '/usr/sbin/mysqld'.
Make sure you have the MySQL server installed, set the correct path and ensure you have the necessary read and execution rights on the server executable. The server executable is typically called 'mysqld'; its location varies depending on the distribution.

Test 4: SUCCESS
--------

MySQL server is executable.
Details: MySQL server found: /usr/sbin/mysqld Ver 5.1.56-log for pc-linux-gnu on x86_64 (Gentoo Linux mysql-5.1.56)


Test 5: ERROR
--------

MySQL server log contains errors.
Details: The MySQL server error log file &apos;<a href='/home/enigma/.local/share/akonadi/db_data/mysql.err'>/home/enigma/.local/share/akonadi/db_data/mysql.err</a>&apos; contains errors.

File content of '/home/enigma/.local/share/akonadi/db_data/mysql.err':
120112 13:54:55 InnoDB: Initializing buffer pool, size = 80.0M
120112 13:54:55 InnoDB: Completed initialization of buffer pool
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
.
.
.This error repeats a lot


InnoDB: using the same InnoDB data or log files.
120112 13:56:35 InnoDB: Unable to open the first data file
InnoDB: Error in opening ./ibdata1
120112 13:56:35 InnoDB: Operating system error number 11 in a file operation.
InnoDB: Error number 11 means 'Resource temporarily unavailable'.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/ ... codes.html
InnoDB: Could not open or create data files.
InnoDB: If you tried to add new data files, and it failed here,
InnoDB: you should now edit innodb_data_file_path in my.cnf back
InnoDB: to what it was, and remove the new ibdata files InnoDB created
InnoDB: in this failed attempt. InnoDB only wrote those files full of
InnoDB: zeros, but did not yet use them in any way. But be careful: do not
InnoDB: remove old data files which contain your precious data!
120112 13:56:35 [ERROR] Plugin 'InnoDB' init function returned error.
120112 13:56:35 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
120112 13:56:35 [ERROR] Unknown/unsupported table type: innodb
120112 13:56:35 [ERROR] Aborting

120112 13:56:35 [Note] /usr/sbin/mysqld: Shutdown complete



Test 6: SUCCESS
--------

MySQL server default configuration found.
Details: The default configuration for the MySQL server was found and is readable at <a href='/usr/share/config/akonadi/mysql-global.conf'>/usr/share/config/akonadi/mysql-global.conf</a>.

File content of '/usr/share/config/akonadi/mysql-global.conf':
#
# Global Akonadi MySQL server settings,
# These settings can be adjusted using $HOME/.config/akonadi/mysql-local.conf
#
# Based on advice by Kris Köhntopp <kris@mysql.com>
#
[mysqld]
skip_grant_tables
skip_networking

# strict query parsing/interpretation
# TODO: make Akonadi work with those settings enabled
#sql_mode=strict_trans_tables,strict_all_tables,strict_error_for_division_by_zero,no_auto_create_user,no_auto_value_on_zero,no_engine_substitution,no_zero_date,no_zero_in_date,only_full_group_by,pipes_as_concat
#sql_mode=strict_trans_tables

# use InnoDB for transactions and better crash recovery
default_storage_engine=innodb
# case-insensitive table names, avoids trouble on windows
lower_case_table_names=1
character_set_server=utf8
collation_server=utf8_general_ci
table_cache=200
thread_cache_size=3
#log_bin=mysql-bin
#expire_logs_days=3
#sync_bin_log=0
# error log file name, relative to datadir
log_error=mysql.err
log_warnings=2
# log all queries, useful for debugging but generates an enormous amount of data
#log=mysql.full
# log queries slower than n seconds, log file name relative to datadir (for debugging only)
#log_slow_queries=mysql.slow
#long_query_time=1
# log queries not using indices, debug only, disable for production use
#log_queries_not_using_indexes=1
# maximum blob size
max_allowed_packet=32M
max_connections=256
# makes sense when having the same query multiple times
# makes no sense with prepared statements and/or transactions
query_cache_type=0
query_cache_size=0

innodb_file_per_table=1
innodb_log_buffer_size=1M
innodb_additional_mem_pool_size=1M
# messure database size and adjust
# SELECT sum(data_length) as bla, sum(index_length) as blub FROM information_schema.tables WHERE table_schema not in ("mysql", "information_schema");
innodb_buffer_pool_size=80M
# size of average write burst, keep Innob_log_waits small, keep Innodb_buffer_pool_wait_free small (see show global status like "inno%", show global variables)
innodb_log_file_size=64M
innodb_flush_log_at_trx_commit=2

# Do not drop the connection to the DB after 8 hours of inactivity
wait_timeout=31536000

[client]
default-character-set=utf8


Test 7: SKIP
--------

MySQL server custom configuration not available.
Details: The custom configuration for the MySQL server was not found but is optional.

Test 8: SUCCESS
--------

MySQL server configuration is usable.
Details: The MySQL server configuration was found at <a href='/home/enigma/.local/share/akonadi/mysql.conf'>/home/enigma/.local/share/akonadi/mysql.conf</a> and is readable.

File content of '/home/enigma/.local/share/akonadi/mysql.conf':
#
# Global Akonadi MySQL server settings,
# These settings can be adjusted using $HOME/.config/akonadi/mysql-local.conf
#
# Based on advice by Kris Köhntopp <kris@mysql.com>
#
[mysqld]
skip_grant_tables
skip_networking

# strict query parsing/interpretation
# TODO: make Akonadi work with those settings enabled
#sql_mode=strict_trans_tables,strict_all_tables,strict_error_for_division_by_zero,no_auto_create_user,no_auto_value_on_zero,no_engine_substitution,no_zero_date,no_zero_in_date,only_full_group_by,pipes_as_concat
#sql_mode=strict_trans_tables

# use InnoDB for transactions and better crash recovery
default_storage_engine=innodb
# case-insensitive table names, avoids trouble on windows
lower_case_table_names=1
character_set_server=utf8
collation_server=utf8_general_ci
table_cache=200
thread_cache_size=3
#log_bin=mysql-bin
#expire_logs_days=3
#sync_bin_log=0
# error log file name, relative to datadir
log_error=mysql.err
log_warnings=2
# log all queries, useful for debugging but generates an enormous amount of data
#log=mysql.full
# log queries slower than n seconds, log file name relative to datadir (for debugging only)
#log_slow_queries=mysql.slow
#long_query_time=1
# log queries not using indices, debug only, disable for production use
#log_queries_not_using_indexes=1
# maximum blob size
max_allowed_packet=32M
max_connections=256
# makes sense when having the same query multiple times
# makes no sense with prepared statements and/or transactions
query_cache_type=0
query_cache_size=0

innodb_file_per_table=1
innodb_log_buffer_size=1M
innodb_additional_mem_pool_size=1M
# messure database size and adjust
# SELECT sum(data_length) as bla, sum(index_length) as blub FROM information_schema.tables WHERE table_schema not in ("mysql", "information_schema");
innodb_buffer_pool_size=80M
# size of average write burst, keep Innob_log_waits small, keep Innodb_buffer_pool_wait_free small (see show global status like "inno%", show global variables)
innodb_log_file_size=64M
innodb_flush_log_at_trx_commit=2

# Do not drop the connection to the DB after 8 hours of inactivity
wait_timeout=31536000

[client]
default-character-set=utf8


Test 9: SUCCESS
--------

akonadictl found and usable
Details: The program '/usr/bin/akonadictl' to control the Akonadi server was found and could be executed successfully.
Result:
Akonadi 1.6.2


Test 10: ERROR
--------

Akonadi control process not registered at D-Bus.
Details: The Akonadi control process is not registered at D-Bus which typically means it was not started or encountered a fatal error during startup.

Test 11: ERROR
--------

Akonadi server process not registered at D-Bus.
Details: The Akonadi server process is not registered at D-Bus which typically means it was not started or encountered a fatal error during startup.

Test 12: ERROR
--------

Nepomuk search service not registered at D-Bus.
Details: The Nepomuk search service is not registered at D-Bus which typically means it was not started or encountered a fatal error during startup.

Test 13: SKIP
--------

Protocol version check not possible.
Details: Without a connection to the server it is not possible to check if the protocol version meets the requirements.

Test 14: ERROR
--------

No resource agents found.
Details: No resource agents have been found, Akonadi is not usable without at least one. This usually means that no resource agents are installed or that there is a setup problem. The following paths have been searched: '/usr/share/akonadi/agents'. The XDG_DATA_DIRS environment variable is set to '/usr/local/share:/usr/share'; make sure this includes all paths where Akonadi agents are installed.

Directory listing of '/usr/share/akonadi/agents':
akonotesresource.desktop
birthdaysresource.desktop
calendarsearchagent.desktop
contactsresource.desktop
davgroupwareresource.desktop
icalresource.desktop
imapresource.desktop
invitationsagent.desktop
kabcresource.desktop
kcalresource.desktop
kdeaccountsresource.desktop
knutresource.desktop
kolabproxyresource.desktop
localbookmarksresource.desktop
maildirresource.desktop
maildispatcheragent.desktop
mboxresource.desktop
microblog.desktop
mixedmaildirresource.desktop
mtdummyresource.desktop
nepomukcalendarfeeder.desktop
nepomukcontactfeeder.desktop
nepomukemailfeeder.desktop
nepomuktagresource.desktop
nntpresource.desktop
notesresource.desktop
openxchangeresource.desktop
pop3resource.desktop
vcarddirresource.desktop
vcardresource.desktop

Environment variable XDG_DATA_DIRS is set to '/usr/local/share:/usr/share'

Test 15: ERROR
--------

Current Akonadi server error log found.
Details: The Akonadi server reported errors during its current startup. The log can be found in <a href='/home/enigma/.local/share/akonadi/akonadiserver.error'>/home/enigma/.local/share/akonadi/akonadiserver.error</a>.

File content of '/home/enigma/.local/share/akonadi/akonadiserver.error':
"[
0: akonadiserver(_Z11akBacktracev+0x37) [0x44e3a7]
1: akonadiserver() [0x44e7a2]
2: /lib64/libc.so.6(+0x35ad0) [0x7f5e724e9ad0]
3: /lib64/libc.so.6(gsignal+0x35) [0x7f5e724e9a55]
4: /lib64/libc.so.6(abort+0x185) [0x7f5e724ead55]
5: /usr/lib64/qt4/libQtCore.so.4(_Z17qt_message_output9QtMsgTypePKc+0x74) [0x7f5e7419e994]
6: /usr/lib64/qt4/libQtCore.so.4(+0x70b2d) [0x7f5e7419eb2d]
7: /usr/lib64/qt4/libQtCore.so.4(_Z6qFatalPKcz+0x95) [0x7f5e7419ecc5]
8: akonadiserver(_ZN13DbConfigMysql19startInternalServerEv+0x11c2) [0x4c9682]
9: akonadiserver(_ZN7Akonadi13AkonadiServer20startDatabaseProcessEv+0xd8) [0x450378]
10: akonadiserver(_ZN7Akonadi13AkonadiServerC1EP7QObject+0xc4) [0x451974]
11: akonadiserver(_ZN7Akonadi13AkonadiServer8instanceEv+0x4a) [0x452e9a]
12: akonadiserver(main+0x21e) [0x44962e]
13: /lib64/libc.so.6(__libc_start_main+0xfd) [0x7f5e724d609d]
14: akonadiserver() [0x449319]
]
"


Test 16: ERROR
--------

Previous Akonadi server error log found.
Details: The Akonadi server reported errors during its previous startup. The log can be found in <a href='/home/enigma/.local/share/akonadi/akonadiserver.error.old'>/home/enigma/.local/share/akonadi/akonadiserver.error.old</a>.

File content of '/home/enigma/.local/share/akonadi/akonadiserver.error.old':
"[
0: akonadiserver(_Z11akBacktracev+0x37) [0x44e3a7]
1: akonadiserver() [0x44e7a2]
2: /lib64/libc.so.6(+0x35ad0) [0x7feb43003ad0]
3: /lib64/libc.so.6(gsignal+0x35) [0x7feb43003a55]
4: /lib64/libc.so.6(abort+0x185) [0x7feb43004d55]
5: /usr/lib64/qt4/libQtCore.so.4(_Z17qt_message_output9QtMsgTypePKc+0x74) [0x7feb44cb8994]
6: /usr/lib64/qt4/libQtCore.so.4(+0x70b2d) [0x7feb44cb8b2d]
7: /usr/lib64/qt4/libQtCore.so.4(_Z6qFatalPKcz+0x95) [0x7feb44cb8cc5]
8: akonadiserver(_ZN13DbConfigMysql19startInternalServerEv+0x11c2) [0x4c9682]
9: akonadiserver(_ZN7Akonadi13AkonadiServer20startDatabaseProcessEv+0xd8) [0x450378]
10: akonadiserver(_ZN7Akonadi13AkonadiServerC1EP7QObject+0xc4) [0x451974]
11: akonadiserver(_ZN7Akonadi13AkonadiServer8instanceEv+0x4a) [0x452e9a]
12: akonadiserver(main+0x21e) [0x44962e]
13: /lib64/libc.so.6(__libc_start_main+0xfd) [0x7feb42ff009d]
14: akonadiserver() [0x449319]
]
"


Test 17: SUCCESS
--------

No current Akonadi control error log found.
Details: The Akonadi control process did not report any errors during its current startup.

Test 18: SUCCESS
--------

No previous Akonadi control error log found.
Details: The Akonadi control process did not report any errors during its previous startup.

Regards.

add mysql to use="..." on make.conf and install qt-sql solve the problems

Salutes!

This topic is marked "solved" but it is far from solved, in my opinion, for any reasonable definition of solved.

add mysql to use="..." on make.conf and install qt-sql solve the problems

Are you making a reference to re-compiling kmail? That seems like a losing strategy, but maybe I misunderstand.

In my Debian-based system (Kubuntu 14.04), qt-sql does not exist in the repositories.

I have all the same errors you listed above; my Kmail will not run. Here's how it got that way:

* I bought a new laptop and intalled Kubuntu 14.04.
* I used rsync to clone my home folder from my previous laptop to my new one

The installation on my previous laptop, with working Kmail, was Mint 16 KDE. I know that using rsync to clone a bunch of .config .directories is not the smartest thing to do. However, none of my other programs had a problem with this-- only Kmail. I have tried in the past to migrate Kmail from one machine to another, using the recommended export-from-one/import-to-another procedure, and this always results in me losing all or part of the configuration and emails from the prior account.

I believe the developers have lost sight of the reason people want to run their own mail client. The only reason I want to run Kmail is so I can capture emails to my own local machine, and archive them for a long period of time. This has been impossible for me, for at least five years, since every time I upgrade to a new distro or migrate to a new machine, I lose emails.

Is it clear I'm frustrated? I'm doing my best to be constructive: Kmail should be easy to migrate forward, but it is not. In KDE 3 it was a simple process, now it is impossible. This needs to be fixed.

Congress is demanding the IRS produce all emails to and from Lois Lerner. The IRS claims it lost all those emails. I've read several IT people who explain why it should be impossible for the IRS to have lost those emails, unless the people running their servers are incompetent. In my opinion, if the IRS simply claims they have been using Kmail, then it will be perfectly plausible that they have lost all their emails. "Lois got a new computer in her office, and she's using Kmail, so all her prior emails are gone." Case closed.

I'm not a programmer, but I'm not a noob either. I've been using Linux for 15 years. Is there some reasonably easy way I can fix this, without resorting to creating a new user folder, and migrating EVERYTHING else over to it, just so I can use Kmail, or should I kiss Kmail goodbye once an for all?

I will appreciate any suggestions, and please forgive the rant-- this is the first time I have ranted, through five years of frustration with this program. When it works, I love it, but it is far more difficult to maintain than it should be.

qt-sql has another name in the Debian / Ubuntu repositories, however I don't have access to such a machine to check. Basically, it is the MySQL plugin for Qt, which is often not installed by default.

I know that using rsync to clone a bunch of .config .directories is not the smartest thing to do. However, none of my other programs had a problem with this-- only Kmail. I have tried in the past to migrate Kmail from one machine to another, using the recommended export-from-one/import-to-another procedure, and this always results in me losing all or part of the configuration and emails from the prior account.

I understand there have been issues, but in such a case you need to file bugs on the export / import. There are so many different configurations that it is physically impossible to test them all. Also the PIM version matters: Debian stable ships with a PIM version that's years old and has issues that have been fixed in more recent version.

In particular rsyncing is a bad idea here exactly for this reason. Sometimes to fix bugs the internal data structures use by PIM change (there's a "protocol version" which is bumped when this occurs) and if you mix old with new, it is likely going to cause issues.

I appreciate your response, Einar.

This evening I decided to try again.

* I googled for "qt-sql"; discovered the package name is libqt4-sql-mysql. I already have the newest version installed (4.8.5)
* I set up a new user account.
* On my old laptop, I used PIM Setting Exporter (version 4.13.1) to save all my settings and data, including email
* I copied the resulting .zip file to the new laptop
* I used PIM to restore the file.

* It immediately warned me about folders which were part of the backup file, but which did not exist in the brand new user account. There was a dialog which enabled me to create the folders. After the third one, my X-Window session froze. I restarted X, tried again, and it froze again.

* I made a list of folders from my old laptop's Kmail, then created all the folders in the new account (which should be unneccesary-- a restore feature should create these folders).

* Ran PIM again. This time it didn't warn of missing folders, but it didn't know which folder to assign any filter to, even though the names were identical.

* I painstakingly selected each folder in turn, and it reported the operation was complete.

The result: Not a single one of my emails appeared in any folder.

Doing this the right way doesn't work.

Please file a bug on bugs.kde.org. It's probably the only way this can get fixed.