Miranda Version : 0.10.0.8 Unicode Build : Yes Test Build # (if applicable) : Plugin Version # (if applicable) : jabber 0.10.0.8

What steps will reproduce the problem? 1. chat with someone in your gtalk roster 2. the other person using pidgin

What is the expected result? i should see the typing notification and the other person should also see when i'm typing.

What happens instead? i dont see when he is typing and he does not see when i'm typing. when we both use pidgin then it works. i think the problem was introduced when i update to miranda 0.10x

We are seeing a similar issue here.

We have Miranda clients on several PCs all on our local network and a private Jabber server on a spare Ubuntu box. As far as I know, we only use Jabber. The PCs are running a mix of Windows XP, Win 7 Pro 32-bit and Win 7 Pro 64-bit. All PCs have Miranda 0.10.0.8.

Before the upgrade to 0.10.0.8, typing notifications appeared as expected. After the upgrade, typing notifications do not appear in chat sessions between PCs running Miranda.

Interestingly, they do appear for chat sessions between Empathy 2.30.3 running on the Ubuntu server and any of the Miranda instances on PCs.

Still no typing notification for us after updating to the latest 0.10.3. This is clearly some regression that happened sometime around 0.10.0.8.

I've tested some random old Miranda versions, until back to v0.9.x branch and it appears that all have the same problem.

Unfortunately I didn't had the chance to install Miranda while Google talk typing notifications were actually working...

On the same Windows 7 x64 PC: 1) The ICQ typing notifications on Miranda IM v0.10.8 (unicode), been received and sent correctly. 2) Google talk typing notifications via Pidgin IM client, been received and sent just correctly.

I've found something interesting though:

If I open both Miranda and Pidgin and I use Pidgin to send a message to someone, then Miranda receives and sends typing notifications just fine to that person, for as long as Pidgin is logged in on the same account.

That probably means that it is not a network or server problem.

I confirm that typing notification has been broken somehow starting with Miranda 0.10.0.8 (and it still hasn't been fixed in current 0.10.8.0).

Typing notifications are not seen at all while working with XMPP services of yandex.ru and jabber.ru (both running ejabberd server). According to this fact and some previous comments I assume that this issue is related to jabber plugin in general, not just to working with some particular XMPP service (I would suggest changing the issue topic if it would be possible).

Strangely enough, typing notifications are shown normally when working with my corporative XMPP service (running Openfire server), but with some nuances: - if a user has only one XMPP resource he sees typing notifications right after the other client starts to type; - if the user has more than one resource he would see typing notifications only after the first message has been received (i.e. his resource has been selected by the other client). But I assume this behavior is normal and conforms to "Re-designed resource selection logic" introduced by Miranda 0.10.0.8.

I have exactly the same problem. I'm not really into the miranda source code, so I can't say what side effects my patch has, but I found a misterious looking comparison around line 351 in protocols/JabberG/jabber_list.cpp (it's ListGetBestResourceNamePtr). It says:

if ( LI->resourceCount > 1 ) {

If I understand it correctly, it means "if at least two resources are online". I changed it to

if ( LI->resourceCount >= 1 ) {

and now the typing notifications work again after both sites sent at least one message. The "> 1" also explains why it helps to be online with two clients (as described in #5).

I'm not sure what the intention of the comparison is, and whether this hack breaks some other parts of the protocol. But for me, it works for the moment :-)

Sorry, I did not attach the patch properly.

Yep, there seems to be a little bug: The point is that if there is only one ressource, there is no choice :) Jabber plugin will use the one and only ressource, so simple :) skip the selection algorithm...

There is still a bug left as I see it (then res variable isnt initialized):

The condition should be as it is, and there should be a catching clause to use first ressource if everything else fails

Leave if ( LI->resourceCount > 1 ) as it is and put something like that on the end AFTER the if:

if ( !res && LI->resource)res = LI->resource[0].resourceName;

Use first ressource if there is only one por no other can be determined