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 234 - Kopete fails to connect to Zimbra after upgrade
Summary: Kopete fails to connect to Zimbra after upgrade
Status: RESOLVED FIXED
Alias: None
Product: TDE
Classification: Unclassified
Component: tdenetwork (show other bugs)
Version: 3.5.11 [Trinity]
Hardware: Other Linux
: P5 major
Assignee: Timothy Pearson
URL:
Depends on:
Blocks:
 
Reported: 2010-08-20 11:31 CDT by John A. Sullivan III
Modified: 2012-10-19 15:25 CDT (History)
3 users (show)

See Also:
Compiler Version:
TDE Version String: 2.5.11(Trinity)
Application Version: 0.12.7
Application Name: Kopete

Attachments
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 John A. Sullivan III 2010-08-20 11:31:36 CDT 
I am using Trinity on Debian Lenny with several packages from backports and Squeeze.  Kopete was working perfectly fine connecting to Zimbra 6.0.7.  I did an apt-get upgrade today which updated many Trinity packages. Since then, Kopete launches but cannot connect.  It looks like missing signals and slots.  Here is stdout/stderr after right clicking on the task bar icon as setting general status to online:

jasiii@jasiii:~$ kopete
jasiii@jasiii:~$ QObject::connect: No such slot XMPP::S5BServer::ss_incomingUDP(const QString&,int,const QHostAddress&,int,const QByteArray&)
QObject::connect:  (sender name:   'unnamed')
QObject::connect:  (receiver name: 'unnamed')
QObject::connect: No such signal XMPP::JT_PushS5B::incomingUDPSuccess(const Jid&,const QString&)
QObject::connect:  (sender name:   'unnamed')
QObject::connect:  (receiver name: 'unnamed')
QObject::connect: No such signal XMPP::JT_PushS5B::incomingActivate(const Jid&,const QString&,const Jid&)
QObject::connect:  (sender name:   'unnamed')
QObject::connect:  (receiver name: 'unnamed')
QObject::connect: No such slot SecureLayer::tlsHandler_readyRead(const QByteArray&)
QObject::connect:  (sender name:   'unnamed')
QObject::connect:  (receiver name: 'unnamed')
QObject::connect: No such slot SecureLayer::tlsHandler_readyReadOutgoing(const QByteArray&,int)
QObject::connect:  (sender name:   'unnamed')
QObject::connect:  (receiver name: 'unnamed')
QObject::connect: No such signal SecureLayer::tlsClosed(const QByteArray&)
QObject::connect:  (sender name:   'unnamed')
QObject::connect:  (receiver name: 'unnamed')
QObject::connect: No such signal SecureLayer::readyRead(const QByteArray&)
QObject::connect:  (sender name:   'unnamed')
QObject::connect:  (receiver name: 'unnamed')
QObject::connect: No such signal SecureLayer::needWrite(const QByteArray&)
QObject::connect:  (sender name:   'unnamed')
QObject::connect:  (receiver name: 'unnamed')

The final result is that I can no longer communicate via chat with other Zimbra users unless I disable SSL (which I cringe to do with chat).
Comment 1 Timothy Pearson 2010-08-21 00:31:48 CDT 
This bug should now be fixed; it was a simple makefile/moc problem.

Please reopen this bug if it is still present after upgrading kdenetwork-trinity.
Comment 2 John A. Sullivan III 2010-08-21 12:11:56 CDT 
Alas, it looks like it is still broken:

jasiii@jasiii:~$ QObject::connect: No such slot SecureLayer::tlsHandler_readyRead(const QByteArray&)
QObject::connect:  (sender name:   'unnamed')
QObject::connect:  (receiver name: 'unnamed')
QObject::connect: No such slot SecureLayer::tlsHandler_readyReadOutgoing(const QByteArray&,int)
QObject::connect:  (sender name:   'unnamed')
QObject::connect:  (receiver name: 'unnamed')
QObject::connect: No such signal SecureLayer::tlsClosed(const QByteArray&)
QObject::connect:  (sender name:   'unnamed')
QObject::connect:  (receiver name: 'unnamed')
QObject::connect: No such signal SecureLayer::readyRead(const QByteArray&)
QObject::connect:  (sender name:   'unnamed')
QObject::connect:  (receiver name: 'unnamed')
QObject::connect: No such signal SecureLayer::needWrite(const QByteArray&)
QObject::connect:  (sender name:   'unnamed')
QObject::connect:  (receiver name: 'unnamed')

This was after doing an apt-get update and apt-get upgrade so I updated everything and not just kdenetwork.
Comment 3 Timothy Pearson 2010-08-21 18:50:48 CDT 
I missed a couple Makefiles; the Kopete build system is (was!) a bit different than the rest of Trinity.

Upgrade kdenetwork-trinity and try again; hopefully this time it truly is fixed.