"Disconnected -- no reason specified" when adding GTalk/Jabber account

[Eddie Ringle]

Binary package hint: empathy

When I try to add my google talk account to empathy (or add it as a jabber account with the server settings set to google's server), it says "Disconnected -- no reason specified". The following was outputted to stdout:

    (empathy:6403): TelepathyBackend-WARNING **: tpf-persona-store.vala:818: failed to add channel 'stored': Unable to complete this channel request, we're disconnecting!

    (empathy:6403): TelepathyBackend-WARNING **: tpf-persona-store.vala:818: failed to add channel 'publish': Unable to complete this channel request, we're disconnecting!

    (empathy:6403): TelepathyBackend-WARNING **: tpf-persona-store.vala:818: failed to add channel 'subscribe': Unable to complete this channel request, we're disconnecting!

This renders empathy completely useless. And no, I haven't tried adding an account using a different service (GTalk is pretty much the only one I use nowadays).

[Pedro Villavicencio (pedro)]

Thanks for the report, with which version of empathy/telepathy are you getting those?

[Eddie Ringle (eddie.ringle)]

Sorry about that, my desktop is running Maverick (so whichever version of empathy is in the Maverick repos right now, I'm away so I can't check).

[Mohamed Amine Ilidrissi (ilidrissi.amine)]

Sorry, but I can't seem to be able to reproduce this issue ; My GTalk account is able to connect automatically. Can you test using another account?

[Eddie Ringle (eddie.ringle)]

My Google Apps account is able to connect successfully and the status is set as "Available". Now when I try my GMail account, it shows "Available" for a split second and then returns to "Disconnected -- no reason specified".

[Omer Akram (om26er)]

please attach telepathy-gabble logs from Help>debug there select gabble and click on the save button and attach the text file to this bug report. the log file should be of the time when the problem actually happens.

[Chris Brunner (chris-brunner)]

I'm having exactly the same issue.

[Dave Morley (davmor2)]

Can you check in the accounts window if under advanced the server details are in place. It should read Server: talk.google.com if it doesn't that is the issue I have.

[Eddie Ringle (eddie.ringle)]

No, all the settings are correct (and as they are provided by Empathy). This occurs on a fresh install of 10.10 as well.

[Keechang Kim (keechang)]

I also encountered this problem. I had been using Gtalk with Empathy without problem until yesterday. For no reason, it keeps disconnecting and retries and disconnects again.

[Omer Akram (om26er)]

the original bug is fixed in maverick. if someone else faces this problem please open a new bug and attach telepathy-gabble logs there.

[Eddie Ringle (eddie.ringle)]

If it's fixed, then I should be able to connect. I've updated to stable 10.10, so I _should_ have the fix, right?

Also, I find it silly to open up a new issue for the same problem.

[Adam Bregenzer (adam-bregenzer)]

I am having the same issue - I enter my google talk credentials, and whether I enter the server name or leave it blank, check old ssl or leave it blank, or check encryption required or leave it blank I get the same results: it connects, shows available for a second, then disconnects with a "no reason specified" error. I have tried every combination of those settings with no luck. I am attaching a screenshot of the settings screen and will floow up with a log file.

[Adam Bregenzer (adam-bregenzer)]

Here is a copy of my logs for gabble while trying to connect to google chat.

[Funnnny (ntcong-it)]

Did a fresh install of maverick, the problem still here.
When I add an gtalk account in Empathy, in the Advance section, nothing pre-configured here

[Michael Hill (mhill-linux)]

Issue effects me as well on a fresh maverick install. Gtalk will not connect, 'Reason not specified'. I open up pidgin and put my credentials in there and it connects with no problem. This also affects fb chat. I'm sitting here watching both gtalk and fb chat connect then immediately disconnect, then a few seconds later attempt to connect and on and on. Going to use pidgin till this is fixed.

[Funnnny (ntcong-it)]

Why the importance is marking as Low, the bug affect the usabilty of the application.

[Michael Nischt (mosaic-school)]

I didn't have any problems connecting since a week.. is it fixed?

[William Jones (junkmail1-stuffedgiraffe)]

Nope. The issue still persists for me. It's very disappointing that this issue doesn't seem to be getting much attention.

[Robert Siemer (robert-siemer-launchpad-net)]

I had exactly the same problem. Maverick here. Workaround was to install telepathy-gabble from natty, it is version 0.11.0-1

...so, XMPP running again, leaves only QQ, MSN and ICQ broken...

[Andrew Moss (andrewmoss)]

This problem didn't affect me originally - some update that I downloaded over the past week started it. I'm using Empathy 2.32.0.1 on Meerkat. The application is completely useless in its current state. I've trimmed the log to a single failed connect attempt, if you need more information to replicate it then please ask.

[Robert Siemer (robert-siemer-launchpad-net)]

Did I say I use telepathy-gabble 0.11.0-1 without problem? Andrew, do you mind doing the same? I also have empathy 2.32.1-0ubuntu2; something similar is in maverick-proposed.

I have something like this in /etc/apt/sources.list.d/natty.list

deb http://ubuntu.cn99.com/ubuntu/ natty restricted universe multiverse main
deb http://ubuntu.cn99.com/ubuntu/ natty-backports restricted universe multiverse main
deb http://ubuntu.cn99.com/ubuntu/ natty-proposed restricted universe multiverse main
deb http://ubuntu.cn99.com/ubuntu/ natty-security restricted universe multiverse main
deb http://ubuntu.cn99.com/ubuntu/ natty-updates restricted universe multiverse main

and in /etc/apt/preferences

Explanation: next generation (maybe there was no codename given (well, not always)!?)
Package: *
Pin: release v=11.04
Pin-Priority: 120

...that makes it comfortable to get packages from natty to try with, without upgrading everything to it.

[Andrew Moss (andrewmoss)]

Sorry Robert but this is a production box in a work environment and so I can't enable packages from another repository on it.

[Andrew Moss (andrewmoss)]

Nothing has changed here either configuration-wise or with versions (all updates are scheduled manually) - but I am now connected to gtalk again. I've attached the log again but there isn't anything helpful in there - it magically starts to work at about 2am 11/29/2010. Looks like Google changed their configuration. Does it now work for everyone else?

[Andrew Moss (andrewmoss)]

And it broke again at 11am this morning....

[Robert Siemer (robert-siemer-launchpad-net)]

What do you mean with “production box in a work environment and so I can't enable packages from another repository”, Andrew?

In which repository do you want the fix to end up? In maverick? Never will. In maverick-updates? I wish you good luck finding someone who is willing to fish the relevant change out of telepathy-gabble 0.11.0, with people like you around not even willing to test a single development package of a bug they don’t like. Or in maverick-proposed? Same as maverick-updates. -- Leaves only maverick-backports... But I see it pretty impossible you got that one enabled on your “production box in a work environment with gtalk for entertainment”.

By the way, maverick-backports would end up with pretty much the same telepathy-gabble 0.11.0, which is in natty now. -- But if you wish to see it there: request a backport for it at the proper place, not here.

https://help.ubuntu.com/community/UbuntuBackports

[Andrew Moss (andrewmoss)]

Oh dear Robert. Shall I explain slowly?

This box is used in a production setting - I cannot risk disabling it as work will grind to a halt. I am well aware that there is a good probability that enabling the repository you suggest will work. But a good probability is not a risk I can take on this box. Even if some wild fluky outside event causes it to stop working then the place that I work will be shafted.

I don't need a lecture from you on why "people like me" are holding back bug detection and resolution. But this box is on the default maverick repository. Hard to believe, but maybe someone shouldn't have broken the package in the first place.

I am sure that of the 50+ people watching this buglist you will find somebody willing to change their repository and test your fix for the problem. But you don't have any moral authority to criticize somebody who is unwilling to be that test subject because if they do screw their box up - "it's a production box in a work environment".

Perhaps your confusion on the issue arises because you think gtalk is an entertainment tool. Here's a wild idea - perhaps there are people who use gtalk as a tool in their work. Shocking isn't it to think that people may actively collaborate with their colleague in different parts of the world! And of course, although it is annoying that empathy is shafted I will continue to keep a gmail tab open in a browser until the fix does make it into the stable repository, however long that way be.

[Funnnny (ntcong-it)]

For conclusion, we're just reporting bugs, and yes it's a bug, it's confirmed and it's affect the main feature of empathy.
Maybe the bug was fixed upstream, or in a later version that didn't appear in official repo, yes, who cares ?, we're reporting so that developer know the current version in maverick has a bug, and they have to fix it. Not all users have ability to enable extra repo, so a official fix is required

[Robert Siemer (robert-siemer-launchpad-net)]

No, the confusion does not arise from me thinking gtalk is for entertainment only.

The confusion arises from the fact that the standard maverick repository will never get updated. So you can wait there for a fix until you turn black.

And let me make that clear: I suggested some packages from (any) natty repository, namely telepathy-gabble 0.11.0 and dependencies; and that is not my fix. -- Tell me, what kind of risk do you expect from these almost empathy specific packages, that can not be caught by simply downgrading again to the maverick versions? -- Come on, don’t tell me your work really relies on that empathy thing running at 100% (it never really did so far for me... :-)

In case you do also draw from maverick-updates (you didn’t answer my question clearly), I really wish you luck (as I stated before) to find someone of the 50+ people here to push that through the “Stable Release Update” process for you.

I personally believe that natty will be out quicker with the packages I refer to like they are now. But I may be wrong.

[Andrew Moss (andrewmoss)]

I don't what risk to expect from updating gabble and the libraries that it depends on - which is my point. On this box I cannot do anything that risks an application unexpectedly dying because I've upgraded one of its libraries.

You may well be right that it will never make into the standard maverick repository - I can live with that. As I said I'm using gmail in a browser tab until it is fixed. But I've never pushed or demanded a quick fix - I only posted to the buglist to add some information in case it was helpful.

In about three weeks this box will cease to be of vital importance at which point I'll probably pull an update from natty to see if it works. There may be someone else on this list who has more flexibility and could test it sooner.

[skalka (skalka)]

I have the same error on my Empathy (2.32.0.1). The strange thing is that I use 3 Gmail accounts at the same time and only one doesn't work. Can I help you in some way?

[Robert Siemer (robert-siemer-launchpad-net)]

I downgraded my empathy(-common) and telepathy-gabble to maverick(-updates). The former two are now 2.32.0.1 again and I have currently no problems connecting to gtalk.

skalka, maybe the third account of yours starts working again with versions from the natty repository. Maybe not.

[skalka (skalka)]

Downgrading doesn't work for me.

[Robert Siemer (robert-siemer-launchpad-net)]

Skalka, what do _you_ mean with “downgrading”, and what with “doesn’t work”?

[Robert Siemer (robert-siemer-launchpad-net)]

Good news everyone: downgrading does work!

Running telepathy-gabble on the maverick version (0.10.0-1) turned my gtalk into unconnected “No reason specified” after some hours. Downgrading to the lucid version (0.8.12-0ubuntu1) turned it back on again. I repeated the test two times. I will leave it on lucid for a while and report if it breaks.

Andrew, if you consider supported (maverick) + supported LTS (lucid) = supported, give it a shot.

I have empathy and empathy-common on 2.32.0.1-0ubuntu1 (maverick-updates).

[Robert Siemer (robert-siemer-launchpad-net)]

I was running lucid’s telepathy-gabble without problems the last days.

Today I updated empathy and empathy-common to the latest maverick-updates and tried telepathy-gabble from maverick again. Broken.

I just now moved telepathy-gabble to the natty version and login works again. -- I will stay with natty for that piece of software now.

Thanks for listening.

[baske (mobacke)]

Problem exist for me as well. Using Empathy 2.32.1 and Maverick. I can sign in on only one of my two google accounts.. This is really strange to me how the bug can exist for only certain accounts.. Seems almost like the problem is at google??

Any progress made in this issue?

Thanks

[Omer Akram (om26er)]

thanks everybody for commenting in this bug report and sorry for the inconvenience of gtalk/jabber not working. but the title that this bug report have, made everyone seeing the same error think if the underlying issue is the same. empathy gives network error so many different reasons and it is not possible for us to identify who is facing which issue. so if you are facing any such issue still in ubuntu 10.10 please open a new bug report for empathy and also attach your telepathy-gabble logs to that bug report (you can get those logs from the empathy debug window). we are again sorry for the inconvenience.

[Robert Siemer (robert-siemer-launchpad-net)]

Omer, your comment is one of the worst I’ve read so far, BECAUSE it reads like:

“bla bla bla, please open a new bug with the same stuff as here, thanks”

Apart from that, you mentioned:
-title of the bug report is bad
+please propose a better one, the actual problem is another bug by itself: a stupid error message from empathy, please open a bug report yourself to fix _that_ bug (a better message would be: “disconnected (unfortunately the telepathy-gabble connection manager did not specify a reason!)”)

-Is it still buggy in 10.10?
+Yes it is. I can reproduce the problem.

-please attach a log
+I‘ve seen those attached

-you marked the bug “won’t fix”
+actually, the bug itself is fixed in newer (and older!) telepathy-gabble

[Omer Akram (om26er)]

Robert, actually you are not even the original reporter of the bug and since
i believe the only person that could have argued would be the original
reporter. there is a downside of empathy error system. it gives same
messages for so many different reasons and keeping such bug reports without
any useful logs means no good for anyone. its a good thing the bug is fixed
for you so rant somewhere else.

On Thu, Jan 13, 2011 at 11:59 AM, Robert Siemer <Robert.Siemer-launchpad.net
@backsla.sh> wrote:

> Omer, your comment is one of the worst I’ve read so far, BECAUSE it
> reads like:
>
> “bla bla bla, please open a new bug with the same stuff as here, thanks”
>
> Apart from that, you mentioned:
> -title of the bug report is bad
> +please propose a better one, the actual problem is another bug by itself:
> a stupid error message from empathy, please open a bug report yourself to
> fix _that_ bug (a better message would be: “disconnected (unfortunately the
> telepathy-gabble connection manager did not specify a reason!)”)
>
> -Is it still buggy in 10.10?
> +Yes it is. I can reproduce the problem.
>
> -please attach a log
> +I‘ve seen those attached
>
> -you marked the bug “won’t fix”
> +actually, the bug itself is fixed in newer (and older!) telepathy-gabble
>
> --
> You received this bug notification because you are subscribed to empathy
> in ubuntu.
> https://bugs.launchpad.net/bugs/620654
>
> Title:
> "Disconnected -- no reason specified" when adding GTalk/Jabber account
>
> Status in “empathy” package in Ubuntu:
> Won't Fix
>
> Bug description:
> Binary package hint: empathy
>
> When I try to add my google talk account to empathy (or add it as a
> jabber account with the server settings set to google's server), it
> says "Disconnected -- no reason specified". The following was
> outputted to stdout:
>
> (empathy:6403): TelepathyBackend-WARNING **:
> tpf-persona-store.vala:818: failed to add channel 'stored': Unable to
> complete this channel request, we're disconnecting!
>
> (empathy:6403): TelepathyBackend-WARNING **:
> tpf-persona-store.vala:818: failed to add channel 'publish': Unable to
> complete this channel request, we're disconnecting!
>
> (empathy:6403): TelepathyBackend-WARNING **:
> tpf-persona-store.vala:818: failed to add channel 'subscribe': Unable to
> complete this channel request, we're disconnecting!
>
> This renders empathy completely useless. And no, I haven't tried
> adding an account using a different service (GTalk is pretty much the
> only one I use nowadays).
>
>
>

[skalka (skalka)]

Fix it or not, fight if you want, I still have this bug on my empathy and it's not nice.

[Omer Akram (om26er)]

attach your gabble logs please

On Tue, Jan 18, 2011 at 12:52 PM, skalka <email address hidden> wrote:

> Fix it or not, fight if you want, I still have this bug on my empathy
> and it's not nice.
>
> --
> You received this bug notification because you are subscribed to empathy
> in ubuntu.
> https://bugs.launchpad.net/bugs/620654
>
> Title:
> "Disconnected -- no reason specified" when adding GTalk/Jabber account
>
> Status in “empathy” package in Ubuntu:
> Won't Fix
>
> Bug description:
> Binary package hint: empathy
>
> When I try to add my google talk account to empathy (or add it as a
> jabber account with the server settings set to google's server), it
> says "Disconnected -- no reason specified". The following was
> outputted to stdout:
>
> (empathy:6403): TelepathyBackend-WARNING **:
> tpf-persona-store.vala:818: failed to add channel 'stored': Unable to
> complete this channel request, we're disconnecting!
>
> (empathy:6403): TelepathyBackend-WARNING **:
> tpf-persona-store.vala:818: failed to add channel 'publish': Unable to
> complete this channel request, we're disconnecting!
>
> (empathy:6403): TelepathyBackend-WARNING **:
> tpf-persona-store.vala:818: failed to add channel 'subscribe': Unable to
> complete this channel request, we're disconnecting!
>
> This renders empathy completely useless. And no, I haven't tried
> adding an account using a different service (GTalk is pretty much the
> only one I use nowadays).
>
>
>

[skalka (skalka)]

Here's gabble log.

[Omer Akram (om26er)]

skalka, reported your bug in telepathy bug tracker here
https://bugs.freedesktop.org/show_bug.cgi?id=33248 would be really helpful
if you open a telepathy gabble bug in launchpad too so that we could link
your issue.

On Tue, Jan 18, 2011 at 9:07 PM, skalka <email address hidden> wrote:

> Here's gabble log.
>
> ** Attachment added: "gabble (jabber)-18-01-11_11-03-54.log"
>
> https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/620654/+attachment/1798144/+files/gabble%20%28jabber%29-18-01-11_11-03-54.log
>
> --
> You received this bug notification because you are subscribed to empathy
> in ubuntu.
> https://bugs.launchpad.net/bugs/620654
>
> Title:
> "Disconnected -- no reason specified" when adding GTalk/Jabber account
>
> Status in “empathy” package in Ubuntu:
> Won't Fix
>
> Bug description:
> Binary package hint: empathy
>
> When I try to add my google talk account to empathy (or add it as a
> jabber account with the server settings set to google's server), it
> says "Disconnected -- no reason specified". The following was
> outputted to stdout:
>
> (empathy:6403): TelepathyBackend-WARNING **:
> tpf-persona-store.vala:818: failed to add channel 'stored': Unable to
> complete this channel request, we're disconnecting!
>
> (empathy:6403): TelepathyBackend-WARNING **:
> tpf-persona-store.vala:818: failed to add channel 'publish': Unable to
> complete this channel request, we're disconnecting!
>
> (empathy:6403): TelepathyBackend-WARNING **:
> tpf-persona-store.vala:818: failed to add channel 'subscribe': Unable to
> complete this channel request, we're disconnecting!
>
> This renders empathy completely useless. And no, I haven't tried
> adding an account using a different service (GTalk is pretty much the
> only one I use nowadays).
>
>
>

[Mariano Stampella (mstampella)]

This is a really disappointing thread. First im one of the
creators and owners of www.dynamicjasper.com and i know exactly how it
feel mantain an open source project.

My company using empathy to work and for us is a critical tool because we using
Gtalk to interact with jenna (www.jennatimetracker.com) our sexy
assistant who ask us about, hours, knowledge and status...and this is
really important for us.

All the company use Ubuntu to work, so...empathy is really relevant,
obviously we can use another option (and we will) but sounds really
disappointing the no relevance of this issue, and the no solutions

[Omer Akram (om26er)]

Mariano, reporting a new bug report with your logs would be very helpful
since this error message is for so many different issues that can happen in
empathy.

On Fri, Mar 4, 2011 at 8:57 PM, Mariano Stampella <<email address hidden>
> wrote:

> This is a really disappointing thread. First im one of the
> creators and owners of www.dynamicjasper.com and i know exactly how it
> feel mantain an open source project.
>
> My company using empathy to work and for us is a critical tool because we
> using
> Gtalk to interact with jenna (www.jennatimetracker.com) our sexy
> assistant who ask us about, hours, knowledge and status...and this is
> really important for us.
>
> All the company use Ubuntu to work, so...empathy is really relevant,
> obviously we can use another option (and we will) but sounds really
> disappointing the no relevance of this issue, and the no solutions
>
> --
> You received this bug notification because you are subscribed to empathy
> in ubuntu.
> https://bugs.launchpad.net/bugs/620654
>
> Title:
> "Disconnected -- no reason specified" when adding GTalk/Jabber account
>
> Status in “empathy” package in Ubuntu:
> Won't Fix
>
> Bug description:
> Binary package hint: empathy
>
> When I try to add my google talk account to empathy (or add it as a
> jabber account with the server settings set to google's server), it
> says "Disconnected -- no reason specified". The following was
> outputted to stdout:
>
> (empathy:6403): TelepathyBackend-WARNING **:
> tpf-persona-store.vala:818: failed to add channel 'stored': Unable to
> complete this channel request, we're disconnecting!
>
> (empathy:6403): TelepathyBackend-WARNING **:
> tpf-persona-store.vala:818: failed to add channel 'publish': Unable to
> complete this channel request, we're disconnecting!
>
> (empathy:6403): TelepathyBackend-WARNING **:
> tpf-persona-store.vala:818: failed to add channel 'subscribe': Unable to
> complete this channel request, we're disconnecting!
>
> This renders empathy completely useless. And no, I haven't tried
> adding an account using a different service (GTalk is pretty much the
> only one I use nowadays).
>