By default, Bugzilla does not search the list of RESOLVED bugs.
You can force it to do so by putting the upper-case word ALL in front of your search query, e.g.: ALL tdelibs
We recommend searching for bugs this way, as you may discover that your bug has already been resolved and fixed in a later release.
Bug 1412 - TQCA-TLS not recognized by Kopete
Summary: TQCA-TLS not recognized by Kopete
Status: RESOLVED FIXED
Alias: None
Product: TDE
Classification: Unclassified
Component: tdenetwork (show other bugs)
Version: R14.0.0 [Trinity]
Hardware: All Debian Squeeze
: P5 major
Assignee: Slávek Banko
URL:
Depends on:
Blocks:
 
Reported: 2013-02-26 14:03 CST by Kris
Modified: 2013-07-24 16:32 CDT (History)
6 users (show)

See Also:
Compiler Version:
TDE Version String:
Application Version:
Application Name:

Attachments
Fix visibility of createProvider, rename lib to tqca-tls (1.41 KB, patch)
2013-07-23 20:16 CDT, Slávek Banko 		Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Kris 2013-02-26 14:03:33 CST 
This may be a Debian packaging issue, I haven't seen reports of it happening elsewhere, and I personally cannot test on other distros at them moment.

I have installed the tqca-tls and I'm trying to connect Kopete to a Jabber connection (in this case, GTalk) which requires protocol encryption. Kopete reports that tqca-tls isn't installed even though it is.

The exact message is:

SSL support could not be initialized for account <myprivateaccount>@gmail.com. This is most likely because the TQCA-TLS is not installed on your system.
Comment 1 Darrell 2013-04-14 11:34:07 CDT 
Do you know whether this worked previously? (Is this a regression?)
Comment 2 Slávek Banko 2013-04-14 12:23:22 CDT 
I believe that I see where the problem is. The package is properly called tqca-tls, library is correctly placed in /usr/lib/tqt3/plugins/crypto, but the library itself is called libqca-tls.so not libtqca-tls.so.

Please try to rename the library to confirm this.
Comment 3 Kris 2013-04-14 12:45:46 CDT 
(In reply to comment #1)
> Do you know whether this worked previously? (Is this a regression?)

I cannot say. Prior to discovering this bug, the Jabber protocol wasn't recognized (bug #1309). However, that bug now *seems* resolved, but I cannot tell for sure until this bug is resolved.
Comment 4 Kris 2013-04-14 12:49:21 CDT 
(In reply to comment #2)
> I believe that I see where the problem is. The package is properly called
> tqca-tls, library is correctly placed in /usr/lib/tqt3/plugins/crypto, but the
> library itself is called libqca-tls.so not libtqca-tls.so.
> 
> Please try to rename the library to confirm this.

Renaming does not help, not even after logging out, restarting TDM, and logging back in.
Comment 5 Timothy Pearson 2013-04-14 13:49:32 CDT 
(In reply to comment #4)
> (In reply to comment #2)
> > I believe that I see where the problem is. The package is properly called
> > tqca-tls, library is correctly placed in /usr/lib/tqt3/plugins/crypto, but the
> > library itself is called libqca-tls.so not libtqca-tls.so.
> > 
> > Please try to rename the library to confirm this.
> 
> Renaming does not help, not even after logging out, restarting TDM, and logging
> back in.

Note that ldconfig will probably need to be rerun after renaming the libray file.
Comment 6 Kris 2013-04-14 14:01:50 CDT 
(In reply to comment #5)
> (In reply to comment #4)
> > (In reply to comment #2)
> > > I believe that I see where the problem is. The package is properly called
> > > tqca-tls, library is correctly placed in /usr/lib/tqt3/plugins/crypto, but the
> > > library itself is called libqca-tls.so not libtqca-tls.so.
> > > 
> > > Please try to rename the library to confirm this.
> > 
> > Renaming does not help, not even after logging out, restarting TDM, and logging
> > back in.
> 
> Note that ldconfig will probably need to be rerun after renaming the libray
> file.

Simply running ldconfig with no parameters does not help. Are there any parameters that should be specified? (I am not familiar with ldconfig, nor what it does)
Comment 7 Francois Andriot 2013-07-03 00:10:30 CDT 
Package pushed to the official repositories.
Comment 8 Francois Andriot 2013-07-03 00:13:20 CDT 
Sorry wrong bug here !
I intended to close #1527 not this one !
Comment 9 Slávek Banko 2013-07-23 20:16:16 CDT 
Created attachment 1376 [details]
Fix visibility of createProvider, rename lib to tqca-tls

I examined the situation and found that because of visibility=hidden function 'createProvider' is not available in libtqca-tls.so.

I attach proposal patch.
Comment 10 Francois Andriot 2013-07-24 02:51:46 CDT 
From what I understand in "kopete/protocols/jabber/libiris/qca/src/qca.cpp", the name of the .so file does not matter, since kopete tries to load every file under "crypto" directory from (T)QT3.

Also, I've found out that, in TQCA-TLS, in file "qca-tls.pro", the define "QCA_PLUGIN" is wrong, it should be "TQCA_PLUGIN" (see how it's used in "qca-tls.h" . I think this is the reason why the "createProvider" is not available to Kopete.
Comment 11 Francois Andriot 2013-07-24 02:53:59 CDT 
... so what I mean is you probably found out the solution, but I do not understand the "visibility option" stuff. I did not use it when building TQCA-TLS for 3.5.13.2.
Comment 12 Francois Andriot 2013-07-24 03:07:21 CDT 
Just built with your patch as is: it looks like it works: Kopete can now use Jabber+SSL protocol.
Comment 13 Slávek Banko 2013-07-24 12:56:19 CDT 
Yes, renaming libqca-tls to libtqca-tls is the only for form.

I had it exactly the same:
+ in 3.5.13.2 without problems
+ then attempt to rename the QCA_PLUGIN => TQCA_PLUGIN, without success
+ in next step I found problem due to visibility=hidden

As I tested with the original qt3 visibility is not used in the build flags. With tqt is used visibility=hidden, that leading to this problem.

Thank you for the test, I'll proceed to push patch into GIT.
Comment 14 Slávek Banko 2013-07-24 16:32:41 CDT 
Fixed in GIT hash 49aac943.