I am running a fresh install of Kubuntu Lucid 10.04. After bootup if i look at the Akonadi System Tray Utility it reports that Akonadi isnt running. The first 2 errors under the details are :-
Akonadi control process not registered at D-bus
Akonadi server process not registered at D-bus
However if i go into the Akonadi Server Configuration and start it, it then runs fine, with the only error reported using test is that there is a previous error log. Any ideas

Can you please paste the error log (the previous one) here?

In .local/share/akonadi/akonadiserver.error.old

Control process died, committing suicide!

Very unusual. Was this after you had restarted it or just after logging in? If it was after login, the current file is needed, as that error file is likely from logout.

To be honest I am not sure. Which log are you after and where do i find it. i did keep a copy of the report that popped up when i looked at akonadi system tray if that is what your after

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/timbo/.config/akonadi/akonadiserverrc':
[%General]
Driver=QMYSQL
SizeThreshold=4096
ExternalPayload=false

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

[Debug]
Tracer=null


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

MySQL server found.
Details: You currently have 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 locations varies depending on the distribution.

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

MySQL server is executable.
Details: MySQL server found: /usr/sbin/mysqld-akonadi Ver 5.1.41-3ubuntu11 for debian-linux-gnu on i486 ((Ubuntu))


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

MySQL server log contains no errors.
Details: The MySQL server log file &apos;<a href='/home/timbo/.local/share/akonadi/db_data/mysql.err'>/home/timbo/.local/share/akonadi/db_data/mysql.err</a>&apos; does not contain any errors or warnings.

File content of '/home/timbo/.local/share/akonadi/db_data/mysql.err':
101201 15:25:58 [Note] Plugin 'FEDERATED' is disabled.
101201 15:25:59 InnoDB: Started; log sequence number 0 140116
101201 15:25:59 [Note] /usr/sbin/mysqld-akonadi: ready for connections.
Version: '5.1.41-3ubuntu11-log' socket: '/home/timbo/.local/share/akonadi/db_misc/mysql.socket' port: 0 (Ubuntu)
101201 19:10:44 [Note] /usr/sbin/mysqld-akonadi: Normal shutdown

101201 19:10:44 InnoDB: Starting shutdown...
101201 19:10:46 InnoDB: Shutdown completed; log sequence number 0 140166
101201 19:10:46 [Note] /usr/sbin/mysqld-akonadi: Shutdown complete



Test 5: 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 <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=latin1
collation_server=latin1_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



Test 6: SKIP
--------

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

Test 7: SUCCESS
--------

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

File content of '/home/timbo/.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=latin1
collation_server=latin1_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



Test 8: 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.3.1


Test 9: 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 10: 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 11: 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 12: SUCCESS
--------

Nepomuk search service uses an appropriate backend.
Details: The Nepomuk search service uses one of the recommended backends.

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 /usr/share/akonadi/agents'. The XDG_DATA_DIRS environment variable is set to '/usr/share:/usr/share:/usr/local/share', make sure this includes all paths where Akonadi agents are installed to.

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

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

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

Current Akonadi server error log found.
Details: The Akonadi server did report error during startup into <a href='/home/timbo/.local/share/akonadi/akonadiserver.error'>/home/timbo/.local/share/akonadi/akonadiserver.error</a>.

File content of '/home/timbo/.local/share/akonadi/akonadiserver.error':
Control process died, committing suicide!


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

Previous Akonadi server error log found.
Details: The Akonadi server did report error during its previous startup into <a href='/home/timbo/.local/share/akonadi/akonadiserver.error.old'>/home/timbo/.local/share/akonadi/akonadiserver.error.old</a>.

File content of '/home/timbo/.local/share/akonadi/akonadiserver.error.old':
Control process died, committing suicide!


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.

Ok, it looks like akonadi_control is somehow crashing or otherwise quitting during the startup process, which is unusual. Can you try adding the following to a executable script in ~/.kde4/Autostart/?

Code: Select all

akonadictl start

i added akonadictl start (create symlink box ticked) however it still isnt running. There is an additional error but i think this refers to the previous session.

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

File content of '/home/timbo/.local/share/akonadi/db_data/mysql.err':
101202 7:35:25 [Note] Plugin 'FEDERATED' is disabled.
101202 7:35:26 InnoDB: Started; log sequence number 0 140166
101202 7:35:26 [Note] /usr/sbin/mysqld-akonadi: ready for connections.
Version: '5.1.41-3ubuntu11-log' socket: '/home/timbo/.local/share/akonadi/db_misc/mysql.socket' port: 0 (Ubuntu)
101202 15:35:27 [Warning] Aborted connection 3 to db: 'akonadi' user: 'timbo' host: '' (Got timeout reading communication packets)
101202 15:35:27 [Warning] Aborted connection 4 to db: 'akonadi' user: 'timbo' host: '' (Got timeout reading communication packets)
101202 15:35:27 [Warning] Aborted connection 5 to db: 'akonadi' user: 'timbo' host: '' (Got timeout reading communication packets)
101202 15:35:28 [Warning] Aborted connection 7 to db: 'akonadi' user: 'timbo' host: '' (Got timeout reading communication packets)
101202 21:32:28 [Warning] Aborted connection 6 to db: 'akonadi' user: 'timbo' host: '' (Got timeout reading communication packets)
101204 7:38:05 [Note] /usr/sbin/mysqld-akonadi: Normal shutdown

101204 7:38:05 InnoDB: Starting shutdown...
101204 7:38:07 InnoDB: Shutdown completed; log sequence number 0 140682

Once again pressing the start button in the Akonadi System tray gets it going

Does it work properly under a new user?

I created a new user logged out and then back in with the new user.I then got an additional 2 errors
MYSQL server not found
Executing MYSQL server failed.
Rebooting the machine i got the same 2 additional errors with the new user. when i then logged out and back in as the original user i got the following from KCMinit The KDE Crash Handler
Executable: kdeinit4 PID: 1664 Signal: 11 (Segmentation fault)
With the original user i'm back to the previous errors and akonadi will start from the system tray. Do i have to setup akonadi for the new user?

When i was using Kubuntu Lucid previously on this laptop it worked fine but this was an upgrade from Karmic. I installed Lucid from scratch (formatted hard drive) only because having upgraded to Meerkat and then tried to upgrade KDE to the latest release i ended up with the computer hanging with a blank screen after login

Akonadi should not need to be setup for new users... it should work out of the box fine. It sounds like it is having problems finding mysqld to start it up. Unfortunately I don't know why your previous user is having problems.

Maybe you are hit by this one?
http://userbase.kde.org/Akonadi_4.4/Tro ... 29_Upgrade

Alternatively you could check this entry (older Ubuntu specific problem)
http://userbase.kde.org/Akonadi_4.4/Tro ... g#Apparmor

Cheers,
_

I tried the second suggestion (as it was a clean install i ignored the first) but alas it makes no difference. i guess i will just have to carry on manually starting it until the next release in April whereupon i shall install from scratch and hope for better luck.