Bug 133478

Summary: jabber user-directory-search does not display any search-fields on a wildfire server
Product: [Unmaintained] kopete Reporter: S. Burmeister <sven.burmeister>
Component: Jabber PluginAssignee: Kopete Developers <kopete-bugs-null>
Status: RESOLVED UNMAINTAINED    
Severity: normal    
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: unspecified   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description S. Burmeister 2006-09-03 09:34:35 UTC
Version:           0.12.2 (using KDE KDE 3.5.4)
OS:                Linux

If I use the user-search on kdetalk.net search-fields are shown. However, if I do the same on my university's wildfire jabber server there are no search-fields shown.

If the university had somehow disabled this service I would expect a notification instead of an empty window.

Yet in this case it is not disabled, since I can search the user-directory in Psi or Miranda.
Comment 1 Olivier Goffart 2006-09-17 12:34:03 UTC
Can you provide the XML which is send or received when you try to search ?
(it is shown on the debug output if you have compiled with debug)
Comment 2 S. Burmeister 2006-09-18 09:20:43 UTC
XML OUT: <iq type="get" to="search.ccccccc.aa" id="abf2a" >
<query xmlns="jabber:iq:search"/>
</iq>

XML IN: <iq from="search.ccccccccccccc.aa" type="result" to="ccccccc@aaaaaaaaa.cc/Kopete" id="abf2a" >
<query xmlns="jabber:iq:search">
<instructions>The following fields are available for search. Wildcard (*) characters are allowed as part the of query.</instructions>
<Username/>
<Name/>
<Email/>
<x xmlns="jabber:x:data" type="form" >
<title>User Search</title>
<instructions>The following fields are available for search. Wildcard (*) characters are allowed as part the of query.</instructions>
<field type="hidden" var="FORM_TYPE" >
<value>jabber:iq:search</value>
</field>
<field type="text-single" label="Search" var="search" >
<required/>
</field>
<field type="boolean" label="Username" var="Username" >
<value>1</value>
</field>
<field type="boolean" label="Name" var="Name" >
<value>1</value>
</field>
<field type="boolean" label="Email" var="Email" >
<value>1</value>
</field>
</x>
</query>
</iq>

BTW, if I get the following, kopete does not notify that the service is unavailable, hence the user will blame kopete, although it is the server's "fault".

XML IN: <iq from="search.jabber.rwth-aachen.de" type="result" to="cccccccc@ccccccccccc.aa/Kopete" id="abe6a" >
<query xmlns="jabber:iq:search">
<x xmlns="jabber:x:data" type="cancel" >
<title>User Search</title>
<instructions>This service is unavailable.</instructions>
</x>
</query>
</iq>
Comment 3 Eitzenberger Thomas 2007-02-08 09:32:52 UTC
Hi,

I can confirm the behaviour, I have a local intranet wildfire server running at my office (some 20 users connected with multiple client son multiple OS :O)
I can discover the search service of wildfire (v3.2 and 3.1.1), but when opening I have no input fields available (running kopete 0.12.4 on Suse 10.2).

Thanx for Kopete "I'm lovin in" :O)
Comment 4 Roman Jarosz 2010-01-17 15:29:15 UTC
Please update to newer version as we don't have manpower to support Kopete in
KDE 3. If you still see this bug in new version please reopen this bug report.