I run my own XMPP server, and kde-telepathy can't connect to it (pidgin connects fine). I have a feeling that it is related to the server's TLS settings, but don't what to change. Server info : https://xmpp.net/result.php?domain=serafean.cz&type=client Telepathy log : Mar 19 16:12:08 Nemmerle plasmashell[32708]: tp-qt 0.9.6.1 WARN: Nested PendingReady for true failed with "org.freedesktop.Telepathy.Error.NetworkError" : "WOCKY_CONNECTOR_ERROR_TLS_SESSION_FAILED (#7): TLS handshake error: Handshake Error" Mar 19 16:12:08 Nemmerle plasmashell[32708]: tp-qt 0.9.6.1 WARN: Building connection "/org/freedesktop/Telepathy/Connection/gabble/jabber/[accountname snip]" failed with "org.freedesktop.Telepathy.Error.NetworkError" - "WOCKY_CONNECTOR_ERROR_TLS_SESSION_FAILED (#7): TLS handshake error: Handshake Error" Mar 19 16:12:08 Nemmerle plasmashell[32708]: tp-qt 0.9.6.1 WARN: StatefulDBusProxy::uniqueNameFrom(): Failed to get unique name of "org.freedesktop.Telepathy.Connection.gabble.jabber.[accountname snip]"
This boils down to unsupported OAUTH-2. Disabled that on ejabberd, and login works.
Duplicate of #354130 ?
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!