kopete cannot connect to multiple jabber servers after system update

Can you test with old versions of openssl to find out if this is a regression in OpenSSL? (I'd be surprised, since OpenSSL hasn't been updated since June and no one else has reported this issue, but if you can track down which version broke your setup that would be very helpful.)

Thanks

well.. you was right. downgrade from 1.0.1 to 0.9.8 has no effect
my apologies
but kopete is still nonworking
can you move this report to kopete section or should i start new one?

Changing OpenSSL versions didn't appear to affect the client

well, meanwile some new updates comes including new kernel, from 3.13.0-70 to 3.13.0-73,
without any hope I did purge/install and trouble seems the same:

$: kopete --noplugins
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
kopete(4678)/libkopete Kopete::PluginManager::loadPluginInternal: Unable to find a plugin named ' "" '!
Unknown signature value: 668
Unknown signature value: 668
Unknown signature value: 669
<-- skipped overhuge like this-->
Task::go(): attempted to send a task over the broken connection.
<-- and agian -->
Unknown signature value: 668
Unknown signature value: 668
Unknown signature value: 669
QMetaObject::invokeMethod: No such method JabberProtocol::shouldExitOnClose()

end of output

okay. I removed my accounts, perhaps it is problem

apt-get purge kopete
rm ./kde/share/config/kopetrc
rm -fr ./kde/share/apps/kopete
apt-get install kopete

I added only one accounts but no changes. output is perfectly identical
any assumptions? I have no one
I swear I will give any information about this case

well some news again
nor pidgin nor psi do not connect to jabber servers
stdout of psy seems extremly like kopet's one:
$ psi
Bus::open: Can not get ibus-daemon's address.
IBusInputContext::createInputContext: no connection to ibus-daemon
Unknown signature value: 668
Unknown signature value: 668
Unknown signature value: 669
<-- endless of it -->

pidgin is more talkative (if anyone wants I'll put whole output):
(11:55:50) account: Network not connected; skipping reconnect

I almost believe problem is kde network libs, but other net or web and mail utilites work perfectly
it doesn't has a clarity, still any help wanted

Okay
I think I found out reason of problem
I've been using bridge network interface for some KVM reason. networkManager seems like don't support this type of connection in 14.04 LTS so I set up network in /etc/network/interfaces and did not pay attention to networkManager's applet in tray long time before december 1, when I got trouble with connections. I was left without any communications and I has taken desperate measures. it was a real shamanism today.
I booted and got working network connection br0, then I 'connected' eth0 by networkManager's applet. eth0 was configured by my own DHCP server. and by this crooked way I use fully configured br0 and eth0 and then kopete is working. it is absolutely abnormal. I do think this kopete's method of checking network connection is really bad.
shortly speaking if networkManager's applet indicates that eth0 unplugged then kopete do not connect anyway. even if connection via brige works fine. if networkManager believes that eth0 is plugged then Kopet (and psi, pidgin, even telepathy) work perfect. did not work anything of them without networkManager. what is a special way that all of it was worked before system update on december 1 I really do not know and it makes me crazy

if anyone will be able to confirm this bug I will get satisfaction at least

something aboute networkManager and bridge https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1013963

sorry for my poor english