Bug 227771 - If jabber resource is not unique, I can't login Gtalk account simultaneously from two different PCs
Summary: If jabber resource is not unique, I can't login Gtalk account simultaneously ...
Status: RESOLVED INTENTIONAL
Alias: None
Product: kopete
Classification: Unmaintained
Component: Jabber Plugin (other bugs)
Version First Reported In: unspecified
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: Kopete Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-02-20 05:59 UTC by Alexander Azikov
Modified: 2013-06-04 16:38 UTC (History)
1 user (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 Alexander Azikov 2010-02-20 05:59:52 UTC 
Version:            (using KDE 4.4.0)
OS:                Linux
Installed from:    openSUSE RPMs

I have two PCs on which I use Kopete. When creating new Gtalk account jabber resource is automatically set as 'Kopete'. It prevents me to login Gtalk account from two PCs simultaneously. Two PCs just keep fighting for the right to be online. Thus I see constant reconnects on both PCs. If I configure jabber resource to be different on each PC, then the problem disappears. Kopete must use some machine specific data as part of the resource name.
Comment 1 Pali Rohár 2013-06-04 16:38:28 UTC 
This is up to you (user) or jabber server. It can select available resource for you. Closing as wontfix, because jabber client do not have to do it and there is no plan for implementing resource randomization in Kopete.