Bug#546544: Bug is still alive.
On Tue, Sep 07, 2010 at 10:39:58PM +0200, Raúl Sánchez Siles wrote: The problem arises when I try to connect with kopete, when I configure it to use SSL, which connects to 5223. In this case I have the message: terminate called after throwing an instance of 'std::logic_error' what(): basic_string::_S_construct NULL not valid and the service dies. I need to manually restart it. There were no relevant information on jabberd14 log. When I configure kopete not to use SSL, ie, use 5222 (possibly without encryption) jabberd14 works correctly. Thanks for take time to report this issue. I use the same client for jabber, I will try to reproduce this problem. -- Miguel Landaeta, miguel at miguel.cc secure email with PGP 0x7D8967E9 available at http://keyserver.pgp.com/ Faith means not wanting to know what is true. -- Nietzsche -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#546544: Bug is still alive.
Hello: Sorry for unarchiving this, but I think this bug is still valid. I've recently managed to configure jabberd14 and now it looks like working when I use Psi client. I'm not sure how Psi negociates the connection, but I suspect it uses STARTTLS on 5222. The problem arises when I try to connect with kopete, when I configure it to use SSL, which connects to 5223. In this case I have the message: terminate called after throwing an instance of 'std::logic_error' what(): basic_string::_S_construct NULL not valid and the service dies. I need to manually restart it. There were no relevant information on jabberd14 log. When I configure kopete not to use SSL, ie, use 5222 (possibly without encryption) jabberd14 works correctly. This part of the information reportbug provides: Version: 1.6.1.1-5 Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing') Architecture: armel (armv5tel) Kernel: Linux 2.6.32-5-kirkwood Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash I've also taken a look at the commit[0] that supposedly fixes this issue, but I have seen little changes. The only meaningful one was adding stddef.h header file. Is this really all that's needed to address the bug? Should I reopen the bug? I'm available for whatever information you need me to provide. Thanks and cheers, [0] http://git.debian.org/?p=collab- maint/jabberd14.git;a=commitdiff;h=f100e86f97991e2a8aa4b5809aab189f7234bc10 -- Raúl Sánchez Siles -Proud Debian user- Linux registered user #416098 signature.asc Description: This is a digitally signed message part.
