What happened: Gabble sent repetitively the chat state "gone" as fast as my laptop could, each time the incoming text channel get closed by Mission Control because of the lack of handler, and re-spawned because it is a text channel. What we should do: - don't send a chat state if we never sent anything in the channel - add a test for that - is it possible to avoid the loop?
MC's meant to call Destroy if the channel is looping.
Maybe so, but we shouldn't send gone if we never sent anything in the first place.
(indeed, the channel should start in a state where it's got no typing notification state at all, and never sends any states or includes them in messages, and only move out of that state and send notifications if the telepathy client calls any such notification methods on it, and this results in a message being sent)
My branch 'going-going-gone' fixes this.
Why did you add a declaration of emit_closed_and_send_gone? It's not used before its definition.
No good reason; I pushed a patch removing it.
Merged; will be in 0.7.29!
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.