When launching kmail, it says that akonadi is not running, and there is a start button right below it. Clicking the start button does nothing. There are no errors and nothing shown in the console. Reproducible: Always Steps to Reproduce: na 2. 3. Actual Results: na Expected Results: na na
@Laurent: I think I can confirm it with master: kquitapp kmail akonadictl stop then start kmail The server is started in the background but the overlay screen doesn't disappear
Ah ? Will look at it this night.
For the moment I can't reproduce it. Will continue to investigate.
Hi Akonadi never starts automatically on KDE startup on my system. This has happened for the last few point releases of KDE (Kubuntu packages) I right click the Akonadi tray icon and click "Start..." and it starts. Telepathy then works. Going to the server configuration and hitting Test I see some errors for previous log files: akonadiserver.error.old Control process died, committing suicide! D-Bus session bus went down - quitting akonadi_control.error void AgentManager::load() Reference to unknown agent type "akonadi_archivemail_agent" in agentsrc void AgentManager::load() Reference to unknown agent type "akonadi_mailfilter_agent" in agentsrc akonadi_control.error.old void AgentManager::load() Reference to unknown agent type "akonadi_archivemail_agent" in agentsrc void AgentManager::load() Reference to unknown agent type "akonadi_mailfilter_agent" in agentsrc D-Bus session bus went down - quitting mysql.err 130213 9:35:57 [Note] Plugin 'FEDERATED' is disabled. 130213 9:35:57 InnoDB: The InnoDB memory heap is disabled 130213 9:35:57 InnoDB: Mutexes and rw_locks use GCC atomic builtins 130213 9:35:57 InnoDB: Compressed tables use zlib 1.2.7 130213 9:35:57 InnoDB: Using Linux native AIO 130213 9:35:57 InnoDB: Initializing buffer pool, size = 80.0M 130213 9:35:57 InnoDB: Completed initialization of buffer pool 130213 9:35:57 InnoDB: highest supported file format is Barracuda. 130213 9:35:57 InnoDB: Waiting for the background threads to start 130213 9:35:58 InnoDB: 1.1.8 started; log sequence number 1916168 130213 9:35:58 [Warning] Can't open and lock time zone table: Table 'mysql.time_zone_leap_second' doesn't exist trying to live without them 130213 9:35:58 [ERROR] Can't open and lock privilege tables: Table 'mysql.servers' doesn't exist 130213 9:35:58 [ERROR] Native table 'performance_schema'.'events_waits_current' has the wrong structure 130213 9:35:58 [ERROR] Native table 'performance_schema'.'events_waits_history' has the wrong structure 130213 9:35:58 [ERROR] Native table 'performance_schema'.'events_waits_history_long' has the wrong structure 130213 9:35:58 [ERROR] Native table 'performance_schema'.'setup_consumers' has the wrong structure 130213 9:35:58 [ERROR] Native table 'performance_schema'.'setup_instruments' has the wrong structure 130213 9:35:58 [ERROR] Native table 'performance_schema'.'setup_timers' has the wrong structure 130213 9:35:58 [ERROR] Native table 'performance_schema'.'performance_timers' has the wrong structure 130213 9:35:58 [ERROR] Native table 'performance_schema'.'threads' has the wrong structure 130213 9:35:58 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_thread_by_event_name' has the wrong structure 130213 9:35:58 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_instance' has the wrong structure 130213 9:35:58 [ERROR] Native table 'performance_schema'.'events_waits_summary_global_by_event_name' has the wrong structure 130213 9:35:58 [ERROR] Native table 'performance_schema'.'file_summary_by_event_name' has the wrong structure 130213 9:35:58 [ERROR] Native table 'performance_schema'.'file_summary_by_instance' has the wrong structure 130213 9:35:58 [ERROR] Native table 'performance_schema'.'mutex_instances' has the wrong structure 130213 9:35:58 [ERROR] Native table 'performance_schema'.'rwlock_instances' has the wrong structure 130213 9:35:58 [ERROR] Native table 'performance_schema'.'cond_instances' has the wrong structure 130213 9:35:58 [ERROR] Native table 'performance_schema'.'file_instances' has the wrong structure 130213 9:35:58 [Note] /usr/sbin/mysqld: ready for connections. Version: '5.5.29-0ubuntu0.12.10.1' socket: '/home/XXXXX/.local/share/akonadi/socket-riba.webqs.com/mysql.socket' port: 0 (Ubuntu) If it helps, I don't use Kmail or Korganizer etc (as Akonadi never worked properly and it couldn't handle my mail volume). I think the only Akonadi based app I use is Telepathy. Nepomuk: Desktop search services are active. File indexing service is off Email indexing is on Hope that helps out... Cheers James
Hi KDE folks This is still happening in KDE 4.10.x. On KDE startup Akonadi never starts, right clicking the tray icon and choosing "Start Akonadi" makes it start up and Instant Messaging starts working. The same log errors appear as in the previous comment. Are there any other logs I should look in to help out resolve this ? Thanks James
The mysql.err suggests there might be something wrong with the MySQL database. If you can still reproduce this problem, please wipe your Akonadi setup first (that is delete ~/.local/share/akonadi and ~/.config/akonadi), then open konsole and type: akonadictl start and copy/paste here all the output that it generates.
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!