Hi there I just updated my Kubuntu 15.04 with the Kubuntu Team KDE 5.3.1 PPA and now Akonadi won't start anymore - hence I'm unable to check email and stuff. Reproducible: Always Actual Results: [QMYSQL] Name=akonadi Host= Options="UNIX_SOCKET=/tmp/akonadi-hyper.FV8bti/mysql.socket" ServerPath=/usr/sbin/mysqld-akonadi StartServer=true [Debug] Tracer=null 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: /usr/sbin/mysqld Ver 5.6.24-0ubuntu2 for debian-linux-gnu on x86_64 ((Ubuntu)) Test 5: ERROR -------- MySQL server log contains errors. Details: The MySQL server error log file '<a href='/home/hyper/.local/share/akonadi/db_data/mysql.err'>/home/hyper/.local/share/akonadi/db_data/mysql.err</a>' contains errors. File content of '/home/hyper/.local/share/akonadi/db_data/mysql.err': 2015-05-30 08:33:06 3848 [Note] Plugin 'FEDERATED' is disabled. 2015-05-30 08:33:06 7fb53755e740 InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator. 2015-05-30 08:33:06 3848 [Note] InnoDB: Using atomics to ref count buffer pool pages 2015-05-30 08:33:06 3848 [Note] InnoDB: The InnoDB memory heap is disabled 2015-05-30 08:33:06 3848 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 2015-05-30 08:33:06 3848 [Note] InnoDB: Memory barrier is not used 2015-05-30 08:33:06 3848 [Note] InnoDB: Compressed tables use zlib 1.2.8 2015-05-30 08:33:06 3848 [Note] InnoDB: Using Linux native AIO 2015-05-30 08:33:06 3848 [Note] InnoDB: Using CPU crc32 instructions 2015-05-30 08:33:06 3848 [Note] InnoDB: Initializing buffer pool, size = 80.0M 2015-05-30 08:33:06 3848 [Note] InnoDB: Completed initialization of buffer pool 2015-05-30 08:33:06 3848 [Note] InnoDB: Highest supported file format is Barracuda. InnoDB: Database page corruption on disk or a failed InnoDB: file read of page 212. InnoDB: You may have to recover from a backup. 2015-05-30 08:33:06 7fb53755e740 InnoDB: Page dump in ascii and hex (16384 bytes): len 16384; hex [....] InnoDB: End of page dump 2015-05-30 08:33:06 7fb53755e740 InnoDB: uncompressed page, stored checksum in field1 31810981, calculated checksums for field1: crc32 3398403491, innodb 1971167555, none 3735928559, stored checksum in field2 2129773491, calculated checksums for field2: crc32 3398403491, innodb 2129773491, none 3735928559, page LSN 0 829873485, low 4 bytes of LSN at page end 829873485, page number (if stored to page already) 212, space id (if created with >= MySQL-4.1.1 and stored already) 0 InnoDB: Page may be a system page InnoDB: Database page corruption on disk or a failed InnoDB: file read of page 212. InnoDB: You may have to recover from a backup. InnoDB: It is also possible that your operating InnoDB: system has corrupted its own file cache InnoDB: and rebooting your computer removes the InnoDB: error. InnoDB: If the corrupt page is an index page InnoDB: you can also try to fix the corruption InnoDB: by dumping, dropping, and reimporting InnoDB: the corrupt table. You can use CHECK InnoDB: TABLE to scan your table for corruption. InnoDB: See also http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html InnoDB: about forcing recovery. InnoDB: Ending processing because of a corrupt database page. 2015-05-30 08:33:06 7fb53755e740 InnoDB: Assertion failure in thread 140416294184768 in file buf0buf.cc line 4201 InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to http://bugs.mysql.com. InnoDB: If you get repeated assertion failures or crashes, even InnoDB: immediately after the mysqld startup, there may be InnoDB: corruption in the InnoDB tablespace. Please refer to InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html InnoDB: about forcing recovery. 06:33:06 UTC - mysqld got signal 6 ; This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked against is corrupt, improperly built, or misconfigured. This error can also be caused by malfunctioning hardware. We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail. key_buffer_size=16384 read_buffer_size=131072 max_used_connections=0 max_threads=256 thread_count=0 connection_count=0 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 101584 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x0 Attempting backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong... stack_bottom = 0 thread_stack 0x40000 /usr/sbin/mysqld(my_print_stacktrace+0x3b)[0x8e09db] /usr/sbin/mysqld(handle_fatal_signal+0x36a)[0x64338a] /lib/x86_64-linux-gnu/libpthread.so.0(+0x10d10)[0x7fb5366f9d10] /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x37)[0x7fb535d3d267] /lib/x86_64-linux-gnu/libc.so.6(abort+0x16a)[0x7fb535d3eeca] /usr/sbin/mysqld[0xa6d57f] /usr/sbin/mysqld[0xa80788] /usr/sbin/mysqld[0xa686ac] /usr/sbin/mysqld[0xa236d2] /usr/sbin/mysqld[0xa2427d] /usr/sbin/mysqld[0xa251bf] /usr/sbin/mysqld[0xa0f9da] /usr/sbin/mysqld[0x94d274] /usr/sbin/mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x48)[0x57da08] /usr/sbin/mysqld[0x6d27c5] /usr/sbin/mysqld(_Z11plugin_initPiPPci+0x868)[0x6d8f08] /usr/sbin/mysqld(_Z11mysqld_mainiPPc+0x925)[0x575a05] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0)[0x7fb535d28a40] /usr/sbin/mysqld(_start+0x29)[0x569eb9] The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains information that should help you find out what is causing the crash. 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 <kris@mysql.com> # [mysqld] # 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 # DEBUGGING: # 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 # # 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"); # NOTES: # Keep Innob_log_waits and keep Innodb_buffer_pool_wait_free small (see show global status like "inno%", show global variables) #expire_logs_days=3 #sync_bin_log=0 # Use UTF-8 encoding for tables character_set_server=utf8 collation_server=utf8_general_ci # use InnoDB for transactions and better crash recovery default_storage_engine=innodb # memory pool InnoDB uses to store data dictionary information and other internal data structures (default:1M) # Deprecated in MySQL >= 5.6.3 innodb_additional_mem_pool_size=1M # memory buffer InnoDB uses to cache data and indexes of its tables (default:128M) # Larger values means less I/O innodb_buffer_pool_size=80M # Create a .ibd file for each table (default:0) innodb_file_per_table=1 # Write out the log buffer to the log file at each commit (default:1) innodb_flush_log_at_trx_commit=2 # Buffer size used to write to the log files on disk (default:1M for builtin, 8M for plugin) # larger values means less I/O innodb_log_buffer_size=1M # Size of each log file in a log group (default:5M) larger means less I/O but more time for recovery. innodb_log_file_size=64M # # error log file name, relative to datadir (default:hostname.err) log_error=mysql.err # print warnings and connection errors (default:1) log_warnings=2 # Convert table named to lowercase lower_case_table_names=1 # Maximum size of one packet or any generated/intermediate string. (default:1M) max_allowed_packet=32M # Maximum simultaneous connections allowed (default:100) max_connections=256 # 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)) query_cache_size=0 # Do not cache results (default:1) query_cache_type=0 # Do not use the privileges mechanisms skip_grant_tables # Do not listen for TCP/IP connections at all skip_networking # The number of open tables for all threads. (default:64) table_open_cache=200 # How many threads the server should cache for reuse (default:0) thread_cache_size=3 # wait 365d before dropping the DB connection (default:8h) wait_timeout=31536000 # We use InnoDB, so don't let MyISAM eat up memory key_buffer_size=16K [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/hyper/.local/share/akonadi/mysql.conf'>/home/hyper/.local/share/akonadi/mysql.conf</a> and is readable. File content of '/home/hyper/.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] # 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 # DEBUGGING: # 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 # # 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"); # NOTES: # Keep Innob_log_waits and keep Innodb_buffer_pool_wait_free small (see show global status like "inno%", show global variables) #expire_logs_days=3 #sync_bin_log=0 # Use UTF-8 encoding for tables character_set_server=utf8 collation_server=utf8_general_ci # use InnoDB for transactions and better crash recovery default_storage_engine=innodb # memory pool InnoDB uses to store data dictionary information and other internal data structures (default:1M) # Deprecated in MySQL >= 5.6.3 innodb_additional_mem_pool_size=1M # memory buffer InnoDB uses to cache data and indexes of its tables (default:128M) # Larger values means less I/O innodb_buffer_pool_size=80M # Create a .ibd file for each table (default:0) innodb_file_per_table=1 # Write out the log buffer to the log file at each commit (default:1) innodb_flush_log_at_trx_commit=2 # Buffer size used to write to the log files on disk (default:1M for builtin, 8M for plugin) # larger values means less I/O innodb_log_buffer_size=1M # Size of each log file in a log group (default:5M) larger means less I/O but more time for recovery. innodb_log_file_size=64M # # error log file name, relative to datadir (default:hostname.err) log_error=mysql.err # print warnings and connection errors (default:1) log_warnings=2 # Convert table named to lowercase lower_case_table_names=1 # Maximum size of one packet or any generated/intermediate string. (default:1M) max_allowed_packet=32M # Maximum simultaneous connections allowed (default:100) max_connections=256 # 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)) query_cache_size=0 # Do not cache results (default:1) query_cache_type=0 # Do not use the privileges mechanisms skip_grant_tables # Do not listen for TCP/IP connections at all skip_networking # The number of open tables for all threads. (default:64) table_open_cache=200 # How many threads the server should cache for reuse (default:0) thread_cache_size=3 # wait 365d before dropping the DB connection (default:8h) wait_timeout=31536000 # We use InnoDB, so don't let MyISAM eat up memory key_buffer_size=16K [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.13.0 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: 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'. The XDG_DATA_DIRS environment variable is set to '/usr/share/plasma:/usr/local/share/:/usr/share/'; make sure this includes all paths where Akonadi agents are installed. Directory listing of '/usr/share/akonadi/agents': akonadibalooindexingagent.desktop akonadinepomukfeederagent.desktop akonotesresource.desktop archivemailagent.desktop birthdaysresource.desktop contactsresource.desktop davgroupwareresource.desktop facebookresource.desktop folderarchiveagent.desktop followupreminder.desktop googlecalendarresource.desktop googlecontactsresource.desktop icaldirresource.desktop icalresource.desktop imapresource.desktop invitationsagent.desktop kabcresource.desktop kalarmdirresource.desktop kalarmresource.desktop kcalresource.desktop kdeaccountsresource.desktop kolabproxyresource.desktop kolabresource.desktop localbookmarksresource.desktop maildirresource.desktop maildispatcheragent.desktop mailfilteragent.desktop mboxresource.desktop migrationagent.desktop mixedmaildirresource.desktop mtdummyresource.desktop newmailnotifieragent.desktop nntpresource.desktop notesagent.desktop notesresource.desktop openxchangeresource.desktop pop3resource.desktop sendlateragent.desktop vcarddirresource.desktop vcardresource.desktop Environment variable XDG_DATA_DIRS is set to '/usr/share/plasma:/usr/local/share/:/usr/share/' Test 14: 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/hyper/.local/share/akonadi/akonadiserver.error'>/home/hyper/.local/share/akonadi/akonadiserver.error</a>. File content of '/home/hyper/.local/share/akonadi/akonadiserver.error': Database process exited unexpectedly during initial connection! executable: "/usr/sbin/mysqld-akonadi" arguments: ("--defaults-file=/home/hyper/.local/share/akonadi/mysql.conf", "--datadir=/home/hyper/.local/share/akonadi/db_data/", "--socket=/tmp/akonadi-hyper.FV8bti/mysql.socket") stdout: "" stderr: "2015-05-30 08:33:06 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details). 2015-05-30 08:33:06 0 [Note] /usr/sbin/mysqld (mysqld 5.6.24-0ubuntu2) starting as process 3848 ... " exit code: 1 process error: "Process operation timed out" "[ 0: akonadiserver() [0x418c8a] 1: akonadiserver() [0x418f04] 2: /lib/x86_64-linux-gnu/libc.so.6(+0x352f0) [0x7f9f840932f0] 3: /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x37) [0x7f9f84093267] 4: /lib/x86_64-linux-gnu/libc.so.6(abort+0x16a) [0x7f9f84094eca] 5: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(_Z17qt_message_output9QtMsgTypePKc+0x12a) [0x7f9f858bda8a] 6: akonadiserver() [0x41ad0d] 7: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(_ZN9QIODevice5writeEPKcx+0x8a) [0x7f9f8595d30a] 8: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(+0x121155) [0x7f9f8596d155] 9: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(_ZN11QTextStreamD1Ev+0x31) [0x7f9f85975ab1] 10: akonadiserver() [0x48235e] 11: akonadiserver() [0x41b90f] 12: akonadiserver() [0x41dff8] 13: akonadiserver() [0x4e2e49] 14: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(_ZN7QObject5eventEP6QEvent+0x1e1) [0x7f9f859ec891] 15: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(_ZN16QCoreApplication14notifyInternalEP7QObjectP6QEvent+0x8d) [0x7f9f859d317d] 16: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(_ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData+0x231) [0x7f9f859d6a21] 17: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(+0x1b669e) [0x7f9f85a0269e] 18: /lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_dispatch+0x24d) [0x7f9f8375bc3d] 19: /lib/x86_64-linux-gnu/libglib-2.0.so.0(+0x49f20) [0x7f9f8375bf20] 20: /lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_iteration+0x2c) [0x7f9f8375bfcc] 21: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(_ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE+0x7e) [0x7f9f85a0280e] 22: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(_ZN10QEventLoop13processEventsE6QFlagsINS_17ProcessEventsFlagEE+0x41) [0x7f9f859d1cd1] 23: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(_ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE+0x1a5) [0x7f9f859d2035] 24: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(_ZN16QCoreApplication4execEv+0x99) [0x7f9f859d7ab9] 25: akonadiserver() [0x4131b5] 26: /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0) [0x7f9f8407ea40] 27: akonadiserver(_start+0x29) [0x413be9] ] " Test 15: 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/hyper/.local/share/akonadi/akonadiserver.error.old'>/home/hyper/.local/share/akonadi/akonadiserver.error.old</a>. File content of '/home/hyper/.local/share/akonadi/akonadiserver.error.old': Database process exited unexpectedly during initial connection! executable: "/usr/sbin/mysqld-akonadi" arguments: ("--defaults-file=/home/hyper/.local/share/akonadi/mysql.conf", "--datadir=/home/hyper/.local/share/akonadi/db_data/", "--socket=/tmp/akonadi-hyper.FV8bti/mysql.socket") stdout: "" stderr: "2015-05-30 08:33:03 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details). 2015-05-30 08:33:03 0 [Note] /usr/sbin/mysqld (mysqld 5.6.24-0ubuntu2) starting as process 3816 ... " exit code: 1 process error: "Process operation timed out" "[ 0: akonadiserver() [0x418c8a] 1: akonadiserver() [0x418f04] 2: /lib/x86_64-linux-gnu/libc.so.6(+0x352f0) [0x7f8172b282f0] 3: /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x37) [0x7f8172b28267] 4: /lib/x86_64-linux-gnu/libc.so.6(abort+0x16a) [0x7f8172b29eca] 5: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(_Z17qt_message_output9QtMsgTypePKc+0x12a) [0x7f8174352a8a] 6: akonadiserver() [0x41ad0d] 7: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(_ZN9QIODevice5writeEPKcx+0x8a) [0x7f81743f230a] 8: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(+0x121155) [0x7f8174402155] 9: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(_ZN11QTextStreamD1Ev+0x31) [0x7f817440aab1] 10: akonadiserver() [0x48235e] 11: akonadiserver() [0x41b90f] 12: akonadiserver() [0x41dff8] 13: akonadiserver() [0x4e2e49] 14: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(_ZN7QObject5eventEP6QEvent+0x1e1) [0x7f8174481891] 15: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(_ZN16QCoreApplication14notifyInternalEP7QObjectP6QEvent+0x8d) [0x7f817446817d] 16: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(_ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData+0x231) [0x7f817446ba21] 17: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(+0x1b669e) [0x7f817449769e] 18: /lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_dispatch+0x24d) [0x7f81721f0c3d] 19: /lib/x86_64-linux-gnu/libglib-2.0.so.0(+0x49f20) [0x7f81721f0f20] 20: /lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_iteration+0x2c) [0x7f81721f0fcc] 21: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(_ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE+0x7e) [0x7f817449780e] 22: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(_ZN10QEventLoop13processEventsE6QFlagsINS_17ProcessEventsFlagEE+0x41) [0x7f8174466cd1] 23: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(_ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE+0x1a5) [0x7f8174467035] 24: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(_ZN16QCoreApplication4execEv+0x99) [0x7f817446cab9] 25: akonadiserver() [0x4131b5] 26: /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0) [0x7f8172b13a40] 27: akonadiserver(_start+0x29) [0x413be9] ] " 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: SUCCESS -------- No previous Akonadi control error log found. Details: The Akonadi control process did not report any errors during its previous startup.
As mentioned in the output, there is a database corruption, so you need to fix it manually (look for InnoDB corruption on Google) or scrap everything and configure Akonadi from start. The database is located in ~/.local/share/db_data.
This bug has never been confirmed for a Kontact version that is based on KDE Frameworks, except possibly a Technology Preview version 5.0.x. Those versions differ significantly from the old 4.x series. Therefore, I plan to close it in around two or three months. In the meantime, it is set to WAITINGFORINFO to give reporters the opportunity to check if it is still valid. As soon as someone confirms it for a recent version (at least 5.1, ideally even more recent), I'll gladly reopen it. Please understand that we lack the manpower to triage bugs reported for versions almost two years beyond their end of life.
Why even bother to report bugs if thats how they are handled?
What response did you expect if you never added feedback after suggestions given in comment #1?
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!