if the hostname of the computer changes then akonadi does not start. The problem seems that the socket address /home/[user]/.local/share/akonadi/socket-[hostname] is harcoded in .local/share/akonadi/db_data/postgresql.conf as unix_socket_directory = '/home/[user]/.local/share/akonadi/socket-[hostname]' Reproducible: Always Steps to Reproduce: 1. Create a new empty user /akonadi configuration with postgresql backend and default options. 2. Change the hostname of the computer. 3. Reboot Actual Results: postgresql refuses to start with error stdout: "esperando que el servidor se inicie....FATAL: no se pudo crear el archivo de bloqueo «/home/user/.local/share/akonadi/socket-oldhostname/.s.PGSQL.5432.lock»: No existe el fichero o el directorio Expected Results: hostname changes should not affect akonadi. It does not for .kde/ socket-cache-tmp symlinks
This bug has only been reported for versions older than KDEPIM 4.14 (at most akonadi-1.3). Can anyone tell if this bug still present? If noone confirms this bug for a recent version of akonadi (part of KDE Applications 15.08 or later), it gets closed in about three months.
I cannot further reproduce this bug with kmail 5.2.3