I am unable to receive messages in Empathy on GTalk with any version of telepathy higher than 0.7.15. They can receive messages just fine from me, but with every release since then, including 0.7.26, I get nothing. No error messages are given. I tried twiddling every knob in the account dialog in different combinations, but to no effect.
Which client are using your gtalk contacts? The web one or the desktop one?
Similar Empathy bug report: http://bugzilla.gnome.org/show_bug.cgi?id=579469
The contacts I'm talking to are using a variety of clients - the gtalk web client, Pidgin, possibly others too. The problem ocurrs with all of them.
Could you attach Gabble's debug output? There are instructions on <http://live.gnome.org/Empathy/Debugging>.
In order to provide debug output, I created a new Google account (in order to have less contact-related cruft in the log file). I was surprised to discover that the issue did not occur with this new account! I tried deleting my account settings (by removing /apps/telepathy in gconf) and re-adding my original account, but ran into the same issue of not being able to receive messages. Strangely, the new account never runs into this issue.
Created attachment 25310 [details] Empathy log when using telepathy-gabble 0.7.26
Created attachment 25311 [details] telepathy-gabble 0.7.26 log
Created attachment 25312 [details] mission-control log using telepathy-gabble 0.7.26
I experienced the same thing as Martey when I created a new account to test with. Anyway, I have attached my logs (finally), per the request.
I am experiencing the same problem with telepathy-gabble 0.7.27 on ubuntu, other protocols are fine, just jabber is a problem. We are considering switching from pidgin to empathy for Karmic, assuming we can get enough of these bugs sorted out.
Thanks. This is a Loudmouth bug: ** (telepathy-gabble:4707): WARNING **: Couldn't create message: ns2:iq One of your contacts is using a Blackberry. Their XMPP client sends valid but unusual XML, and Loudmouth chokes and falls down a well...
So should this bug be moved to loudmouth?
There's already a loudmouth bug...
Complete with a patch to at least not totally break. Maybe distros should apply that patch in the meantime?
This is not our bug. Also, this should work in the 0.9 branch, where we no longer use Loudmouth.
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.