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 will file the bug reports. Before I do that would you provide some coaching hints as to what to look for? As I'm continually trying to learn more about this game, perhaps I can get lucky and patch them without filing the reports.

I understand the concept of signals and slots, but that is about all. What am I looking for?

Darrell

...

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?

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/bugzill...

In addition to these messages, I have one similar from Amarok: QObject::connect: Incompatible sender/receiver arguments StarManager::ratingsColorsChanged() --> ContextBrowser::ratingOrScoreOrLabelsChanged(const QString&)

I confirm the amarok messages. My GIT output looks like this:

TQLayout "unnamed" added to TQVBox "unnamed", which already has a layout TQLayout: Adding KToolBar/mainToolBar (child of TQVBox/unnamed) to layout for PlaylistWindow/PlaylistWindow TQObject::connect: Incompatible sender/receiver arguments StarManager::ratingsColorsChanged() --> ContextBrowser::ratingOrScoreOrLabelsChanged(const TQString&)

When quitting amarok I see the following:

TQObject::disconnect: Unexpected null parameter TQObject::connect: Cannot connect (null)::activePartChanged( KParts::Part * ) to KHTMLPart::slotActiveFrameChanged( KParts::Part * )

With respect to amarok, I see the same equivalent messages in kde3. Therefore those "bugs" have existed before Trinity:

kde3 startup:

QLayout "unnamed" added to QVBox "unnamed", which already has a layout QLayout: Adding KToolBar/mainToolBar (child of QVBox/unnamed) to layout for PlaylistWindow/PlaylistWindow QObject::connect: Incompatible sender/receiver arguments StarManager::ratingsColorsChanged() --> ContextBrowser::ratingOrScoreOrLabelsChanged(const QString&)

kde3 quitting:

QObject::disconnect: Unexpected null parameter QObject::connect: Cannot connect (null)::activePartChanged( KParts::Part * ) to KHTMLPart::slotActiveFrameChanged( KParts::Part * )

With respect to the kmail messages, I do not see those in kde3. Therefore they likely were introduced in Trinity.

Darrell