| Summary: | Kopete Jabber support not working | ||
|---|---|---|---|
| Product: | TDE | Reporter: | Tiago Marques <tiagomnm> |
| Component: | tdenetwork | Assignee: | Timothy Pearson <kb9vqf> |
| Status: | RESOLVED FIXED | ||
| Severity: | major | CC: | bugwatch, darrella |
| Priority: | P5 | ||
| Version: | 3.5.12 [Trinity] | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Compiler Version: | TDE Version String: | ||
| Application Version: | Application Name: | ||
|
Description
Tiago Marques
2011-10-26 10:55:45 CDT
System is Ubuntu 11.04 with Trinity SVN (In reply to comment #0) > Try to add an account but get an error. Thoughts? Might try to look into the > bug but would like some idea of where to look, if anyone knows. Can you post the error message? "Cannot load the jabber protocol plugin." I wanted to add a screenshot but it isn't working. I select the file and it doesn't add it. Will send an e-mail to the ML about that. This is a nasty problem. A regression test of Kopete back to 3.5.12 is not able to resolve the issue (compiling the 3.5.12 Kopete source on 3.5.13 still results in a Jabber failure). Tracing the function calls, dlopen() in kdelibs ltdl.c appears to be unable to load the /opt/trinity/lib/trinity/kopete_jabber.so file, even though a quick check of the dynamic dependencies with ldd did not show any unresolved symbols. I am not sure this can be fixed for 3.5.13.... I have modified kdelibs in SVN revision 1261212 to output debugging information when an error such as this occurs, to simplify debugging of other applications that use TDE plugins as well as this one. The undefined symbol is _ZTV11SecureLayer Still working on it... Fixed in SVN revision 1261215. Thanks for reporting! ========================================================================== If you find our work useful donations to the project are much appreciated! No problem, thank you very much for fixing it! Today I updated #555, though it isn't exactly critical for the system to work :) Had I known the schedule I would have done a thorough test and reporting sooner. Give me a bump when you need QA done ;) Best regards, Tiago (In reply to comment #7) > No problem, thank you very much for fixing it! > > Today I updated #555, though it isn't exactly critical for the system to work > :) > > Had I known the schedule I would have done a thorough test and reporting > sooner. Give me a bump when you need QA done ;) > > Best regards, > Tiago Sure! This release was more than a little rushed due to the massive changes "under the hood" in Trinity as well as in the major Linux distributions. Future releases will have a scheduled soft freeze, a much longer Q/A period, then the hard freeze and release shortly thereafter. Tim |