Bug 127809

Summary: Broken error message when retrieving the list of Jabber services fails
Product: [Unmaintained] kopete Reporter: Stefan Borggraefe <Stefan.Borggraefe>
Component: Jabber PluginAssignee: Kopete Developers <kopete-bugs-null>
Status: RESOLVED WORKSFORME    
Severity: minor CC: andrew.crouthamel, rasasi78
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Debian testing   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Stefan Borggraefe 2006-05-22 10:13:51 UTC
Version:           Current 0.12 SVN build (using KDE KDE 3.5.2)
Installed from:    Debian testing/unstable Packages
Compiler:          gcc (GCC) 4.0.4 20060507 (prerelease) (Debian 4.0.3-3) 
OS:                Linux

Steps to reproduce:

1. Create a Jabber account and connect
2. From the right-click menu of the Jabber status icon select "Services..."
3. In the "Server:" field enter a non-existing host, an existing host that doesn't have a Jabber server or some random string

Result:
In all cases you get the same error message:

  Unable to retrieve the list of services.
  Reason:
                     [OK]

Expected Result:
Show the reason for the error (better) or don't display the string "Reason:" (quick fix).
Comment 1 Raúl 2006-05-31 22:41:21 UTC
Confirmed here. Service discovery works in psi, and once done in psi, you can use the new service within kopete. I have tried jabber-hispano.org server.

This bug seems related to #127811, but I'm not sure it could be considered the same.
Comment 2 Stefan Borggraefe 2006-05-31 23:08:36 UTC
Raúl: This bug is just about the incomplete error string. Bug 127811 is about being unable to subscribe to services. So they are not the same.
Comment 3 Dominik Tritscher 2008-07-23 21:56:14 UTC
The problem has gotten even worse:
kopete 0.50.80 doesn't display any error message.
If I try it with a non existent url or a blank server field, it returns an empty node in the treeview.
If I try it with a valid url from a server without jabber, it returns a treeview with the server as root node but without any child node.
Expected behaviour: Should display a error message explaining the problem ("Server not found" / "No Jabber services found on server").
Comment 4 Andrew Crouthamel 2018-11-02 04:26:46 UTC
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 5 Raúl 2018-11-03 17:54:52 UTC
Hello:
Have just tested on kopete 1.13.0 on KDE 4.14.38.
When I proceed as per Stefan described, what I have is a single result which only includes the name of the introduced server and no other results, as oposed to a valid jabber server. I don't have any error message or dialog. Therefore I would say this report is no longer valid.
Sidenote: I'm not sure if there's a more recent kopete version or if kopete has been ported to KF5 at all.
HTH,
Comment 6 Andrew Crouthamel 2018-11-05 02:42:09 UTC
Thanks for the update!