Registered Member
|
I've installed KDE from MacPorts, meaning 4.12.5. While most things work fine, 2 things stand in the way of serious use:
- kmail is unable to send email. I don't have the exact error message, but it involves a failed SSL handshake. - The kded4 daemon very quickly runs into the open file limit, which among other things renders the cookie jar dysfunctional, which in turn makes it impossible to access google contacts. Any feedback on those 2 issues; possible causes to hunt down, or "things work fine using KDE from homebrew/Fink/whatever" ? I was hoping to replace Apple's own Mail.app with kmail, given how annoying the former has become in 10.9 ... Thanks, René |
Administrator
|
I can't comment on how to fix the kded4 file limit issue - how high is the limit though?
As for KMail and SSL issues - is the OpenSSL which Qt is compiled against able to connect to most websites? You can use other KDE applications (such as Rekonq) to test this...
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
Registered Member
|
Curiously, sending succeeds when I change the port number from GMail's normal 587 port to the more standard 465 .
As to the maximum number of open files: `limit` gives 256 for the max. number of descriptors. Which surprises me a bit, I'm almost sure I saw a higher number. Sadly, MacPorts has pushed upgrades since I diagnosed the issue (a month ago, time flies ... ) and as a result I've lost my custom-built ktimetracker binary. I'll see if I can find a slot to rebuild the whole packages it's part of. However, I seem to recall that other services were affected by the open file issue too, like the cookiejar, but the now seem to function correctly. I did find an output log from kded4, which had multiple
lines in it. It's not impossible that this issue was remedied by the patch that also corrected a kdepim issue with QFileSystemWatcher in 4.12.5 : 2 additional lines in .kde/share/config/kdeglobalrc:
|
Administrator
|
Okay, i'm afraid this will need someone with more specific OS X knowledge.
As for why those files are being watched - that is necessary to operate the Sycoca. I'm not sure if it will have a material impact, but if you can please try raising the file limit to 2048 or higher.
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
Registered Member
|
OK, I'll try to have another look at the kded4 issue, esp. since I ran into another cookiejar refusal.
|
Registered Member
|
Here's what I posted about this elsewhere:
but that was with KDE 4.12.4 and Qt 4.8.5. MacPorts now has Qt 4.8.6 and KDE 4.12.5, and kded4 is now at a cumulated runtime of over 73 minutes, without complaining about anything. According to lsof it has suspiciously few files open. However - and this is great news though it does drive me crazy - the cookiejar now seems to work, at least I had no error messages when logging in to a number of sites through Konqueror ... |
Administrator
|
That is excellent news. For KMail, is it now functional as well?
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
Registered Member
|
You mean the email sending issue? It remains when I try to use the default port recommended by gmail (587), but the standard port for secure smtp (465 I think) appears to work fine. Curious ...
|
Administrator
|
Indeed, that is extremely odd. If SSL was broken you'd expect all connection attempts to fail.
Do you have the exact error message it gives?
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
Registered Member
|
Nothing appears on stderr when I launch kmail from a terminal (and let akonadi be started on demand so that in theory those processes are connected to the same terminal), nor in any of the usual logs. I only get the on-screen notification stating that SSL negotiation failed. I didn't manage to grab a screenshot but I can try again if you think there's anything else to extract from that message. |
Administrator
|
Could you try launching Akonadi manually after enabling all debug areas using kdebugdialog? (Hopefully this is available).
Akonadi can be launched manually by running "akonadictl start"
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
Registered Member
|
Lots of output after hitting send (with the port configured to 587), but if it really teaches you much more about the reason of the failure ...
|
Administrator
|
Unfortunate, I guess it is something hidden within the smtps KIO slave - and it is likely missing the necessary debug output.
Thanks for noting the solution - to use the alternative port.
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
Registered Member
|
If you want to investigate this, I'd be happy to build the corresponding MacPorts port from source (I think it is anyway, for licensing reasons) with some patches to add debug output.
But I'm guessing that any KDE developer with Mac hardware can reproduce the issue directly |
Administrator
|
I'd suggest reporting the issue on bugs.kde.org, so it can be attended to when a developer gets a spare moment.
This sort of debugging is beyond my ability i'm afraid.
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
Registered users: bartoloni, Bing [Bot], Google [Bot], Sogou [Bot], Yahoo [Bot]