Bug 140394 - Kopete Jabber error: "There was a connection error: Operation is not supported."
Summary: Kopete Jabber error: "There was a connection error: Operation is not supported."
Status: RESOLVED WORKSFORME
Alias: None
Product: kopete
Classification: Applications
Component: Jabber Plugin (show other bugs)
Version: unspecified
Platform: Debian testing Linux
: NOR normal
Target Milestone: ---
Assignee: Kopete Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-01-21 13:30 UTC by Adam Porter
Modified: 2018-11-06 12:21 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Adam Porter 2007-01-21 13:30:35 UTC
Version:            (using KDE KDE 3.5.5)
Installed from:    Debian testing/unstable Packages

Kopete has been working fine with Jabber, but lately, after being connected to a server for about 20 minutes, I get an error dialog that says, "There was a connection error: Operation is not supported."  After I dismiss the error, the account does not reconnect automatically, and I have to manually reconnect the account.  Most of the time using the master Online status doesn't work either, but this time when I tried it, one of my three Jabber accounts did connect, while the other two didn't even try.

I haven't been able to find any errors in ~/.xsession-errors.  This problem is occurring on a Dreamhost Jabber server, the official jabber.org server, and the Google Gtalk Jabber server.
Comment 1 Philip Rodrigues 2007-01-22 22:22:53 UTC
If you start kopete from a konsole, do you get any useful debug output?
Comment 2 Torsten Martin 2008-03-05 20:45:42 UTC
I have a problem like this, too.

kopete tries to connect my jabber account for about 5 minutes, until I get this error message ("There was a connection error: Operation is not supported.")

When started in a konsole, it prints out
"MNG error 1029: Chunk out of sequence; chunk TERM; subcode 0:0"
every second.

Pidgin has no problems connecting this account.

My Kopete (V0.12.7) runs on Kubuntu gutsy gibbon. The jabber account belongs to the web.de jabber server.
Comment 3 Charles Connell 2008-03-08 18:52:21 UTC
Could some having the problem post the entire debug output (you can abridge many identical lines if you want) please? The MNG thing is probably unrelated. We need to see the real output, not just one line that you think is relevant.
Comment 4 Torsten Martin 2008-03-08 21:57:12 UTC
Unfortunally, this seems to be really everything:

 skrilax@xorxcel:~$ kopete
 skrilax@xorxcel:~$ MNG error 1029: Chunk out of sequence; chunk TERM; subcode 0:0
 MNG error 1029: Chunk out of sequence; chunk TERM; subcode 0:0

when I try to connect my jabber account it just goes on that way:

 MNG error 1029: Chunk out of sequence; chunk TERM; subcode 0:0
 MNG error 1029: Chunk out of sequence; chunk TERM; subcode 0:0
 MNG error 1029: Chunk out of sequence; chunk TERM; subcode 0:0
 MNG error 1029: Chunk out of sequence; chunk TERM; subcode 0:0
 MNG error 1029: Chunk out of sequence; chunk TERM; subcode 0:0 
  ...

after closing the error window I get:

 X Error: BadWindow (invalid Window parameter) 3
  Major opcode:  20
  Minor opcode:  0
  Resource id:  0x28016a4

but this should be even more unrelated ;-)

I don't know what else information could be important?
it's a 64 Bit kubuntu.
And I didn't even get far enough to type in my password (I didn't save it in the configuration dialog)
Comment 5 Charles Connell 2008-03-08 21:59:23 UTC
It looks like you don't have the debug version of kdenetwork. If you install it then you will be able to get useful debug output.
Comment 6 Torsten Martin 2008-03-08 23:14:37 UTC
I installed kdenetwork-dbg, this gave me no additional output.

But I registered a new account at jabber.org -- and it works! (I should have tried that earlier - sorry)

But as pidgin has no problems connecting to that web.de account, there must be something wrong. Could it be an error on web.de, that pidgin can correct or doesn't trap in?
Comment 7 George Kiagiadakis 2008-07-21 15:52:44 UTC
I have seen this bug many times with an account at jabber.org. I don't remember when it was the last time it happened, but I think it was when I was using a KDE 4.1 beta version. It is a completely random event, but it happens.
Comment 8 Boris 2008-08-16 07:36:41 UTC
Could reproduce with 0.50.80 Kde 4.1
Comment 9 Martin Bagge / brother 2008-10-08 14:27:52 UTC
Using Debian Unstable I've come across something similar.

connecting to jabber(.org) I get the following error:
There was an eror in the protocol stream: Policy violation in the protocol stream

this is the output in terminal:
brother@zond:~$ kopete
VIDIOC_ENUM_FMT: Ogiltigt argument
VIDIOC_STREAMOFF error 22, Ogiltigt argument
QDom: saving invalid character �, the document will not be well-formed
QDom: saving invalid character �, the document will not be well-formed
QDom: saving invalid character �, the document will not be well-formed
QDom: saving invalid character �, the document will not be well-formed
QDom: saving invalid character �, the document will not be well-formed
QDom: saving invalid character �, the document will not be well-formed
QDom: saving invalid character �, the document will not be well-formed
QDom: saving invalid character �, the document will not be well-formed
QFont::setPointSize: Point size <= 0 (-1)
QDom: saving invalid character &#xdbff;, the document will not be well-formed
QDom: saving invalid character &#xded6;, the document will not be well-formed
QDom: saving invalid character &#xdbff;, the document will not be well-formed
QDom: saving invalid character &#xded6;, the document will not be well-formed
QDom: saving invalid character &#xdbff;, the document will not be well-formed
QDom: saving invalid character &#xdee4;, the document will not be well-formed
QDom: saving invalid character &#xdbff;, the document will not be well-formed
QDom: saving invalid character &#xded6;, the document will not be well-formed

according to my aptitude log I haven't touched the kopete package since early april.
Comment 10 Andrew Crouthamel 2018-11-02 04:26:19 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 11 Martin Bagge / brother 2018-11-06 08:13:40 UTC
Haven't used kopete and jabber for a long time but upon testing this morning (CET) it looks like it works as intended and this bug can probably be closed.

Using Kopete 1.13.0 on Debian unstable.
Comment 12 Martin Bagge / brother 2018-11-06 08:15:15 UTC
And setting the status accordingly.
Comment 13 Christoph Feck 2018-11-06 12:21:01 UTC
Thanks for the update; changing status.