GNOME Bugzilla – Bug 316172
Composing message triggers new message notification
Last modified: 2005-10-09 00:20:48 UTC
[From bugs.debian.org/327881] Since I upgraded to 0.9, Gossip has been firing off the 'new message' sound + flashing notification area icon seemingly at random while talking to another Jabber user. Today I found about LM_DEBUG=ALL and discovered that this is what is triggering the event: RECV [161]: ----------------------------------- '<message xmlns='jabber:client' to='sam@robots.org.uk/home' from='XXXXXXXXXXXXXXXX@jabber.org/Home'> <x xmlns='jabber:x:event'> <id/> <composing/> </x> </message>' ----------------------------------- *** Read: 161 chars LM-PARSER: ATTRIBUTE: xmlns = jabber:client LM-PARSER: ATTRIBUTE: to = sam@robots.org.uk/home LM-PARSER: ATTRIBUTE: from = XXXXXXXXXXXXXXXX@jabber.org/Home LM-PARSER: ATTRIBUTE: xmlns = jabber:x:event LM-PARSER: Trying to close node: id LM-PARSER: Trying to close node: composing LM-PARSER: Trying to close node: x LM-PARSER: Trying to close node: message LM-PARSER: Have a new message *** New message with type="message" from: XXXXXXXXXXXXXXXX@jabber.org/Home I guess this is a 'user is typing' notification that Gossip is mis-recognising as a message from that user.
Yea, sounds like it. I have just committed work that reimplements typing notifications into Gossip, it seems to work well. There is an obvious distinction in the code now between an x event and a normal message so hopefully this will not happen again. Let me know if it does, I am marking this as fixed, Thanks Ross ;)