Bug#266597: Cannot use SSL/jabber with kopete 3.3.0
Package: kopete
Version: 4:3.3.0-1
Severity: normal
I just updated to kopete 3.3.0-1 and now it refuses to connect to
jabber.org with this message:
SSL support could not be initialized for account meskes@jabber.org. This
is most likely because the QCA TLS plugin is not installed on your
system.
Without SSL it works fine. And of course the 3.2.3 version also worked
with SSL.
Michael
-- System Information:
Debian Release: 3.1
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.8-1-686
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8
Versions of packages kopete depends on:
ii kdelibs4 4:3.3.0-1 KDE core libraries
ii libart-2.0-2 2.3.16-6 Library of functions for 2D graphi
ii libc6 2.3.2.ds1-16 GNU C Library: Shared libraries an
ii libfam0c102 2.7.0-5 client library to control the FAM
ii libgadu3 1:1.5-2 Gadu-Gadu protocol library - runti
ii libgcc1 1:3.4.1-5 GCC support library
ii libglib1.2 1.2.10-9 The GLib library of C routines
ii libgtk1.2 1.2.10-17 The GIMP Toolkit set of widgets fo
ii libice6 4.3.0.dfsg.1-6 Inter-Client Exchange library
ii libidn11 0.5.2-2 GNU libidn library, implementation
ii libjpeg62 6b-9 The Independent JPEG Group's JPEG
ii libpcre3 4.5-1.1 Perl 5 Compatible Regular Expressi
ii libpng12-0 1.2.5.0-7 PNG library - runtime
ii libqt3c102-mt 3:3.3.3-3 Qt GUI Library (Threaded runtime v
ii libsm6 4.3.0.dfsg.1-6 X Window System Session Management
ii libstdc++5 1:3.3.4-9 The GNU Standard C++ Library v3
ii libx11-6 4.3.0.dfsg.1-6 X Window System protocol client li
ii libxext6 4.3.0.dfsg.1-6 X Window System miscellaneous exte
ii libxi6 4.3.0.dfsg.1-6 X Window System Input extension li
ii libxml2 2.6.11-3 GNOME XML library
ii libxrender1 0.8.3-7 X Rendering Extension client libra
ii libxslt1.1 1.1.8-3 XSLT processing library - runtime
ii xlibs 4.3.0.dfsg.1-6 X Window System client libraries m
ii xmms 1.2.10-1 Versatile X audio player that look
ii zlib1g 1:1.2.1.1-5 compression library - runtime
-- no debconf information
Reply to: