Empathy can't connect to a Jabber account

Bug #361731 reported by Etienne Lepercq
52
This bug affects 9 people
Affects Status Importance Assigned to Milestone
Empathy
Invalid
Undecided
Unassigned
telepathy-gabble
Fix Released
High
telepathy-gabble (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

I tried using empathy to connect to my jabber account (I usually work with Gajim, and it works fine). My account parameters are correct, and using empathy with archlinux on another computer (same empathy release) works fine.

After setting BUTTERFLY_PERSIST to 1 and BUTTErFLY_DEBUG=all, here is what I get when trying to connect through telepathy-butterfly:

/usr/lib/python2.6/dist-packages/pymsn/util/weak.py:23: DeprecationWarning: the sets module is deprecated
  from sets import Set
/usr/lib/python2.6/dist-packages/pymsn/p2p.py:38: DeprecationWarning: the sha module is deprecated; use the hashlib module instead
  import sha
INFO:Butterfly.ConnectionManager:Connection manager created
INFO:Butterfly:No connection received - quitting
INFO:Butterfly.ConnectionManager:Connection manager quitting

By the way, a simple trick to get rid of the second warning (sha deprecated) is to use hashlib in /usr/lib/python2.6/dist-packages/pymsn/p2p.py line 38 and /usr/lib/python2.6/dist-packages/butterfly/avatars.py line 38, but this does not solve the problem.

It gets never connected. Using empathy (GUI) just provides one info : L'authentification a echoue (authentication failed translated into english)

Another thing interesting : once going back to gajim, I get an error saying that keyring has been badly configured (by empathy) : environment variable has been misconfigured.
The full message (in french) is available as a screenshot (see attachment).

Maybe this is more related to the connection between empathy and gnome-keyring ??
Finally, I am using an account with SSL connection, on port 5222 (I also tried 5223, with or without SSL, ... but SSL is in use with gajim).

Thank you.

Revision history for this message
Etienne Lepercq (e-guepe) wrote :
Revision history for this message
Etienne Lepercq (e-guepe) wrote :

This is a bug related to gnome-keyring : when connecting with debug output and using empathy

** (empathy:18186): WARNING **: couldn't connect to daemon at $GNOME_KEYRING_SOCKET: /tmp/keyring-jeN4bb/socket: Connexion refusée

** (empathy:18186): WARNING **: couldn't connect to daemon at $GNOME_KEYRING_SOCKET: /tmp/keyring-jeN4bb/socket: Connexion refusée

How could I specify the gnome-keyring-daemon that empathy is trusted ? I don't even have a popup asking for authorization !

Revision history for this message
Matej Moško (gnaag) wrote :

I have same problem (ubuntu jaunty AMD64). My account settings are good. Using same account I can connect through Pidgin, but empathy couldn't connect even if it got connection settings from pidgin. Interesting is that, if I connect to my jabber.org account, it goes well, but No way ho to connect to k2city.eu account. I have made new test account on the server, so If you want to, you can try, where the problem is

login: <email address hidden>
pass: password
server: mail.k2city.eu
port: 5222
no need to encryption

Revision history for this message
Etienne Lepercq (e-guepe) wrote :

Problem solved by update of the last three days :-) !

Revision history for this message
Olivier Le Thanh Duong (olethanh) wrote :

Telepathy-butterfly is the backend used to connect MSN (Windows Live) not Jabber. Reassigning the bug to the empathy package.

affects: telepathy-butterfly (Ubuntu) → empathy (Ubuntu)
Revision history for this message
Bernd Schlapsi (bernd-sch) wrote :

I installed empathy 2.27.2 through the launchpad ppa (https://launchpad.net/~telepathy/+archive/ppa) and imported my accounts from pidgin. But I couldn't connect to my jabber account.

So I debugged the connection process with the following instructions: http://live.gnome.org/Empathy/Debugging
I attach gabble.log and empathy.log to this bug. Please tell me if you need more information

Revision history for this message
Bernd Schlapsi (bernd-sch) wrote :

bernd@jaunty-gnome:~$ uname -a
Linux jaunty-gnome 2.6.28-11-generic #42-Ubuntu SMP Fri Apr 17 01:57:59 UTC 2009 i686 GNU/Linux

Revision history for this message
Bernd Schlapsi (bernd-sch) wrote :

this is the second log file

Revision history for this message
Oleksij Rempel (olerem) wrote :

I use karmic and same issue here.

Changed in empathy (Ubuntu):
importance: Undecided → Low
Revision history for this message
Oleksij Rempel (olerem) wrote :

Seems i do not understand the world.... Empathy accepted to replace pidgin in karmic, and basic function of this messenger do not working. How could some one set importance to low ?!

Revision history for this message
Bernd Schlapsi (bernd-sch) wrote :

>> Seems i do not understand the world.... Empathy accepted to replace pidgin in karmic, and basic function of this
>> messenger do not working. How could some one set importance to low ?!

Some opinion here!!!

@Pedro Villavicencio: Could you tell us why you think this bug isn't important? I think a connection the my jabber account is a basic function. Without this possibility empathy is useless for a lot of people and should not replace pidgin in karmic

Revision history for this message
Pedro Villavicencio (pedro) wrote :

raising the importance wouldn't make a difference, the report needs to be send upstream at bugzilla.gnome.org.

Changed in empathy (Ubuntu):
importance: Low → Medium
Revision history for this message
Vincenzo Ciancia (vincenzo-ml) wrote :

Raising the importance will certainly make a difference if the bug will be fixed upstream. In that case, having a high priority will probably mean someone will be interested in fixing it *before* a release. Pedro has 4090 bugs related to him, could somebody else report upstream? :)

Revision history for this message
Matej Moško (gnaag) wrote :

I have filed a bug at bugzilla.gnome.org. I am not quite sure if it is the upstream, you mentioned

http://bugzilla.gnome.org/show_bug.cgi?id=586770

Revision history for this message
Nicolas DERIVE (kalon33) wrote :

It is, thanks for the upstream reporting gnaag.

Revision history for this message
Anakin Starkiller (sunrider) wrote :

I can confirm this problem with the latest packages from PPA https://launchpad.net/~telepathy/+archive/ppa
But gtalk account works great though I have not tried video/audio yet.

Revision history for this message
Bernd Schlapsi (bernd-sch) wrote :

Today I tested my google jabber account and this seems to work. But empathy could not connect to my "linuxlover.at" account

Revision history for this message
Bernd Schlapsi (bernd-sch) wrote :

Today I updated my Ubuntu 9.04 with the latest packages from the Telepathy PPAs (https://launchpad.net/~telepathy/+archive/ppa). There was a new version of telepathy-gabble and now the connection with my jabber-account works.

Revision history for this message
Matej Moško (gnaag) wrote :

Problem still appearing after mentioned update

Revision history for this message
Falconix (falconix) wrote :

The update from PPA of Gabble version 0.7.30-1~ppa9.04+1 solved the connection issue for me, against ejabberd servers. So it seems that the problem is solved.

Iheb Ben amor (ihebfseg)
Changed in empathy (Ubuntu):
status: New → Confirmed
Revision history for this message
Sebastien Bacher (seb128) wrote :

could you confirm it's fixed in karmic?

Changed in empathy (Ubuntu):
status: Confirmed → Triaged
summary: - [Jaunty] Empathy can't connect to a Jabber account
+ Empathy can't connect to a Jabber account
Revision history for this message
Bernd Schlapsi (bernd-sch) wrote :

It works for me in karmic and in jaunty with the telepathy-paa.

Revision history for this message
Matej Moško (gnaag) wrote :

This bug is still on in my karmic beta with latest karmic updates. Still using the same test account <email address hidden> at server mail.k2city.eu with password "passwords" without quotes.

Revision history for this message
Oleksij Rempel (olerem) wrote : Re: [Bug 361731] Re: Empathy can't connect to a Jabber account

Try to remove old account and add new one. It helped me.

Revision history for this message
Matej Moško (gnaag) wrote :

Haven't helped. Tried to create new account and also delete and re-create old. No progress.

Revision history for this message
Anders Jackson (anders-jackson) wrote :

I have problem with empathy doesn't uses SRV DNS record from the jabber domain, which tells the Jabber client where the Jabber server is. If I set server under advanced in the setting window for the account, I can connect.

Are there any possibility to see what XML communication is going on between client and server i emapthy?

Revision history for this message
Falconix (falconix) wrote :

A Jackson : are you sure of that, so it isn't your DNS server which can't handle SRV-records, i have bad experience with FON routers and theirs DNS servers and SRV records. Try to change to an reliable DNS server.
otherwise try to use dig if you can resolve a SRV record
dig +short _xmpp-server._tcp.yourhost.com. SRV

Revision history for this message
John Gill (swfiua) wrote :

At the risk of being a 'me too', I'm using the Karmic release candidate and jabber accounts are still failing to authenticate.

With empathy as the default IM for Karmic, this bug would seem to be rather critical.

Revision history for this message
John Gill (swfiua) wrote :

An update on this for karmic.

I've done quite a bit of hacking around the last couple of days to try and get things working.

It seems the problem is the interaction between empathy, telepathy and the gnome keyrings.

Things worked fine for me when I set up a fresh account.

I then observed that my own account had two keyrings and wondered if that was the issue. Lots of hacking around, removing keyrings, .mission-control etc followed.

Eventually, I just deleted the lot and got a working system.

On my netbook I was also having problems. Deleting the existing jabber account and re-creating worked, but only when I chose "use existing account" as opposed to "create new".

I'm afraid up to now I haven't been able to create an easily reproducible way of generating the bug, but figured this report might a. help others get empathy working and b. point a developer in the right direction.

Revision history for this message
Thomas Kempis (kempis76) wrote :

Using Karmic here. Got the problem with Empathy in the desktop and netbook remix. I erased the configuration file in the home directory at /home/XXXX/.conf/Emphaty and reinstalled the program. Now everythig is working perfectly... have no idea why...

Revision history for this message
davenz (davekoelmeyer) wrote :

John Gills workaround of '"Deleting the existing jabber account and re-creating worked, but only when I chose "use existing account" as opposed to "create new'" worked for me, strangely enough.

Revision history for this message
Ihar Hrachyshka (ihar-hrachyshka) wrote :

Workaround in #31 helped me too.

Revision history for this message
Matej Moško (gnaag) wrote :

My jabber still does not work using telepathy-gabble version 0.8.11. The connection encounters several errors, but still goes on, the error that actually ends the connection is 407: Registration Required, in GUI it shows as authentication failed. I attach log and the mentioned excerpt of log

[code]
LM-DEBUG: 04.03.2010 13:31:15.244672: Have a new message
LM-DEBUG: 04.03.2010 13:31:15.244718: New message with type="stream:error" from: unknown
LM-DEBUG: 04.03.2010 13:31:15.244781: XMPP 1.0 stream received: 0315130431
LM-DEBUG: 04.03.2010 13:31:15.244870:
SEND:
LM-DEBUG: 04.03.2010 13:31:15.244920: -----------------------------------
LM-DEBUG: 04.03.2010 13:31:15.244966: <iq type="set" id="239619244844"> <bind xmlns="urn:ietf:params:xml:ns:xmpp-bind"> <resource>empathy</resource>
</bind>
</iq>
LM-DEBUG: 04.03.2010 13:31:15.245012: -----------------------------------
LM-DEBUG: 04.03.2010 13:31:15.245170: Stream features received
LM-DEBUG: 04.03.2010 13:31:15.245234:
SEND:
LM-DEBUG: 04.03.2010 13:31:15.245281: -----------------------------------
LM-DEBUG: 04.03.2010 13:31:15.245327: <auth mechanism="DIGEST-MD5" xmlns="urn:ietf:params:xml:ns:xmpp-sasl" id="239623245223"></auth>
LM-DEBUG: 04.03.2010 13:31:15.245374: -----------------------------------
LM-DEBUG: 04.03.2010 13:31:15.251959:
RECV [173]:
LM-DEBUG: 04.03.2010 13:31:15.252065: -----------------------------------
LM-DEBUG: 04.03.2010 13:31:15.252116: '<iq id="239619244844" type="error"> <bind xmlns="urn:ietf:params:xml:ns:xmpp-bind"> <resource>empathy</resource>
</bind>
<error code="407">Registration Required</error></iq>'
LM-DEBUG: 04.03.2010 13:31:15.252166: -----------------------------------
LM-DEBUG: 04.03.2010 13:31:15.253371: Read: 173 chars
LM-DEBUG: 04.03.2010 13:31:15.253439: ATTRIBUTE: id = 239619244844
LM-DEBUG: 04.03.2010 13:31:15.253499: ATTRIBUTE: type = error
LM-DEBUG: 04.03.2010 13:31:15.253551: ATTRIBUTE: xmlns = urn:ietf:params:xml:ns:xmpp-bind
LM-DEBUG: 04.03.2010 13:31:15.253602: Trying to close node: resource
LM-DEBUG: 04.03.2010 13:31:15.253649: Trying to close node: bind
LM-DEBUG: 04.03.2010 13:31:15.253700: ATTRIBUTE: code = 407
LM-DEBUG: 04.03.2010 13:31:15.253747: Trying to close node: error
LM-DEBUG: 04.03.2010 13:31:15.253797: Trying to close node: iq
LM-DEBUG: 04.03.2010 13:31:15.253859: Have a new message
LM-DEBUG: 04.03.2010 13:31:15.253909: New message with type="iq" from: unknown
LM-DEBUG: 04.03.2010 13:31:15.253984: connection_bind_reply: error while binding to resource
gabble/connection-DEBUG: 04.03.2010 13:31:15.254038: connection_auth_cb: failed
[/code]

Revision history for this message
Omer Akram (om26er) wrote :

@Matej Moško can you please try to install the development release of empathy and see if that solves the problem for you.
sudo add-apt-repository ppa:telepathy/ppa ;sudo apt-get update ;sudo apt-get dist-upgrade and then reboot.

Changed in empathy (Ubuntu):
status: Triaged → Incomplete
Revision history for this message
Matej Moško (gnaag) wrote :

My fault, should mention, I already run development version of empathy. Moreover I have already tried 0.9.6 version of telepathy-gabble. Telepathy-haze do not get over wrong certificate.

Revision history for this message
Omer Akram (om26er) wrote :

Can you please reply to the last comment upstream

Changed in empathy (Ubuntu):
status: Incomplete → Triaged
Revision history for this message
Matej Moško (gnaag) wrote :

I am sorry, I don't understand

Revision history for this message
Omer Akram (om26er) wrote :

The bug report that you opened at bugzilla they requested some information
can you please provide them the requested information.

2010/3/4 Matej Moško <email address hidden>

> I am sorry, I don't understand
>
> --
> Empathy can't connect to a Jabber account
> https://bugs.launchpad.net/bugs/361731
> You received this bug notification because you are subscribed to empathy
> in ubuntu.
>
> Status in Chat app, and Telepathy user interface: Unknown
> Status in “empathy” package in Ubuntu: Triaged
>
> Bug description:
> I tried using empathy to connect to my jabber account (I usually work with
> Gajim, and it works fine). My account parameters are correct, and using
> empathy with archlinux on another computer (same empathy release) works
> fine.
>
> After setting BUTTERFLY_PERSIST to 1 and BUTTErFLY_DEBUG=all, here is what
> I get when trying to connect through telepathy-butterfly:
>
>
> /usr/lib/python2.6/dist-packages/pymsn/util/weak.py:23: DeprecationWarning:
> the sets module is deprecated
> from sets import Set
> /usr/lib/python2.6/dist-packages/pymsn/p2p.py:38: DeprecationWarning: the
> sha module is deprecated; use the hashlib module instead
> import sha
> INFO:Butterfly.ConnectionManager:Connection manager created
> INFO:Butterfly:No connection received - quitting
> INFO:Butterfly.ConnectionManager:Connection manager quitting
>
>
> By the way, a simple trick to get rid of the second warning (sha
> deprecated) is to use hashlib in
> /usr/lib/python2.6/dist-packages/pymsn/p2p.py line 38 and
> /usr/lib/python2.6/dist-packages/butterfly/avatars.py line 38, but this does
> not solve the problem.
>
> It gets never connected. Using empathy (GUI) just provides one info :
> L'authentification a echoue (authentication failed translated into english)
>
> Another thing interesting : once going back to gajim, I get an error saying
> that keyring has been badly configured (by empathy) : environment variable
> has been misconfigured.
> The full message (in french) is available as a screenshot (see attachment).
>
> Maybe this is more related to the connection between empathy and
> gnome-keyring ??
> Finally, I am using an account with SSL connection, on port 5222 (I also
> tried 5223, with or without SSL, ... but SSL is in use with gajim).
>
> Thank you.
>
>
>

Revision history for this message
Matej Moško (gnaag) wrote :

thank you, info posted to upstream, I am still a bit confused about the bug reporting terminology.

Revision history for this message
In , Matej Moško (gnaag) wrote :

My jabber account at k2city.eu still does not work using telepathy-gabble version 0.8.11 (I havetried 0.9.6, no success, but not quite sure if the same error). The connection encounters several errors, but still goes on, the error that actually ends the connection in debug is 407: Registration Required, in GUI it shows as authentication failed. I attach log and the mentioned excerpt of log

When trying to set up a connection through telepathy-haze, it cannot get through certificate, while certificate is self-signed and empathy doesn't have certificate managing for telepathy-haze

You can test it with account:
login: test(at)k2city.eu
pass: password
server: mail.k2city.eu
port: 5222

[code]
LM-DEBUG: 04.03.2010 13:31:15.244672: Have a new message
LM-DEBUG: 04.03.2010 13:31:15.244718: New message with type="stream:error"
from: unknown
LM-DEBUG: 04.03.2010 13:31:15.244781: XMPP 1.0 stream received: 0315130431
LM-DEBUG: 04.03.2010 13:31:15.244870:
SEND:
LM-DEBUG: 04.03.2010 13:31:15.244920: -----------------------------------
LM-DEBUG: 04.03.2010 13:31:15.244966: <iq type="set" id="239619244844"> <bind
xmlns="urn:ietf:params:xml:ns:xmpp-bind"> <resource>empathy</resource>
</bind>
</iq>
LM-DEBUG: 04.03.2010 13:31:15.245012: -----------------------------------
LM-DEBUG: 04.03.2010 13:31:15.245170: Stream features received
LM-DEBUG: 04.03.2010 13:31:15.245234:
SEND:
LM-DEBUG: 04.03.2010 13:31:15.245281: -----------------------------------
LM-DEBUG: 04.03.2010 13:31:15.245327: <auth mechanism="DIGEST-MD5"
xmlns="urn:ietf:params:xml:ns:xmpp-sasl" id="239623245223"></auth>
LM-DEBUG: 04.03.2010 13:31:15.245374: -----------------------------------
LM-DEBUG: 04.03.2010 13:31:15.251959:
RECV [173]:
LM-DEBUG: 04.03.2010 13:31:15.252065: -----------------------------------
LM-DEBUG: 04.03.2010 13:31:15.252116: '<iq id="239619244844" type="error">
<bind xmlns="urn:ietf:params:xml:ns:xmpp-bind"> <resource>empathy</resource>
</bind>
<error code="407">Registration Required</error></iq>'
LM-DEBUG: 04.03.2010 13:31:15.252166: -----------------------------------
LM-DEBUG: 04.03.2010 13:31:15.253371: Read: 173 chars
LM-DEBUG: 04.03.2010 13:31:15.253439: ATTRIBUTE: id = 239619244844
LM-DEBUG: 04.03.2010 13:31:15.253499: ATTRIBUTE: type = error
LM-DEBUG: 04.03.2010 13:31:15.253551: ATTRIBUTE: xmlns =
urn:ietf:params:xml:ns:xmpp-bind
LM-DEBUG: 04.03.2010 13:31:15.253602: Trying to close node: resource
LM-DEBUG: 04.03.2010 13:31:15.253649: Trying to close node: bind
LM-DEBUG: 04.03.2010 13:31:15.253700: ATTRIBUTE: code = 407
LM-DEBUG: 04.03.2010 13:31:15.253747: Trying to close node: error
LM-DEBUG: 04.03.2010 13:31:15.253797: Trying to close node: iq
LM-DEBUG: 04.03.2010 13:31:15.253859: Have a new message
LM-DEBUG: 04.03.2010 13:31:15.253909: New message with type="iq" from: unknown
LM-DEBUG: 04.03.2010 13:31:15.253984: connection_bind_reply: error while
binding to resource
gabble/connection-DEBUG: 04.03.2010 13:31:15.254038: connection_auth_cb: failed
[/code]

Revision history for this message
Omer Akram (om26er) wrote :

Marking this incomplete as upstream bug report suggests this bug should be reported agains telepathy-gabble. The version og gabble in Lucid is 0.8.12 If any one still face this bug with the latest gabble I will open an upstream gabble bug report or If you have the time please open yourself :)

Changed in empathy (Ubuntu):
status: Triaged → Incomplete
Changed in empathy:
importance: Unknown → Undecided
status: Unknown → New
status: New → Invalid
Omer Akram (om26er)
affects: empathy (Ubuntu) → telepathy-gabble (Ubuntu)
Revision history for this message
Matej Moško (gnaag) wrote :
Changed in telepathy-gabble:
importance: Undecided → Unknown
status: New → Unknown
Revision history for this message
Omer Akram (om26er) wrote :

Thanks for sending this upstream. I have subscribed myself to the upstream bug report.

Changed in telepathy-gabble (Ubuntu):
status: Incomplete → Triaged
Changed in telepathy-gabble:
status: Unknown → Confirmed
Revision history for this message
David Robert Lewis (afrodeity) wrote :

I'm on karmic and suspect telepathy-gabble is outdated. Do I need to add the ppa to get any fixes? Why no official updates?

Revision history for this message
Philipp Reinkemeier (philipp-reinkemeier) wrote :

Hi there. I had the same problem about empathy throwing an error at me "authentication failed". Fortunately
this seems to be fixed in version 0.9.11, although the devs still did not comment on https://bugs.freedesktop.org/show_bug.cgi?id=27095. At least for me this issue disappeared since i use that new version.

Revision history for this message
In , Matej Moško (gnaag) wrote :

After upgrade to telepathy-gabble 0.9.11 I have been finally able to connect to my k2city.eu account. Thanks a lot

Revision history for this message
Matej Moško (gnaag) wrote :

Thanks a lot. After upgrade to 0.9.11 I am eventualy able to connect to my k2city.eu account

Revision history for this message
Andrey Andreev (andreev00) wrote :

Upgrading of telepathy-gabble to 0.9.11 (and its dependencies) from the telepathy's ppa solved the problem.

Revision history for this message
Prunus dulcis (prunus-dulcis) wrote :

For me upgrading using the ppa solved this problem as well. But I had to dig for this 20 minutes today. If it is easily fixed, that would be highly welcome :)

Changed in telepathy-gabble:
importance: Unknown → High
status: Confirmed → Fix Released
Revision history for this message
Omer Akram (om26er) wrote :

this bug has been fixed in telepathy 0.10 if anyone still faces any problems please open a new bug report.

Changed in telepathy-gabble (Ubuntu):
status: Triaged → Fix Released
Changed in telepathy-gabble:
importance: High → Unknown
Changed in telepathy-gabble:
importance: Unknown → High
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.