[Telepathy] [Bug 17353] Delayed Signals after changing my presence state.

[bugzilla-daemon at freedesktop.org]

http://bugs.freedesktop.org/show_bug.cgi?id=17353


Olli Salli <ollisal at gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |NOTOURBUG




--- Comment #1 from Olli Salli <ollisal at gmail.com>  2008-08-30 10:55:25 PST ---
The TelepathyQt4 library does no processing, queuing or anything else to
emissions of that signal, in fact nothing in the library itself is connected to
the signal. The signal simply is declared in the proxy class for QtDBus to
match signals received over DBus against, and you getting the signals otherwise
indicates the signal is declared correctly.

Are you sure you are returning to the Qt event loop properly while waiting for
the signal to happen? (or running a separate QEventLoop?) Other such simple
issues? Otherwise, the problem likely lies in service space (in the
Gabble/TpPresenceMixin implementation).

Of course, a weird QtDBus bug might be a cause, but as QtDBus doesn't in any
way unpack complex types (such as the PresencesChanged arguments), I can't see
any way it could possibly handle signal emissions in a different fashion in
different cases.

In any case, cannot be a bug in TelepathyQt4. Tracking up the problem should be
started with running your application with QDBUS_DEBUG=2 ./yourapp, running
dbus-monitor, and possibly also running the Telepathy connection manager with
debugging enabled (for Gabble, do GABBLE_DEBUG=all telepathy-gabble). That way
you can see where in the chain the event is lost.


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.