Description of problem:
=============================

Notification not received, when a buddy client goes offline by virtue of being disconnected from the wifi (telepathy-salut) network.




Version-Release number of selected component (if applicable):
=================================================================
F17





Steps to Reproduce:
==========================

When a contact disconnects (from the telepathy network), the callback
function, specified for the signal

http://telepathy.freedesktop.org/spec/Connection_Interface_Contact_List.html#Signal:ContactsChangedWithID

is NOT hit.





  
Actual results:
===================
The callback function, specified for the signal

http://telepathy.freedesktop.org/spec/Connection_Interface_Contact_List.html#Signal:ContactsChangedWithID

is NOT hit.






Expected results:
===================
The callback function, specified for the signal

http://telepathy.freedesktop.org/spec/Connection_Interface_Contact_List.html#Signal:ContactsChangedWithID

SHOULD BE hit.






Additional info:
===================

a)
One thing I notice is that both - 'ContactChanged' and 'ContactsChangedWithID' - callbacks are hit when the buddy comes online, but are NOT hit when the same buddy goes offline (by disconnecting from the telepathy-salut wifi network).

So, I guess I am using the code properly at least, in case of both 'ContactsChanged' and 'ContactsChangedWithID'.




b)
Following are the telepathy-packages, that were installed on F17 where this bug occurred ::

telepathy-haze-0.6.0-1.fc17.i686
telepathy-idle-0.1.11-2.fc17.i686
telepathy-logger-0.4.0-2.fc17.i686
python-telepathy-0.15.19-4.fc17.noarch
telepathy-farstream-0.4.0-2.fc17.i686
telepathy-filesystem-0.0.2-3.fc17.noarch
telepathy-mission-control-5.12.0-1.fc17.i686
telepathy-glib-0.18.0-1.fc17.i686
telepathy-salut-0.8.0-1.fc17.i686
telepathy-gabble-0.16.0-1.fc17.i686