Jabberd2 cannot handle certain Jabber clients

[Akshat Aranya]

I'm running jabberd2.0s8-0ubuntu5 on edgy and I am unable to get PSI and Kopete to connect with the server. In my configuration, I am using PAM authentication and have also turned on TLS and require TLS. I am able to connect with Gaim without any problem. However, PSI and Kopete give me the following error in c2s.log:

Thu Sep 28 11:17:11 2006 [notice] [8] [138.xxx.xxx.xxx, port=54266] connect
Thu Sep 28 11:17:11 2006 [notice] [8] [138.xxx.xxx.xxx, port=54266] error: XML parse error (not well-formed (invalid token))
Thu Sep 28 11:17:11 2006 [notice] [8] [138.xxx.xxx.xxx, port=54266] disconnect

Unfortunately, that's the only info I get. If there's any way to get a more verbose output, I can definitely try it out and give more info.

Thanks,
Akshat

[Akshat Aranya (aaranya+ubuntu)]

I've been able to reproduce the same bug on Fedora Core 4, so this is an upstream bug.

[Lionel Le Folgoc (mrpouit)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Thanks in advance.

[Maarten Fonville (maarten-fonville)]

When searching at google for this bug it seems that most cases of this error are caused by unicode/non-unicode compliance. They have committed a fix now (dec 2007) so i propose this bug being closed and re-opened if Akshat reports if this bug is still residing in feisty.

[Connor Imes (ckimes)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!