In <[EMAIL PROTECTED]>, you wrote: > remove_signal_receiver() takes and releases a lock (which protects the > signal-match tree from concurrent modification when dbus-python is used > multi-threaded). I'll check other places where this lock is used - > there's probably some code path where it's not being released properly.
FWIW after I read this I thought perhaps it's a reentrancy problem, caused by the application trying to call remove_signal_receiver() from a signal receiver. So I made DevTray defer the calls with gobject.idle_add() but it still froze. So I was on the wrong track :-(. -- TH * http://www.realh.co.uk -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
