Messages are not being dispatched

[Jan Lübbe]

Hello,

I've discovered a strange problem while debugging FSO's frameworkd
(which uses dbus-python):

In a very specific case, one dbus connection used by frameworkd stops
dispatching messages. This occours while waiting for a reply to a method
call which is looped back into frameworkd on another connection.

The method completes correctly and the response is sent, but it is only
queued (and not dispatched to python) on the broken connection. It seems
that even a timeout is not being generated.

I've created a log with DBUS_VERBOSE and was using dbus-monitor at the
same time:

http://sicherheitsschwankung.de/~jluebbe/dbus_verbose_1.log.bz2
http://sicherheitsschwankung.de/~jluebbe/monitor_1.log.bz2

incoming queue 0x16d668 seems to be broken:

Line 119539:
1894: Message 0x8bf9e0 (2 no path no interface no member '' reply to 94) added to incoming queue 0x16d668, 2 incoming

Line 119876:
1894: Message 0x288e88 (2 no path no interface no member '' reply to 95) added to incoming queue 0x16d668, 3 incoming

Line 137452:
1894: Message 0x8022d8 (4 /org/freesmartphone/Device/IdleNotifier/0 org.freesmartphone.Device.IdleNotifier State 's' reply to 0) added to incoming queue 0x16d668, 4 incoming

There are no more messages being dispatched for this connection... i'm
not sure how to continue debugging this.
>From where is the dispatch logic triggered? What could break this?

Thanks,
Jan

-- 
Jan Lübbe <jluebbe at lasnet.de>            http://sicherheitsschwankung.de
 gpg-key      1024D/D8480F2E 2002-03-20
 fingerprint  1B25 F91F 9E7B 5D4F 1282  02D6 8A83 8BE4 D848 0F2E