appimage-packages / kmail

KDE Kmail Appimage
https://s3-eu-central-1.amazonaws.com/ds9-apps/kmail-master-appimage/kmail-git20170302-x86_64.AppImage
2 stars 0 forks source link

The akonadi personal management service is not running #10

Closed probonopd closed 7 years ago

probonopd commented 7 years ago

When launching KMail for the first time, I get "The akonadi personal management service is not running". There is a start button and when I press it, it seems to start akonadi. So I wonder whether we should launch akonadi from the AppRun bash script if it is not already running, and then launch KMail itself. This would possibly remove the need to press the button.

ScarlettGatelyMoore commented 7 years ago

Sure I had it that way, but it starts automatically for me, odd. Will make it so after this long image rebuild

probonopd commented 7 years ago

I only have to press the button for the very first time I launch an KMail AppImage on a freshly-booted system. Thereafter I don't have to to this again because actually processes from earlier invocations kept running in the background (i.e., were not killed after KMail itself exited), as per https://github.com/appimage-packages/kmail/issues/11

probonopd commented 7 years ago

https://s3-eu-central-1.amazonaws.com/ds9-apps/kmail-master-appimage/kmail-git20170221-18:02:00-x86_64.AppImage still has

screenshot at 2017-02-21 19 48 52

Pressing the Start button, everything works, but Akonadi processes don't get killed when one closes KMail.

star-buck commented 7 years ago

i still get this with latest version.... seems close to working though :)

probonopd commented 7 years ago

Let's find out what KMail does when you press the start button, and let's do the exact same thing from the bash script.

probonopd commented 7 years ago

When running on neon-useredition-current.iso I get a different result:

screenshot_20170222_191340 screenshot_20170222_191414

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 '/home/me/.config/akonadi/akonadiserverrc' could not be opened

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:  ERROR
--------

MySQL server not found.
Details: You have currently configured Akonadi to use the MySQL server ''.
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:  ERROR
--------

Executing the MySQL server failed.
Details: Executing the MySQL server '' failed with the following error message: ''

Test 5:  SUCCESS
--------

No current MySQL error log found.
Details: The MySQL server did not report any errors during this startup. The log can be found in '/mysql.err'.

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

MySQL server default configuration found.
Details: The default configuration for the MySQL server was found and is readable at <a href="/tmp/.mount_kjBI6J/etc/xdg/akonadi/mysql-global.conf">/tmp/.mount_kjBI6J/etc/xdg/akonadi/mysql-global.conf</a>.

File content of '/tmp/.mount_kjBI6J/etc/xdg/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:8M)
# Deprecated in MySQL >= 5.6.3, removed in 5.7 (works in MariaDB)
# innodb_additional_mem_pool_size=8M

# memory buffer InnoDB uses to cache data and indexes of its tables (default:128M)
# Larger values means less I/O
innodb_buffer_pool_size=128M

# 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

secure_file_priv=

[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:  ERROR
--------

MySQL server configuration not found or not readable.
Details: The MySQL server configuration was not found or is not readable.

Test 9:  SUCCESS
--------

akonadictl found and usable
Details: The program '/tmp/.mount_kjBI6J/usr/bin/akonadictl' to control the Akonadi server was found and could be executed successfully.
Result:
akonadictl 5.4.43

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: '/tmp/.mount_kjBI6J/usr/share/akonadi/agents'. The XDG_DATA_DIRS environment variable is set to '/tmp/.mount_kjBI6J/usr/share:/home/me/.local/share:/tmp/.mount_kjBI6J/share:/usr/local/share/:/usr/share:/usr/share//usr/share/xsessions/plasma:/usr/local/share/:/usr/share/:/var/lib/snapd/desktop'; make sure this includes all paths where Akonadi agents are installed.

Directory listing of '/tmp/.mount_kjBI6J/usr/share/akonadi/agents':
akonadiindexingagent.desktop
akonotesresource.desktop
archivemailagent.desktop
birthdaysresource.desktop
contactsresource.desktop
davgroupwareresource.desktop
followupreminder.desktop
googlecalendarresource.desktop
googlecontactsresource.desktop
icaldirresource.desktop
icalresource.desktop
imapresource.desktop
invitationsagent.desktop
kalarmdirresource.desktop
kalarmresource.desktop
knutresource.desktop
kolabresource.desktop
maildirresource.desktop
maildispatcheragent.desktop
mailfilteragent.desktop
mboxresource.desktop
migrationagent.desktop
mixedmaildirresource.desktop
newmailnotifieragent.desktop
notesresource.desktop
openxchangeresource.desktop
pop3resource.desktop
sendlateragent.desktop
tomboynotesresource.desktop
vcarddirresource.desktop
vcardresource.desktop

Environment variable XDG_DATA_DIRS is set to '/tmp/.mount_kjBI6J/usr/share:/home/me/.local/share:/tmp/.mount_kjBI6J/share:/usr/local/share/:/usr/share:/usr/share//usr/share/xsessions/plasma:/usr/local/share/:/usr/share/:/var/lib/snapd/desktop'

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:  SUCCESS
--------

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

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 reported errors during its previous startup. The log can be found in <a href="/home/me/.local/share/akonadi/akonadi_control.error.old">/home/me/.local/share/akonadi/akonadi_control.error.old</a>.

File content of '/home/me/.local/share/akonadi/akonadi_control.error.old':
D-Bus session bus is not available!
ScarlettGatelyMoore commented 7 years ago

Yes, I just hit that, seems akonadi clashes with itself if host has it running. I just found https://techbase.kde.org/KDE_PIM/Akonadi/Multi-Instance though, rebuilding now.

ScarlettGatelyMoore commented 7 years ago

@star-buck @probonopd

Please test https://s3-eu-central-1.amazonaws.com/ds9-apps/kmail-master-appimage/kmail-git20170223-16:38:16-x86_64.AppImage

probonopd commented 7 years ago

Akonadi is launched on Ubuntu 16.04 and killed :+1: Works when executed from a shell and when executed from the menu. :100: So looks really good on Ubuntu 16.04. :1st_place_medal:

(Edit: I was too impatient - looks like it is properly killed)

probonopd commented 7 years ago

Also runs properly on maui-1-64bit.iso. :+1: Akonadi is started and killed.

star-buck commented 7 years ago

So it runs fine on Maui but on Ubuntu isnt killed?

probonopd commented 7 years ago

After some more testing I can confirm that it runs fine on both Maui and Ubuntu, Akonadi is properly started and killed in both cases.

ScarlettGatelyMoore commented 7 years ago

Fixed