Bug 230165

Summary: Communication errors not displayed
Product: [Unmaintained] kopete Reporter: Ancoron <ancoron.luciferis>
Component: generalAssignee: Kopete Developers <kopete-bugs-null>
Status: RESOLVED WORKSFORME    
Severity: normal    
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: Captured Kopete session

Description Ancoron 2010-03-10 08:51:13 UTC 
Version:            (using KDE 4.4.1)
OS:                Linux
Installed from:    Ubuntu Packages

I just added my gmail.com jabber account to kopete and it doesn't go online as expected. After several failing attempts to resolve this issue by double and triple checking the settings and my credentials I started to run kopete from the terminal and capturing the output.

Strange enough that all output goes to stderr instead of just the warnings and errors it I found the reason and wondered myself how this can be called "stable":

The jabber server returns the error message in XML
...
<error type="auth" code="403">
<forbidden xmlns="urn:ietf:params:xml:ns:xmpp-stanzas"/>
<text xmlns="urn:ietf:params:xml:ns:xmpp-stanzas">Username or password not correct.</text>
</error>
...

and Kopete says: ...slotClientDebugMessage: "Client stream error."

???

The server response is totally valid according to RFC-3920:

http://tools.ietf.org/html/rfc3920#section-9.3.4

So Kopete just doesn't pay any attention to that. And it doesn't give any information to the user. And in turn the user will not be able to resolve the issue as long as he doesn't know what issue to resolve.

Acceptable error-reporting is not one of KDE4's advantages.

I will attach the captured output of kopete of the short session.

I used this command to capture it:
kopete 2>&1 | sed -u -e 's/"/\\"/g' -e 's/^\(.*\)$/echo "[`date +"%F %T.%N"`] \1"/' | sh | tee kopete.log


Some additional system information:

OS: Kubuntu Lucid Alpha 3 (latest updates applied)
Kernel: 2.6.33 mainline AMD64
KDE: 4.4.1
Kopete: 1.0.0
Ubuntu package version: 4:4.4.1-0ubuntu1
Comment 1 Ancoron 2010-03-10 08:52:17 UTC 
Created attachment 41497 [details]
Captured Kopete session
Comment 2 Andrew Crouthamel 2018-11-02 22:55:13 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 3 Andrew Crouthamel 2018-11-16 02:39:14 UTC 
Dear Bug Submitter,

This is a reminder that 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?

Thank you for helping us make KDE software even better for everyone!
Comment 4 Justin Zobel 2022-12-06 00:56:58 UTC 
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 5 Bug Janitor Service 2022-12-21 05:18:32 UTC 
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 6 Bug Janitor Service 2023-01-05 05:27:39 UTC 
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!