Bug 549413 - kmail/akonadi falls over if kdepim-runtime is not present
Summary: kmail/akonadi falls over if kdepim-runtime is not present
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: kdepim
Version: rawhide
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Than Ngo
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: kde-4.4
TreeView+ depends on / blocked
 
Reported: 2009-12-21 16:24 UTC by Rex Dieter
Modified: 2009-12-21 16:43 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-12-21 16:43:34 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Rex Dieter 2009-12-21 16:24:11 UTC
Trying to run kmail, akonadi complains about missing akonadi resources.  Then kmail either quits or crashes.

Using kdepim-4.3.85 (and kdepim-runtime-4.3.85) here.


Ping upstream on whether kdepim really needs
Requires: kdepim-runtime
or if this is just a plain 'ol bug.

Comment 1 Rex Dieter 2009-12-21 16:24:42 UTC
From irc,
[10:23] <nucleo> but in 4.3.80 kmail not quits even without kdepim-runtime installed

Comment 2 Rex Dieter 2009-12-21 16:27:05 UTC
Maybe a data migration thing, I now uninstalled kdepim-runtime, and now things are still working ok.  fun.

Comment 3 Rex Dieter 2009-12-21 16:29:56 UTC
OK, I lied, nevermind comment #2.

*really* uninstalled kdepim-runtime, on kmail launch, tries to launch akonadi, and I get an "Akonadi Server Self-Test" window, with contents:

I'd venture the interesting stuff is Test 14.

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

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

[Debug]
Tracer=null


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

MySQL server found.
Details: You currently have configured Akonadi to use the MySQL server '/usr/libexec/mysqld'.
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/libexec/mysqld  Ver 5.1.40 for redhat-linux-gnu on x86_64 (Source distribution)


Test 4:  ERROR
--------

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

File content of '/home/rdieter1/.local/share/akonadi/db_data/mysql.err':
091221 10:28:14 [Note] Plugin 'ndbcluster' is disabled.
091221 10:28:14  InnoDB: Started; log sequence number 0 125390
091221 10:28:14 [Warning] Can't open and lock time zone table: Table 'mysql.time_zone_leap_second' doesn't exist trying to live without them
091221 10:28:14 [ERROR] Can't open and lock privilege tables: Table 'mysql.servers' doesn't exist
091221 10:28:14 [Note] /usr/libexec/mysqld: ready for connections.
Version: '5.1.40-log'  socket: '/home/rdieter1/.local/share/akonadi/db_misc/mysql.socket'  port: 0  Source distribution


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>
#
[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
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=8M
innodb_flush_log_at_trx_commit=2



Test 6:  SUCCESS
--------

MySQL server custom configuration found.
Details: The custom configuration for the MySQL server was found and is readable at <a href='/etc/akonadi/mysql-local.conf'>/etc/akonadi/mysql-local.conf</a>

File content of '/etc/akonadi/mysql-local.conf':


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

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

File content of '/home/rdieter1/.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>
#
[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
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=8M
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.2.80


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

Directory listing of '/usr/share/akonadi/agents':
nepomukemailfeeder.desktop

Environment variable XDG_DATA_DIRS is set to '/usr/share/kde-settings/kde-profile/default/share:/usr/local/share:/usr/share'

Test 15:  SUCCESS
--------

No current Akonadi server error log found.
Details: The Akonadi server did not report any errors during its current startup.

Test 16:  SUCCESS
--------

No previous Akonadi server error log found.
Details: The Akonadi server did not report any errors during its previous startup.

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.

Comment 4 Rex Dieter 2009-12-21 16:43:34 UTC
* Mon Dec 21 2009 Rex Dieter <rdieter> - 4.3.85-3
- Requires: kdepim-runtime (unconditionally)

I guess we'll just consider it a hard-dep (unless proven otherwise).


Note You need to log in before you can comment on or make changes to this bug.