[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#604805: kmail: unusable with $HOME on OpenAFS due to Akonadi not starting

Ansgar Burchardt <ansgar@mathi.uni-heidelberg.de> writes:

> The problem with starting Akonadi is that it tries to create a UNIX
> socket in $HOME/.local/share/akonadi/db_misc/mysql.socket.  This is not
> possible with OpenAFS.  See also the attached report.

I forgot to attach the report, but after searching a second time this
has already been reported[1].

  [1] <http://bugs.debian.org/545139>
> a) Akonadi should create the socket elsewhere.  Other parts of KDE seem
> to use /tmp/ksocket-$USER here (or $HOME/.kde/socket-$HOSTNAME which is
> a symlink to the directory in /tmp).
> b) KMail should not exit when it cannot start Akonadi.  It still seems
> to be usable.

I noticed that KMail does not close when I ignore the message box with
the error message.  Reading mail seems to work fine, but KMail stops
responding once I try to send a mail (after pushing the "Send" button)
and displays the following error message in a loop:

  kmail(6123)/libakonadi Akonadi::SessionPrivate::socketError: Socket error occurred: "QLocalSocket::connectToServer: Invalid name" 

So (b) looks non-trivial as well.


Reply to: