Bug 221533

I can't connect to Openfire server too

.xsession-errors

X Error: BadWindow (invalid Window parameter) 3
  Major opcode: 20 (X_GetProperty)
  Resource id:  0x4babee6
Unknown signature value:  0
Unknown signature value:  0
X Error: BadWindow (invalid Window parameter) 3
  Major opcode: 20 (X_GetProperty)
  Resource id:  0x4badf8c
Unknown signature value:  0
X Error: BadWindow (invalid Window parameter) 3
  Major opcode: 20 (X_GetProperty)
  Resource id:  0x4bae237
Unknown signature value:  0
X Error: BadWindow (invalid Window parameter) 3
  Major opcode: 20 (X_GetProperty)
  Resource id:  0x4bae910
Unknown signature value:  0
X Error: BadWindow (invalid Window parameter) 3
  Major opcode: 20 (X_GetProperty)
  Resource id:  0x4baeb88

Using Kubuntu 9.10 

Kopete Versione 0.80.2
Con KDE 4.3.2 (KDE 4.3.2)

Cannot connect to gchat from Kopete
Using kopete version 0.80.2(Using KDE 4.3.4) 
Below is the error message i got.

Creating the PushJingleSession task....
Object::connect: No such signal XMPP::JingleSessionManager::incomingSession()

I am seeing this bug also.

Just upgraded to Fedora 12 and my SSL Kopete connection to a Openfire Jabber server fails silently after attempting to connect for a couple of minutes.  

Here is the complete command line session... although I'm not sure anything is relevant.  The appendChild errors notes seemed to come up before connection attempt, so I would rule those out.  Not so sure about the Jingle errors - but I have my doubts they are connected also.

% kopete --nofork  
Calling appendChild() on a null node does nothing.
Calling appendChild() on a null node does nothing.
Calling appendChild() on a null node does nothing.
Calling appendChild() on a null node does nothing.
JingleSessionManager::JingleSessionManager created. 
Creating the PushJingleSession task.... 
Object::connect: No such signal XMPP::JingleSessionManager::incomingSession()
Creating the PushJingleSession task.... 
Object::connect: No such signal XMPP::JingleSessionManager::incomingSession()


Other relevant info:

1. I run the server also - and have ports 5222 and 5223 open (5223 old style SSL)
2. This worked consistently in Fedora 11 and past for years.
3. I can see packets arriving at the server on initial connection attempt however nothing after server ack
4. Non SSL connections work in kopete
5. Empathy works in all modes (non SSL, SSL to 5223 and old style SSL to 5222)

Anywhere else I can find logs?

I dont know if this is related but I have also discovered that PSI has the same issue.

Im using

Fedora12 with all updates as of (5/3/10)
Psi 0.14
Qt 4.6.2

I try to connect to the same jabber server as I discussed before and get similair symptoms. After a while PSI errors with "TLS Handshake error"

The thing to note is that Kopete and PSI are both based on Qt

I have found that PSI jabber client cannot establish a connection either.

The one things these 2 clients have in common is that they are both QT based clients and hence use QCA to establish encryption. 

This may be a problem with QCA rather than the kopete software itself

Not sure about the SSL problems, but I can't get non-SSL to connect either to an openfire server. F11 connects fine. After the upgrade to F12, it fails. Pidgin connects fine SSL or non-SSL on 5222 or 5223.

*** Bug 238160 has been marked as a duplicate of this bug. ***

I can confirm the same problems. kopete and psi cannot connect to Google Talk. 
pidgin can. The difference seems to be QCA. The root problem seems to be:

Object::connect: No such signal XMPP::JingleSessionManager::incomingSession()

Someone shall change the subject line of the bug to include the "No such signal" error message. I don't have permissions to do it.

Same problem over here, trying to connect to google talk:

--
Unknown signature value:  795 
--

Kopete version  1.0.80
                os build: 4:4.4.85-0ubuntu2

libqca2 version: 2.0.2
                os build: 2.0.2-1ubuntu2

My kopete could connect to Google Talk before I did below.

I was following the url below for using MSN via Google Talk with transport servers using psi.

http://lifehacker.com/289097/chat-with-aim-msn-yahoo-and-other-contacts-over-
google-talk

After I did above, and not going well, I switched back to Kopete, and it couldn't connect to Google Talk anymore. I launched kopete from terminal and i get:

Unknown signature value:  795 

It occurs everytime I try to set status online.

My kopete version is: 4:4.4.5-0ubuntu1~lucid1~ppa1

Maybe we should drop kopete from kde, and include pidgin by default, that's the only way to get something working.

*** This bug has been confirmed by popular vote. ***

same on FC13, tried kopete from svn, revision 1156603:
When I'm trying to connect to corporate jabber account, I see these log messages in the terminal:

JingleSessionManager::JingleSessionManager created. 
Creating the PushJingleSession task.... 
Object::connect: No such signal XMPP::JingleSessionManager::incomingSession()
Unknown signature value:  795 
Unknown signature value:  795 
Unknown signature value:  668 
Unknown signature value:  795 
Unknown signature value:  668 
Unknown signature value:  795 
Unknown signature value:  668

and no connection to jabber account is available.

I would set the priority to high.

Still a problem with recent development versions.

Version 1.0.80
Using KDE Development Platform 4.5.65 (KDE 4.5.65 (KDE 4.6 >= 20100819)) "release 1" on top off OpenSuse 11.3

Since I control the Openfire server I did some testing today and found that the problem seems to be with TLS support.  If I disable TLS and enable only the old SSL method on the server Kopete will succesfully connect.

Here is the error message that is logged when kopete attempts to connect to openfire:

2010.02.19 12:01:04 Closing session due to exception: (SOCKET, R: /127.0.1.1:33753, L: /127.0.1.1:5222, S: 0.0.0.0/0.0.0.0:5222)
org.apache.mina.filter.codec.ProtocolDecoderException: java.lang.Exception: Disallowed character (Hexdump: 80 62 01 03 01 00 39 00 00 00 20 00 00 04 01 00 80 00 00 05 00 00 2F 00 00 33 00 00 32 00 00 0A 07 00 C0 00 00 16 00 00 13 00 00 09 06 00 40 00 00 15 00 00 12 00 00 03 02 00 80 00 00 08 00 00 14 00 00 11 4B 7E 6F 70 A7 61 72 41 DF CB 80 47 07 08 5F 5E B1 9D BF BE 0E A2 BE D7 5B 6C D8 65 29 3E 55 FA)
at org.apache.mina.filter.codec.ProtocolCodecFilter.messageReceived(ProtocolCodecFilter.java:170)

at org.apache.mina.common.support.AbstractIoFilterChain.callNextMessageReceived(AbstractIoFilterChain.java:299)

at org.apache.mina.common.support.AbstractIoFilterChain.access$1100(AbstractIoFilterChain.java:53)

at org.apache.mina.common.support.AbstractIoFilterChain$EntryImpl$1.messageReceived(AbstractIoFilterChain.java:648)

at org.apache.mina.filter.executor.ExecutorFilter.processEvent(ExecutorFilter.java:239)

at org.apache.mina.filter.executor.ExecutorFilter$ProcessEventsRunnable.run(ExecutorFilter.java:283)

at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)

at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)

at org.apache.mina.util.NamePreservingRunnable.run(NamePreservingRunnable.java:51)

at java.lang.Thread.run(Thread.java:619)
Caused by: java.lang.Exception: Disallowed character
at org.jivesoftware.openfire.nio.XMLLightweightParser.read(XMLLightweightParser.java:211)

at org.jivesoftware.openfire.nio.XMPPDecoder.doDecode(XMPPDecoder.java:32)
at org.apache.mina.filter.codec.CumulativeProtocolDecoder.decode(CumulativeProtocolDecoder.java:133)

at org.apache.mina.filter.codec.ProtocolCodecFilter.messageReceived(ProtocolCodecFilter.java:163)

        ... 9 more

(copied from http://dev.eclipse.org/mhonarc/lists/ecf-dev/msg03380.html - exactly same as what I saw in my openfire logs though)


Psi (which uses QCA also) can connect to my openfire server OKAY.  If I recall correctly, kopete and psi were both not able to connect in April 2010.

This seems to be a problem with qca-ossl as described here: https://bugs.archlinux.org/task/19175?dev=280 . If I apply this patch to qca-ossl, it works for me: https://bugs.archlinux.org/task/19175?getfile=5727 (Ubuntu Maverick).

I can confirm this bug on Kubuntu 10.10/KDE 4.5.1. Both Psi and Kopete fail to connect to our openfire server while Gajim,Tkabber and qutIM can connect just fine.

no resolution to that yet?

For what it's worth: I'm experiencing this error with my gmail-account.

If there's something I can do to verify/diagnose this problem apart from posting my console-output, I'd be happy to help.

Qt: 4.7.0
KDE: 4.5.90 (4.6 RC1)
Kopete: 1.0.80
Kubuntu 10.04

Symptom:
- Goggle-Talk Account offline

Sample console-output:
~$ kopete
kopete(7510)/kio (KDirWatch) KDirWatchPrivate::removeEntry: doesn't know "/home/xxx/.kde/share/apps/kabc" 
QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: Datei oder Verzeichnis nicht gefunden
QFileSystemWatcher: failed to add paths: /home/xxx/.config/ibus/bus
Bus::open: Can not get ibus-daemon's address. 
IBusInputContext::createInputContext: no connection to ibus-daemon 
kopete(7510)/kdecore (KLibrary) kde4Factory: The library "/usr/lib/kde4/kopete_history.so" does not offer a qt_plugin_instance function.
kopete(7510)/libkopete Kopete::PluginManager::loadPluginInternal: Unable to find a plugin named ' "" '! 
kopete(7510)/libkopete Kopete::PluginManager::loadPluginInternal: Unable to find a plugin named ' "" '! 
kopete(7510)/libkopete Kopete::PluginManager::loadPluginInternal: Unable to find a plugin named ' "" '! 
Unknown signature value:  795 
Unknown signature value:  795 
Unknown signature value:  795 
Unknown signature value:  795 
Unknown signature value:  795 
Unknown signature value:  795 
Unknown signature value:  795 
Unknown signature value:  795 
Unknown signature value:  795 
Unknown signature value:  795 
Unknown signature value:  795 
Unknown signature value:  795

I have been having this issue with Kopete and our Openfire server for most of this year, on various distributions.  I finally got sick of Pidgin, and started looking into it.

For those of you who control, or can influence, their Openfire configurations, under Server Settings -> Security Settings, set "Client Connection Security" as follows:
*Custom
  Old SSL method:  *Available
  TLS method:  *Required

That fixed my connectivity issues with Kopete (running KDE-unstable on FC14 right now, and kde 4.6 betas on Ubuntu 10.10).

This problem now remains for many months :-) On

I'm also unable to connect to GTalk using Kopete on port 443. But this happens only when I'm behind a proxy. If I'm not behind a proxy and port 5223 is open kopete connects to gtalk fine.

The patch in 16th comment https://bugs.kde.org/show_bug.cgi?id=221533#c16
is not useful. I am facing same problem even after applying the patch as well.

It bugs me too, and affects PSI. Maybe something related to some QT library :(

I've problems too, to connect to openfire server, that keeps me from switching from pidgin.

I'm also having this issue with OpenSUSE 12.1 and Kopete connecting to an OpenFire XMPP private server.

My XML Console gives me something like:
<?xml version="1.0"?>

<stream:stream xmlns:stream="http://etherx.jabber.org/streams" xmlns="jabber:client" to="domain.com">

<?xml version='1.0' encoding='UTF-8'?><stream:stream xmlns:stream="http://etherx.jabber.org/streams" xmlns="jabber:client" from="dc2" id="17a600f4" xml:lang="en">

<iq type="get" to="domain.org" id="auth_1">
<query xmlns="jabber:iq:auth">
<username>user</username>
</query>
</iq>

<iq from="domain.com" type="error" id="auth_1" to="dc2/17a600f4">
<query xmlns="jabber:iq:auth">
<username>user</username>
</query>
<error type="modify" code="400">
<bad-request xmlns="urn:ietf:params:xml:ns:xmpp-stanzas"/>
</error>
</iq>

I still have the problem of being unable to connect to openfire jabber server, is there any workaround for this?

Some help would be really, really appreciated...

Still over a year later and this problem has not been looked at or anything.

I would like to mentioned that this appears to be fixed in Telepathy 15.08

I am again able to connect to my OpenFire Server.

Thank you for the bug report.

As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists.

If this bug is no longer persisting or relevant please change the status to resolved.

I am not using Jabber neither Kopete anymore.