Bug 195400 - GoogleTalk IDs confuse kopete, cause new conversation window to open
Summary: GoogleTalk IDs confuse kopete, cause new conversation window to open
Status: RESOLVED FIXED
Alias: None
Product: kopete
Classification: Unmaintained
Component: Jabber Plugin (other bugs)
Version First Reported In: 0.70.2
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Kopete Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-06-06 02:28 UTC by Ioannis
Modified: 2013-06-04 16:59 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Ioannis 2009-06-06 02:28:10 UTC 
Version:           0.70.2 (using KDE 4.2.2)
OS:                Linux
Installed from:    Ubuntu Packages

When initiating a google talk conversation and the other end responds, kopete opens up a new window instead of using the already opened conversation window. It does so the same every time the other end re-logins.

It seems that Google Talk assigns different ID to each established conversation and this causes kopete to treat them separately. I've tried playing with the various 'grouping' options, but I couldn't find one that would prevent this from happening

This does not affect yahoo! or msn accounts.
Comment 1 Jan Ritzerfeld 2009-06-06 08:33:46 UTC 
This looks like a duplicate of Bug 194808, Bug 175078, Bug 111537 or Bug 142650: They address the changing of the resource name when the Google Talk server is used.
Comment 2 Ioannis 2009-06-06 14:02:47 UTC 
great. So this bug exists for ages and is not addressed because it is perceived as being the 'correct' behaviour ?

Despite the fact that some of those original bug reports claim that it is 'fixed', that is not the case...
Comment 3 M. P. Čtyři 2010-01-04 17:16:35 UTC 
I can confirm that the behavior exists in Kopete 0.80.2 under KDE 4.3.2. But Matt Rogers says in #194808 that the fix is in KDE 4.4.
Comment 4 Andrew Young 2011-11-10 15:39:06 UTC 
I can confirm that this issue is resolved in KDE 4.7.2.