Bug 170217

Summary:	Bad signal/slot connection
Product:	[Unmaintained] kopete	Reporter:	Daniel Winter <dw>
Component:	Jabber Plugin	Assignee:	Kopete Developers <kopete-bugs-null>
Status:	RESOLVED WORKSFORME
Severity:	normal	CC:	sven.burmeister, tomastrnka
Priority:	NOR	Keywords:	investigated, triaged
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Compiled Sources
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Daniel Winter 2008-09-01 23:12:40 UTC

Version:            (using Devel)
OS:                Linux
Installed from:    Compiled sources

Since an update to svn trunk from yesterday I can not connect to my jabber server anymore.

The last build where it was working was a few weeks old.

That is the output from Kopete when trying to connect (It shows "connecting all the time in the GUI):

kopete(24330)/kopete (jabber) JabberBaseContact::reevaluateStatus: New status for  "danielw@jabber.der-winti.de"  is  "Connecting"
kopete(24330) KopeteWindow::slotIdentityStatusIconChanged: QVariant(, )
kopete(24330)/libkopete Kopete::Contact::setStatusMessage: Setting up the status title property with this:  ""
kopete(24330)/libkopete Kopete::Contact::setStatusMessage: Setting up the status message property with this:  ""
kopete(24330)/kopete (jabber) JabberResourcePool::lockToResource: Locking  "danielw@jabber.der-winti.de"  to  "Kopete"
kopete(24330)/kopete (jabber) JabberResourcePool::removeLock: Removing resource lock for  "danielw@jabber.der-winti.de"
kopete(24330)/kopete (jabber) JabberResourcePool::removeLock: No locks found.
kopete(24330)/kopete (jabber) JabberConnector::JabberConnector: New Jabber connector.
kopete(24330)/kopete (jabber) JabberByteStream::JabberByteStream: Instantiating new Jabber byte stream.
kopete(24330)/kopete (jabber) JabberConnector::setOptSSL: Setting SSL to  false
kopete(24330)/kopete (jabber) JabberConnector::setOptHostPort: Manually specifying host  ""  and port  5222
kopete(24330)/kopete (jabber) JabberByteStream::close: Closing stream.
kopete(24330)/kopete (jabber) JabberConnector::connectToServer: Initiating connection to  "jabber.der-winti.de"
kopete(24330)/kopete (jabber) JabberByteStream::connect:  Connecting to  "" , port  5222
Object::connect: Parentheses expected, signal QSslSocket::QAbstractSocket::SocketError
Object::connect: No such signal QSslSocket::closed()

Comment 1 Daniel Winter 2008-09-01 23:55:56 UTC

OK, the problem was that somehow my kopete settings got lost because of a full harddisk.

It is set to use the default hostname derived from the jabber-id. So I think it is still a bug, that although it still know the jabber id it trys to connect to an empty hostname. In such cases.

But the real bug still there is the connection of a non existing signal. I think it is causing kopete not so show when a connection failed.  (It always says "connecting".

Comment 2 Tomas Trnka 2009-01-28 23:10:37 UTC

Can someone reproduce this with recent versions of Kopete? Otherwise I'll close the bug...

Comment 3 Matt Rogers 2009-03-29 03:44:15 UTC

No response on whether this is still reproducible. Closing.

Comment 4 Andrew Crouthamel 2018-09-19 04:34:29 UTC

Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

Comment 5 Andrew Crouthamel 2018-10-21 04:20:36 UTC

This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!