Bug 30226

Summary:	TLS problems connecting to GTalk with 0.9.18
Product:	Telepathy	Reporter:	Simon McVittie <smcv>
Component:	gabble	Assignee:	Telepathy bugs list <telepathy-bugs>
Status:	RESOLVED FIXED	QA Contact:	Telepathy bugs list <telepathy-bugs>
Severity:	normal
Priority:	medium	CC:	mehmet.giritli
Version:	0.10
Hardware:	Other
OS:	All
Whiteboard:
i915 platform:		i915 features:
Bug Depends on:	29364
Bug Blocks:

Description Simon McVittie 2010-09-16 05:05:46 UTC

On Bug #29364, Mehmet Giritli wrote:

> I updated gabble to 0.9.18 and now I can not connect to gtalk. From the debug,
> it seems this is again a problem with tls. 
> 
> The previous versions were ok with gnutls 2.8 series but now, I am having
> problems with that too.
> 
> This time I do not get an error but tries to connect without success and any
> apparent error messages...

and attached <https://bugs.freedesktop.org/attachment.cgi?id=38738>.

Comment 1 mehmet.giritli 2010-09-16 05:12:34 UTC

So, unlike in the previous versions, downgrading gnutls to 2.8 is not a work around anymore? In other words, until gnutls bumps itself with the backported patches, there is no way of connecting to gtalk with the new gabble releases (>= 0.9.18)?

Is this a correct observation Simon?

Comment 2 mehmet.giritli 2010-09-16 05:16:25 UTC

Ok, I just read your message in the blocker bug, so this is a new bug. Sorry for the annoyance..

Comment 3 Simon McVittie 2010-09-16 05:22:20 UTC

Does this go away if you upgrade telepathy-mission-control to version 5.5.0 or later, or Empathy to 2.31.92 or later?

(I recommend Mission Control 5.6 when we release it, or the highest possible 5.5.x version until then; similarly, Empathy 2.32 when available, or the highest possible 2.31.x until then.)

Comment 4 Simon McVittie 2010-09-16 05:30:05 UTC

Thinking about it further, the version of Empathy isn't as important, but you must have Mission Control 5.5 to avoid the connection "getting stuck" shortly before CONNECTED state.

Comment 5 mehmet.giritli 2010-09-16 05:32:28 UTC

(In reply to comment #3)
> Does this go away if you upgrade telepathy-mission-control to version 5.5.0 or
> later, or Empathy to 2.31.92 or later?
> 
> (I recommend Mission Control 5.6 when we release it, or the highest possible
> 5.5.x version until then; similarly, Empathy 2.32 when available, or the
> highest possible 2.31.x until then.)

Just tried with 5.5.0 and it made no difference. Exact same debug as well.

With emapthy, I do not have the dev-version packages but if you think it is important, I can give it a shot?

Comment 6 mehmet.giritli 2010-09-16 05:35:52 UTC

(In reply to comment #5)
> (In reply to comment #3)
> > Does this go away if you upgrade telepathy-mission-control to version 5.5.0 or
> > later, or Empathy to 2.31.92 or later?
> > 
> > (I recommend Mission Control 5.6 when we release it, or the highest possible
> > 5.5.x version until then; similarly, Empathy 2.32 when available, or the
> > highest possible 2.31.x until then.)
> 
> Just tried with 5.5.0 and it made no difference. Exact same debug as well.
> 
> With emapthy, I do not have the dev-version packages but if you think it is
> important, I can give it a shot?


Correction: 5.5.0 just worked. The background process was not killed with empathy quitting so the prev comment was in fact with 5.4 perhaps.

I just got connected to gtalk.

Comment 7 Simon McVittie 2010-09-16 05:52:59 UTC

Excellent. I can consider this to be a packaging bug, then: recent Gabble should have a Breaks/Conflicts relationship with older MC versions (it's not a dependency, as such, because Gabble doesn't strictly *need* MC, but some packaging systems might have to represent it as a dependency).

I'll make that clearer in the NEWS file for 0.10.0.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.