Bug 142915

Summary:	kopete: freezes when KABC fails to load immediately.
Product:	[openSUSE] SUSE LINUX 10.0	Reporter:	Daniel Rahn <drahn>
Component:	KDE	Assignee:	Will Stephenson <wstephenson>
Status:	RESOLVED FIXED	QA Contact:	E-mail List <qa-bugs>
Severity:	Normal
Priority:	P5 - None
Version:	Final
Target Milestone:	---
Hardware:	i386
OS:	SuSE Linux 10.0
Whiteboard:
Found By:	Customer	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Daniel Rahn 2006-01-12 19:18:24 UTC

Hi,

the summary might be misleading. Constellation is as follows:

- Via groupwarewizard kontact/KDE was configured to use the wrong Groupwise POA.
- In kopete accounts were defined for ICQ and GroupwiseIM.
- Both accounts were set to autoconnect.

Upon start of kopete, no connection was made.
In ~/.xsession-errors thise messages appeared:

--cut--
kio_groupwise: ERROR: SOAP Response Status: 59923 Redirect user to different post office.
kopete: ERROR: Unable to login: Redirect user to different post office.
kopete: ERROR: Unable to login: Redirect user to different post office.
--cut--

After correcting the Groupwise POA definition in kontact all plugins connect as expected ...

Comment 1 Daniel Rahn 2006-01-12 19:19:36 UTC

Btw, program version used is kdenetwork3-InstantMessenger-3.4.2-11.

Comment 2 Will Stephenson 2006-01-13 14:18:57 UTC

The error messages are due to Kopete loading the KDE addressbook, which checks for updates from the wrong PO, and fails.  The addressbook load takes too long, the error is not notified in time, and Kopete doesn't connect until the addressbook load times out.  It does eventually give up and connects to GWIM itself though. 

This bug is really a problem in the Kontact GW resource, that it doesn't handle errors quickly enough.  I am planning to fix this for SL10.1, changes will be backported.

Comment 3 Will Stephenson 2006-04-26 15:43:31 UTC

Fixed in GW resource for 10.1/CODE10, but not backported due to volume of changes.