Bug 299231 - akonadiserver crashes with umlaut in mysql socket
Summary: akonadiserver crashes with umlaut in mysql socket
Status: RESOLVED UNMAINTAINED
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: server (show other bugs)
Version: unspecified
Platform: Gentoo Packages Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-05-02 10:34 UTC by Jaakko Perttilä
Modified: 2017-01-07 22:00 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jaakko Perttilä 2012-05-02 10:34:05 UTC
akonadiserver forces the socket filename from the hostname. If the hostname contains probably any non-ASCII characters, the socket cannot be found.

The Options="UNIX_SOCKET=" in ~/.config/akonadi/akonadiserverrc gets overwritten by the server start command parameters, so I couldn't manually change the socket name.

After failing, the config gets changed to this:
Options="UNIX_SOCKET=/home/jaakko/.local/share/akonadi/socket-j\xe4\xe4karhu/mysql.socket"


Reproducible: Always

Steps to Reproduce:
1. # hostname jääkarhu
2. # /etc/init.d/dbus restart
3. startx
4. akonadictl start
Actual Results:  
...
mysql.user                                         OK
Unable to listen on Unix socket "/home/jaakko/.local/share/akonadi/socket-jääkarhu/akonadiserver.socket"
...
ProcessControl: Application 'akonadiserver' returned with exit code 255 (Unknown error)
"akonadiserver" crashed too often and will not be restarted! 


As a result, there are four mysqld processed running with following parameters:
/usr/sbin/mysqld --defaults-file=/home/jaakko/.local/share/akonadi/mysql.conf --datadir=/home/jaakko/.local/share/akonadi/db_data/ --socket=/home/jaakko/.local/share/akonadi/socket-jääkarhu/mysql.socket


Expected Results:  
akonadiserver starting ok.

Works fine after I change the hostname to something with only ASCII characters, and restart the dbus.
Comment 1 Denis Kurz 2016-09-24 20:42:37 UTC
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.
Comment 2 Denis Kurz 2017-01-07 22:00:25 UTC
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.