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

Reply via email to