Does anyone have a non-working empathy in gtalk? I don’t mean voice and video, I mean normal text chat. I can send messages fine but can’t receive any. People get my messages but I never see a response. It’s as if they never respond.
Searching for bugs has been unfruitful – most of them that mention gtalk are bugs about the voice/video implementation so searching has been cluttered with the wrong bugs. None of my empathy installs work, which leads me to believe that I could have configured them wrong in the account dialog. Any help would be appreciated, especially if you have a bug report to link me to.
Thanks internet!
I have that problem when i’m logged into gmail and to the embed webchat, all the replies go to the embed webchat instead of to my empathy, it’s really weird.
@nxvl: did you try to set a higher value in the ‘Priority’ spin box of your gtalk settings in empathy? Maybe you can resolve with that. That value sets where the messages will go, as you can use two instances of the same account in two different machines. At least it worked for me with two instances of empathy, but never tried with empathy and web-gtalk interface.
Yeah, I can reproduce that. If I send an IM from my Jabber on Pidgin, the message goes across fine. If I send one from GTalk on Empathy to Jabber on Pidgin, nothing. If I add my GTalk to my Jabber’s buddy list in Pidgin, the “Send To” menu in the conversation window, which *should* show all available versions of the GTalk (with the different resources), lists only the Pidgin one, not the Empathy one. Maybe Empathy is not properly marking the account as online on that resource, so other clients think they can’t send to it?
If I understood the behavior correctly, you should see only one. If you set a different ‘resource’ name (one ‘pidgin’ and one ‘empathy’), you always have the same account, but you are using it with two different clients.
Yes, but I’m pretty sure you should be able to choose which resource to send to. In any case, logging out of that account in Pidgin so that Empathy should’ve been the only reference did not fix it.
Try to connect to the port 5223. I don’t have empathy here, but I fixed it in that way
We had same problem. Try to unmark “Use old SSL” in Advanced Options.