| Summary: | Odd KMail messages in xsession log | ||
|---|---|---|---|
| Product: | TDE | Reporter: | Darrell <darrella> |
| Component: | tdepim | Assignee: | Timothy Pearson <kb9vqf> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | bugwatch, darrella, slavek.banko |
| Priority: | P5 | ||
| Version: | R14.0.0 [Trinity] | ||
| Hardware: | Other | ||
| OS: | Linux | ||
| Compiler Version: | TDE Version String: | ||
| Application Version: | Application Name: | ||
This should be fixed in GIT hash acecca8. Please check for any new kmail issues which might have been caused by reconnecting these long-dormant slots before closing this bug report. With the patch the signal/slot errors no longer appear. Thanks. As I do not see any other related kmail errors, I'm closing this report as resolved. |
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) The messages likely mean a definition of a slot function was changed but an associated signal wasn't. I do not notice any failures in KMail, but that does not mean other people don't or that the bugs are not related to other KMail bug reports. :-)