[Akonadi] [Bug 277839] akonadiserver.socket path to long
https://bugs.kde.org/show_bug.cgi?id=277839 Christian Mollekopf chrig...@fastmail.fm changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED Latest Commit||http://commits.kde.org/akon ||adi/6f6c691451726544487970e ||f325c71c4ae4a02fa --- Comment #11 from Christian Mollekopf chrig...@fastmail.fm --- Git commit 6f6c691451726544487970ef325c71c4ae4a02fa by Christian Mollekopf. Committed on 19/08/2013 at 09:31. Pushed by cmollekopf into branch '1.10'. Use the target of the symlink instead as socket directory. Socket paths must be shorter than 108 characters, and the symlink is quickly beyond that. By using the actual directory this can be avoided. This results in the socket used to start the mysql database, as well as the socket in akonadiconnectionrc being set to the /tmp/ path. REVIEW: 112152 M +2-2server/src/utils.cpp http://commits.kde.org/akonadi/6f6c691451726544487970ef325c71c4ae4a02fa -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 277839] akonadiserver.socket path to long
https://bugs.kde.org/show_bug.cgi?id=277839 Christophe Giboudeaux cgiboude...@gmx.com changed: What|Removed |Added CC||joerg.steff...@dass-it.de --- Comment #9 from Christophe Giboudeaux cgiboude...@gmx.com --- *** Bug 292323 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 277839] akonadiserver.socket path to long
https://bugs.kde.org/show_bug.cgi?id=277839 gust...@angulosolido.pt changed: What|Removed |Added CC||gust...@angulosolido.pt --- Comment #10 from gust...@angulosolido.pt --- I think this problem might be related: https://bugs.kde.org/show_bug.cgi?id=320102 and we may have a general problem that affects KDE when the paths to home directories are long. In the case I'm referring to we had /home/DOMAIN/somelonusername plus the fact that we are defining KDETMP=~/tmp/$USER-kde KDEVARTMP=~/tmp/$USER-kde So a socket path could be /home/DOMAIN/somelongusername/tmp/somelongusername-kde/ Since we were having problems we skipped the DOMAIN component for homes. So now we have socket paths such as /home/somelongusernameXX/tmp/somelongusernameXX-kde/ksocket-somelongusernameX/klauncherT31044.slave-socket= which are still like 109 chars long. That is, for some usernames we still have problems that I suspect are socket related. What could be a solution for this? -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
