this is the crash report :
Akonadi Server Self-Test Report
Test 1: SUCCESS
Database driver found.
Details: The QtSQL driver 'QMYSQL' is required by your current Akonadi server configuration and was found on your system.
File content of '/home/chajalleluia/.config/akonadi/akonadiserverrc':
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-akonadi'.
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: 140119 17:01:15 [Warning] Using unique option prefix key_buffer instead of key_buffer_size is deprecated and will be removed in a future release. Please use the full name instead.
/usr/sbin/mysqld Ver 5.5.34-0ubuntu0.13.10.1 for debian-linux-gnu on x86_64 ((Ubuntu))
Test 5: SUCCESS
No current MySQL error log found.
Details: The MySQL server did not report any errors during this startup. The log can be found in '/home/chajalleluia/.local/share/akonadi/db_data/mysql.err'.
Test 6: SUCCESS
MySQL server default configuration found.
Details: The default configuration for the MySQL server was found and is readable at <a href='/etc/akonadi/mysql-global.conf'>/etc/akonadi/mysql-global.conf</a>.
File content of '/etc/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 <firstname.lastname@example.org>
# strict query parsing/interpretation
# TODO: make Akonadi work with those settings enabled
# log all queries, useful for debugging but generates an enormous amount of data
# log queries slower than n seconds, log file name relative to datadir (for debugging only)
# log queries not using indices, debug only, disable for production use
# mesure database size and adjust innodb_buffer_pool_size
# SELECT sum(data_length) as bla, sum(index_length) as blub FROM information_schema.tables WHERE table_schema not in ("mysql", "information_schema");
# Keep Innob_log_waits and keep Innodb_buffer_pool_wait_free small (see show global status like "inno%", show global variables)
# Use UTF-8 encoding for tables
# use InnoDB for transactions and better crash recovery
# memory pool InnoDB uses to store data dictionary information and other internal data structures (default:1M)
# Deprecated in MySQL >= 5.6.3
# memory buffer InnoDB uses to cache data and indexes of its tables (default:128M)
# Larger values means less I/O
# Create a .ibd file for each table (default:0)
# Write out the log buffer to the log file at each commit (default:1)
# Buffer size used to write to the log files on disk (default:1M for builtin, 8M for plugin)
# larger values means less I/O
# Size of each log file in a log group (default:5M) larger means less I/O but more time for recovery.
# # error log file name, relative to datadir (default:hostname.err)
# print warnings and connection errors (default:1)
# Convert table named to lowercase
# Maximum size of one packet or any generated/intermediate string. (default:1M)
# Maximum simultaneous connections allowed (default:100)
# The two options below make no sense with prepared statements and/or transactions
# (make sense when having the same query multiple times)
# Memory allocated for caching query results (default:0 (disabled))
# Do not cache results (default:1)
# Do not use the privileges mechanisms
# Do not listen for TCP/IP connections at all
# The number of open tables for all threads. (default:64)
# How many threads the server should cache for reuse (default:0)
# wait 365d before dropping the DB connection (default:8h)
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: ERROR
MySQL server configuration not found or not readable.
Details: The MySQL server configuration was not found or is not readable.
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.
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: SUCCESS
Nepomuk search service registered at D-Bus.
Details: The Nepomuk search service is registered at D-Bus which typically indicates it is operational.
Test 13: SUCCESS
Nepomuk search service uses an appropriate backend.
Details: The Nepomuk search service uses one of the recommended backends.
Test 14: 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 15: 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/share:/usr/share/kde-plasma:/usr/local/share/:/usr/share/'; make sure this includes all paths where Akonadi agents are installed.
Directory listing of '/usr/share/akonadi/agents':
Environment variable XDG_DATA_DIRS is set to '/usr/share:/usr/share/kde-plasma:/usr/local/share/:/usr/share/'
Test 16: SUCCESS
No current Akonadi server error log found.
Details: The Akonadi server did not report any errors during its current startup.
Test 17: SUCCESS
No previous Akonadi server error log found.
Details: The Akonadi server did not report any errors during its previous startup.
Test 18: SUCCESS
No current Akonadi control error log found.
Details: The Akonadi control process did not report any errors during its current startup.
Test 19: SUCCESS
No previous Akonadi control error log found.
Details: The Akonadi control process did not report any errors during its previous startup.
I've already done as specified in bug 326480 : deleted my folder ~/.local/share/akonadi and it has changed nothing.
but I suppose there's a hacking problem because we have passwords sent by mail and registered on KMail which have been stolen.
This bug has only been reported for versions older than KDEPIM 4.14 (at most akonadi-1.3). Can anyone tell if this bug still present?
If noone confirms this bug for a recent version of akonadi (part of KDE Applications 15.08 or later), it gets closed in about three months.
Created attachment 102040 [details]
Akonadi self-test report
I have similar symptoms with PIM 4.14.2. This is with a fresh install of Mint 17.3. I thought perhaps I'd broken something during the installation until I saw other people have had similar problems.
Grateful for any ideas.
Actually, the solution to Bug 362138 from Ekeluo Chukwuogor seems to have worked for me, too. Thank you Ekeluo.
*** This bug has been marked as a duplicate of bug 362138 ***