python - using a signal not in introspection

[John (J5) Palmieri]

On Wed, 2007-04-25 at 17:38 -0400, Havoc Pennington wrote:
> Hi,
> 
> notification-daemon omits its signals from the introspection data (looks 
> like because dbus-glib creates the introspection data but the signals 
> are done manually in order to set a sender on them)
> 
> I can't seem to convince dbus-python 0.70 (FC6) to get the signals with 
> either connect_to_signal or add_signal_receiver. The signals are on the 
> bus according to dbus-monitor.
> 
> Is the introspection info used even for add_signal_receiver, or does 
> this function maybe not work in 0.70, or ... ?
> 
> If anyone wants to mess with it the signal is 
> org.freedesktop.Notifications.ActionInvoked on bus name 
> org.freedesktop.Notifications
> 
> I'm probably doing something silly.

I believe we send ActionInvoked signals to the caller who started the
notification (set_destination with the unique name) so if your python
app isn't the caller it won't get them.
 
-- 
John (J5) Palmieri <johnp at redhat.com>