If we had a fancy downstream tag like KDE does, I would mark it as
downstream ;-)
KMail does not directly poke /tmp/ksocket-$USER in any way, in fact, the
only component that ever fiddles with the permissions of that directory
is a very lowlevel application that initial creates the dir. However if
this app was responsible KDE would have refused to login at all.
I guess some weird script or 3rd party application tried to do fancy
things with /tmp in a recursive manner, messing up the permissions.
** Changed in: kdepim (Ubuntu)
Status: New => Invalid
--
/tmp/ksocket-bugabundo/ has wrong permissions
https://bugs.launchpad.net/bugs/304705
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to kdepim in ubuntu.
--
kubuntu-bugs mailing list
[EMAIL PROTECTED]
https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
