Version: 4.4.1 (using 4.4.1 (KDE 4.4.1), Kubuntu packages) Compiler: cc OS: Linux (i686) release 2.6.31-19-generic When I start Kontact, the Akonadi server is started, but that results in an error dialog with some red marks and KAdressbook is disabled. When I then open a shell and enter 'akonadictl start' the message 'Akonadi is already running' is printed. A after 'akonadictl stop', some seconds waiting and then 'akonadictl start' Akonadi starts up and KAdressbook comes to life. When I start akonadi manually with 'akonadictl start' before launching Kontact, the error dialog is not shown and KAdressbook works normally.
Hej Wilbert, and what exactly is printed after the red crosses? That would be an important information, because that's the reason why Akonadi server does not start the first time... Ciao, Tobias
Below is the copied report. Strange thing is that when I run akonadictl start *before* launching Kontact, everything runs as advertised. This only happens the first time after a boot (I use autologin). When I quit Kontact without stopping or restarting Akonadi, and then log off and back in again, Kontact starts akonadi without errors. ==================================================== 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/wilbert/.config/akonadi/akonadiserverrc': [%General] Driver=QMYSQL SizeThreshold=4096 ExternalPayload=false [QMYSQL] Name=akonadi Host= User= Password= Options="UNIX_SOCKET=/home/wilbert/.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.37-1ubuntu5 for debian-linux-gnu on i486 ((Ubuntu)) Test 4: ERROR -------- MySQL server log contains errors. Details: The MySQL server error log file '<a href='/home/wilbert/.local/share/akonadi/db_data/mysql.err'>/home/wilbert/.local/share/akonadi/db_data/mysql.err</a>' contains errors. File content of '/home/wilbert/.local/share/akonadi/db_data/mysql.err': 100308 11:19:49 [Note] Plugin 'FEDERATED' is disabled. 100308 11:19:50 InnoDB: Started; log sequence number 0 14415166 100308 11:19:51 [Warning] Can't open and lock time zone table: Table 'mysql.time_zone_leap_second' doesn't exist trying to live without them 100308 11:19:51 [ERROR] Can't open and lock privilege tables: Table 'mysql.servers' doesn't exist 100308 11:19:51 [ERROR] Cannot open mysql.db 100308 11:19:51 [ERROR] Cannot open mysql.user 100308 11:19:51 [ERROR] Cannot open mysql.event 100308 11:19:51 [ERROR] Event Scheduler: An error occurred when initializing system tables. 100308 11:19:51 [Note] /usr/sbin/mysqld-akonadi: ready for connections. Version: '5.1.37-1ubuntu5-log' socket: '/home/wilbert/.local/share/akonadi/db_misc/mysql.socket' port: 0 (Ubuntu) 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/wilbert/.local/share/akonadi/mysql.conf'>/home/wilbert/.local/share/akonadi/mysql.conf</a> and is readable. File content of '/home/wilbert/.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: SUCCESS -------- Akonadi control process registered at D-Bus. Details: The Akonadi control process is registered at D-Bus which typically indicates it is operational. Test 10: SUCCESS -------- Akonadi server process registered at D-Bus. Details: The Akonadi server process is registered at D-Bus which typically indicates it is operational. Test 11: 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 12: 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 13: 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 14: SUCCESS -------- No current Akonadi server error log found. Details: The Akonadi server did not report any errors during its current startup. Test 15: ERROR -------- Previous Akonadi server error log found. Details: The Akonadi server did report error during its previous startup into <a href='/home/wilbert/.local/share/akonadi/akonadiserver.error.old'>/home/wilbert/.local/share/akonadi/akonadiserver.error.old</a>. File content of '/home/wilbert/.local/share/akonadi/akonadiserver.error.old': Control process died, committing suicide! D-Bus session bus went down - quitting Test 16: SUCCESS -------- No current Akonadi control error log found. Details: The Akonadi control process did not report any errors during its current startup. Test 17: ERROR -------- Previous Akonadi control error log found. Details: The Akonadi control process did report error during its previous startup into <a href='/home/wilbert/.local/share/akonadi/akonadi_control.error.old'>/home/wilbert/.local/share/akonadi/akonadi_control.error.old</a>. File content of '/home/wilbert/.local/share/akonadi/akonadi_control.error.old': D-Bus session bus went down - quitting ====================================================
I'm experiencing something similar using KDE 4.4.1 on Arch Linux 64 bit: The first time I run Kontact, the Akonadi error window appears and Kontact is disabled. Closing and reopening Kontact a second time fixes the issue. This bug is marked as fixed but nowhere do I see an indication of the fix or the version containing the fix.
*** This bug has been marked as a duplicate of bug 224079 ***