Run time issue with queued argument of type uint32_t

[pasnox]

The omemo stack use that in signals connection, unfortunately it's not registered via qRegisterMetatype and cause run time issue in xmpp, which break kaidan omemo support.
This would lead to have some contact for which I can speak omemo, and some not.
Kaidan tried to fix it, but it seems not enough and needs to be fixed in xmpp itself as it's there the queued connectons are done.

[lnjX]

Where are queued connections done in QXmpp?

[melvo]

There are several signals emitted in the OMEMO manager such as

qxmpp/src/omemo/QXmppOmemoManager_p.cpp

Line 2546 in 8542082

Q_EMIT q->deviceAdded(jid, deviceId);

having parameters of type uint32_t. Could that be the problem?

[lnjX]

Those signals don't use queued connections, because both OmemoManager and OmemoManagerPrivate are always on the same thread.

[lnjX]

And the other (easier) option to solve this issue is probably to use quint32 instead of uint32_t, I guess?

[pasnox]

I did not check the code, I just saw Qt throwing the usual warning about queued arguments type not registered, so somewhere in QXmpp or kaidan there is an issue. And yes moving to quint32 is probably a better change.