Bug 59309 - QObject::connect: No such signal OscarContact::contactDestroyed(KopeteContact*c)
Summary: QObject::connect: No such signal OscarContact::contactDestroyed(KopeteContact*c)
Status: RESOLVED FIXED
Alias: None
Product: kopete
Classification: Unmaintained
Component: ICQ and AIM Plugins (other bugs)
Version First Reported In: 0.6.2
Platform: RedHat Enterprise Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Kopete Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-06-04 05:27 UTC by michael
Modified: 2003-06-30 20:02 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description michael 2003-06-04 05:27:03 UTC 
Version:           0.6.2 (using KDE KDE 3.1)
Installed from:    RedHat RPMs
OS:          Linux

I'm not sure why, but when running Kopete, I get the following console output.  It happened after I set up my accounts for the first time and hit the "Connect All" button.

QObject::connect: No such signal OscarContact::contactDestroyed(KopeteContact*c)
QObject::connect:  (sender name:   'unnamed')
QObject::connect:  (receiver name: 'unnamed')

This message repeats over and over until the contact list has been filled in.
Comment 1 Matt Rogers 2003-06-14 17:51:27 UTC 
This is just a debugging message and shouldn't cause any harm. As long as kopete doesn't 
crash or exhibit any strange behavior any strange behavior, then I'll close this bug in about a 
week.   
 
Thanks, 
Matt
Comment 2 Martijn Klingens 2003-06-14 17:54:28 UTC 
Subject: Re: [Kopete-devel]  QObject::connect: No such signal OscarContact::contactDestroyed(KopeteContact*c)

On Saturday 14 June 2003 17:51, Matt Rogers wrote:
> This is just a debugging message and shouldn't cause any harm. As
> long as kopete doesn't crash or exhibit any strange behavior any strange
> behavior, then I'll close this bug in about a week.

Please don't.

Although indeed a broken slot connection hardly ever causes crashes the code 
still needs to be fixed. Consider this bug a nice reminder :)
Comment 3 Matt Rogers 2003-06-21 00:19:14 UTC 
> Although indeed a broken slot connection hardly ever causes crashes the code 
> still needs to be fixed. Consider this bug a nice reminder :) 

and a nice reminder it is. :)
Comment 4 Olivier Goffart 2003-06-30 20:02:25 UTC 
this has been fixed in cvs.