0.5.1 fixes this. Thanks!
** Changed in: telepathy-gabble (Ubuntu)
Status: Fix Committed = Fix Released
--
Connect() failed
https://launchpad.net/bugs/75842
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Fixed upstream.
** Changed in: gossip-telepathy (Ubuntu)
Sourcepackagename: gossip-telepathy = telepathy-gabble
Status: Unconfirmed = Fix Committed
--
Connect() failed
https://launchpad.net/bugs/75842
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
yes, you should try with current development version, or wait for a
release packaged into feisty.
--
Connect() failed
https://launchpad.net/bugs/75842
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
No the fact that error messages reported to the user are not very clear
and often errors are not reported at all...
** (gossip:5680): WARNING **: Connect() failed: Message did not receive
a reply (timeout by message bus)
Now I know a little more about this message. The cause is gabble crashed
I have telepathy-gabble 0.5.0-0ubuntu1; do you mean a newer version?
--
Connect() failed
https://launchpad.net/bugs/75842
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Did you set the server to talk.google.com, ssl enabled and port 5223 ?
--
Connect() failed
https://launchpad.net/bugs/75842
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
for gtalk on gabble use:
server: talk.google.com
use encryption (SSL): checked
port: 5223
login ID: [EMAIL PROTECTED]
--
Connect() failed
https://launchpad.net/bugs/75842
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
On 12/16/06, Xavier Claessens [EMAIL PROTECTED] wrote:
Did you set the server to talk.google.com, ssl enabled and port 5223 ?
I did now. I had copied the settings from Gaim (incorrectly) so it
wasn't set right. But there was no UI feedback except in the debug
output. (I don't need to tell you
That's a known problem already reported upstream.
--
Connect() failed
https://launchpad.net/bugs/75842
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
On 12/16/06, Xavier Claessens [EMAIL PROTECTED] wrote:
That's a known problem already reported upstream.
I'm sorry, but what is? This whole bug?
--
Connect() failed
https://launchpad.net/bugs/75842
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Can you try this:
kill all telepathy process and then run:
$ GOSSIP_DEBUG=all gossip
and post here the output of gossip.
Thanks :D
--
Connect() failed
https://launchpad.net/bugs/75842
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
** Changed in: gossip-telepathy (Ubuntu)
Importance: Undecided = Medium
Assignee: (unassigned) = Telepathy
Status: Unconfirmed = Needs Info
--
Connect() failed
https://launchpad.net/bugs/75842
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
[EMAIL PROTECTED]:~$ lsb_release -dr
Description:Ubuntu feisty (development branch)
Release:7.04
[EMAIL PROTECTED]:~$ dpkg -l gossip-telepathy | grep ^ii
ii gossip-telepathy 0.21~cvs20061215-0ubuntu1 friendly Jabber client for GNOME
(using Telepathy)
Strange, i can to connect in
Telepathy: Possible match:
org.freedesktop.Telepathy.Connection.gabble.jabber._fernando_ribeiro_jabber_conab_gov_br_Telepathy
why it take old account (of my local server [removed before trying login
on gtalk])?
strange hehehe
--
Connect() failed
https://launchpad.net/bugs/75842
--
Make sure you enable ssl support and connect port 5223, it should fix
the problem I guess...
--
Connect() failed
https://launchpad.net/bugs/75842
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Yes really only connect with ssl enable.
I have jabber working fine now.
Thanks
--
Connect() failed
https://launchpad.net/bugs/75842
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
On 12/15/06, Xavier Claessens [EMAIL PROTECTED] wrote:
Make sure you enable ssl support and connect port 5223, it should fix
the problem I guess...
Are you thinking this will work for me also? I'm not at my machine to
test yet.
--
Connect() failed
https://launchpad.net/bugs/75842
--
[EMAIL PROTECTED]:~$ dpkg -l telepathy-idle | grep ^ii
ii telepathy-idle 0.0.3-0ubuntu1 IRC connection manager for Telepathy
telepathy-gossip with irc (telepathy-idle) working fine here.
I'm unable to reproduce the original issue reported.
thanks
--
Connect() failed
On 12/15/06, Fernando Ribeiro [EMAIL PROTECTED] wrote:
I'm unable to reproduce the original issue reported.
Should you maybe report a new bug then?
--
Connect() failed
https://launchpad.net/bugs/75842
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
BTW, I tried with and without SSL; didn't matter. (The output that
follows is with SSL.)
On 12/15/06, Xavier Claessens [EMAIL PROTECTED] wrote:
Can you try this:
kill all telepathy process and then run:
$ GOSSIP_DEBUG=all gossip
AccountManager: Attempting to parse
20 matches
Mail list logo
