10 Jul
2012
10 Jul
'12
7:33 p.m.
On Wednesday 11 of July 2012 03:06:45 Darrell Anderson
wrote:
Those messages do mean that there is a bug somewhere; someone likely
changed the C++ definition of a slot function and forgot to update the
signal that triggers it.
I notice the following messages in my xsession
log when I start KMail:
[tdeinit] kmail is executable and not a library. Launching with exec.
TQObject::connect: Incompatible sender/receiver arguments
KMFolderMgr::msgRemoved(KMFolder*,TQ_UINT32) -->
KMMsgIndex::slotRemoveMessage(TQ_UINT32) TQObject::connect: Incompatible
sender/receiver arguments
KMFolderMgr::msgAdded(KMFolder*,TQ_UINT32) -->
KMMsgIndex::slotAddMessage(TQ_UINT32) TQObject::connect: Incompatible
sender/receiver arguments
KMFolderMgr::msgRemoved(KMFolder*,TQ_UINT32) -->
KMMsgIndex::slotRemoveMessage(TQ_UINT32) TQObject::connect: Incompatible
sender/receiver arguments
KMFolderMgr::msgAdded(KMFolder*,TQ_UINT32) -->
KMMsgIndex::slotAddMessage(TQ_UINT32)
Do the messages mean a bug?
Darrell
I see the same messages on 3.5.13.1, but when using KMail not noticed any
major problems. Perhaps the occasional one that is reported as
http://bugs.pearsoncomputing.net/bugzilla/bugzilla/bugzilla/bugzilla/bugzil…
In addition to these messages, I have one similar from
Amarok:
QObject::connect: Incompatible sender/receiver arguments
StarManager::ratingsColorsChanged() -->
ContextBrowser::ratingOrScoreOrLabelsChanged(const QString&)
Same thing. These would be trivial bug reports in all likelihood.
Tim