Bug 314009 - Akonadi is unable to listen on Unix socket
Summary: Akonadi is unable to listen on Unix socket
Status: RESOLVED UNMAINTAINED
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: 1.8.1
Platform: Gentoo Packages Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-01-28 01:54 UTC by Artem Vorotnikov
Modified: 2017-01-07 22:03 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Artem Vorotnikov 2013-01-28 01:54:50 UTC 
I have Unicode (cyrillic) user, host names and Unicode home path. Akonadi fails to start with error:

Unable to listen on Unix socket "/home/артём/.local/share/akonadi/socket-стол1/akonadiserver.socket" 
"[
0: akonadiserver(_Z11akBacktracev+0x35) [0x453315]
1: akonadiserver() [0x4535dc]
2: /lib64/libc.so.6() [0x3ebda38090]
3: /lib64/libc.so.6(gsignal+0x35) [0x3ebda38015]
4: /lib64/libc.so.6(abort+0x17b) [0x3ebda3948b]
5: /usr/lib64/qt4/libQtCore.so.4(_Z17qt_message_output9QtMsgTypePKc+0x74) [0x3ec3a779e4]
6: akonadiserver(_ZN15FileDebugStream9writeDataEPKcx+0x92) [0x455602]
7: /usr/lib64/qt4/libQtCore.so.4(_ZN9QIODevice5writeEPKcx+0xaf) [0x3ec3b12f1f]
8: /usr/lib64/qt4/libQtCore.so.4() [0x3ec3b1e64b]
9: /usr/lib64/qt4/libQtCore.so.4(_ZN11QTextStreamD1Ev+0x39) [0x3ec3b27029]
10: akonadiserver(_ZN7Akonadi13AkonadiServerC1EP7QObject+0x323) [0x457653]
11: akonadiserver(_ZN7Akonadi13AkonadiServer8instanceEv+0x37) [0x458ae7]
12: akonadiserver(main+0x1ea) [0x44bb1a]
13: /lib64/libc.so.6(__libc_start_main+0xed) [0x3ebda2491d]
14: akonadiserver() [0x44c2a1]
]
" 

Reproducible: Always
Comment 1 Denis Kurz 2016-09-24 20:39:06 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:03:49 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.