Bug 308476

Summary:	okcupid-pidgin does not work with KDE telepathy (certificate issues?)
Product:	[Unmaintained] telepathy	Reporter:	kdestuff
Component:	general	Assignee:	Telepathy Bugs <kde-telepathy-bugs>
Status:	RESOLVED WORKSFORME
Severity:	normal	CC:	kde
Priority:	NOR	Keywords:	triaged
Version:	0.5.1
Target Milestone:	Future
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description kdestuff 2012-10-16 09:05:44 UTC

I am trying to get https://code.google.com/p/okcupid-pidgin/ working with KDE telepathy. It works fine with pidgin on the same system. I am also able to create an account which is shown as online, but no contacts are shown.
I have made use of the KDE Telepathy Debug Tool to find the source of the problem. Unfortunately it does not allow to copy several lines at once. So I only copy the lines (from the haze-tab) which indicate some problem:
"[purple/certificate/x509/tls_cached] Name mismatch: Certificate given for 208.83.243.215 has a name of www.okcupid.com
16.10.2012 10:34:46.70724 - [purple/okcupid] executing message check failsafe"
These appear repeatingly apart from other lines (which do not indicate any problem).
In missing control there do not appear any errors:
16.10.2012 10:48:37.316159 - [mcd] set_requested_presence: called for haze/bigbrownchunx_okcupid/username
16.10.2012 10:48:37.316205 - [mcd] set_requested_presence: setting requested presence: 2, available, 
16.10.2012 10:48:37.316247 - [mcd] mcd_account_request_presence_int: Requested presence: 2 available 
16.10.2012 10:48:37.316289 - [mcd] _mcd_connection_request_presence: Presence requested: 2
16.10.2012 10:48:37.316334 - [mcd] _mcd_connection_set_presence: Setting status 'available' of type 2 ('available' was requested)
16.10.2012 10:48:37.316382 - [mcd] mcd_account_changed_property: called: ChangingPresence
16.10.2012 10:48:37.316426 - [mcd] mcd_account_changed_property: First changed property
16.10.2012 10:48:37.327086 - [mcd] emit_property_changed: called


Reproducible: Always

Comment 1 David Edmundson 2013-01-15 22:12:16 UTC

Thanks for the report.

Would it be possible for you to see what Empathy does in this situation?
Empathy and us share the same backend code,  so it helps diagnose the situation.

I'll confirm this bug, because the logs look legit. There is a related bug that could be causing this.

Comment 2 kdestuff 2013-01-16 08:12:05 UTC

I am now running KDE Telepathy 0.5.2

I have tried, but everything turns out a little more confusing since the behaviour of telepathy has changed as well. In KDE telepathy the account is not shown anymore as connected but as connecting (which might be more correct as the previous state)
Empathy shows an error box in the contact list, telling me that a passwort is required. But when I press the "+"-button (which is supposed to allow me to enter the password) I just receive the message that "it can not be connected. There is no chance to enter a password. KDE Telepathy does not even ask for the password.
I also have to note that I definitely have entered the password correctly. I have copied it from the Firefox password manager via copy and paste (and checked in Klipper that it is correct). I also have to add that it is not possible to set up the account in Empathy, but it appears if set up in KDE Telepathy. In KDE telepathy I have tried with "force-https" and without.

The debug log has significantly changed now. It is very long and I need to do some anonymizing for privacy reasons first. I would help, if I new which part of the logs are the most interesting.

Comment 3 David Edmundson 2013-02-22 12:41:21 UTC

Hopefully fixed in 0.6

Will need you to test and report back.

Comment 4 Andrew Crouthamel 2018-09-24 02:13:55 UTC

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 set the bug status 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!

Comment 5 Andrew Crouthamel 2018-10-27 03:46:32 UTC

Dear Bug Submitter,

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!