Description of problem:
When I try to login with my google talk account in Empathy, a red panel with a message appears. It's random between: "Network error" or "No reason specified".
Version-Release number of selected component (if applicable):
Just add a Gtalk account.
Steps to Reproduce:
1. Open Empathy
2. Add Gtalk account
Red panel with an error message.
Access to my Gtalk contacts and talk with them.
It worked yesterday...
They are this problem from a long time. I would like to know if a fix come soon ?
Well, there isn't much information available here to diagnosis what's wrong. I have back-ported some FB & Googletalk fixes (dealing with creating accounts) to Empathy that might solve this (obviously you'll need to delete the account & re-add it for the changes to be picked up). It's sitting in Bodhi right now waiting to be pushed to testing, if you want to try it.
The latest update I picked up from Koji didn't help for me.
Is there any way I can provide more information to help with the bug report?
I'm currently running:
What seems weird to me is that Jabber worked fine and then stopped and it's the case for both GoogleTalk and different Jabber server. Pidgin works fine with the same account data (sans its Gnome 3 integration).
(In reply to comment #3)
> Is there any way I can provide more information to help with the bug report?
After attempting to log-in with your Jabber/GoogleTalk accounts in Empathy, go to Help->Debug,and save a copy of your mission-control & gabble logs and attach them here. That should give upstream and me a better idea of what's causing your problem. Thanks!
Created attachment 514938 [details]
empathy log (facebook)
with latest empathy build from koji (x86_64) i have try for xmpp account all fail see attached file (in this example it is facebook account)
Created attachment 515089 [details]
(In reply to comment #5)
> Created attachment 514938 [details]
> empathy log (facebook)
> with latest empathy build from koji (x86_64) i have try for xmpp account all
> fail see attached file (in this example it is facebook account)
I'm attaching my log as well. To my uninitiated eye it looks like the same problem as Jonathan is seeing.
They are another bug to
In debug window if you select gabble dropdown at left, debug message still mission-control
For get gablle log you need take the old way:
$ GABBLE_DEBUG=all WOCKY_DEBUG=all GABBLE_PERSIST=1 /usr/libexec/telepathy-gabble
you can piping to a file for save log
The problem seem to be: gabble is trying to resolve empty strings so fails to connect
i have check server with:
$ host -t SRV _xmpp-client._tcp.jabber.fr
_xmpp-client._tcp.jabber.fr has SRV record 20 0 5222 im.apinc.org.
So it is good, is empathy bug around connection or gnome3 problem
the problem start here: gabble-DEBUG: connector_error_disconnect (connection.c:1673): connection failed: g-resolver-error-quark (#0): connection failed: Error resolving '': Name or service not known
Created attachment 515218 [details]
problem start line 271
if you are behind a proxy upstream works for a patch
else open dconf-editor:
-> mode = none
solved for me
Thanks, Jonathan, that did the trick for me. I wonder why the proxy was set in the first place..
same strange, maybe a old-update i use fedora-15 since alpha was released ...
So it will solve other problem with other gnome application like epiphany, pino ....
Have just had this same problem -- for some reason I had (F15, Gnome3) network settings -> proxy set to 'Auto' with the config URL blank.
Setting back to 'None' and the xmpp sessions restarted OK (MSN wasn't affected by this)
yes it was the problem i think, i have do same thing works for me
We can close the bug now
This message is a notice that Fedora 15 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 15. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. At this time, all open bugs with a Fedora 'version'
of '15' have been closed as WONTFIX.
(Please note: Our normal process is to give advanced warning of this
occurring, but we forgot to do that. A thousand apologies.)
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen
this bug and simply change the 'version' to a later Fedora version.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we were unable to fix it before Fedora 15 reached end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora, you are encouraged to click on
"Clone This Bug" (top right of this page) and open it against that
version of Fedora.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
The process we are following is described here: