Empathy (MSN) unable to connect
Joe Marcus Clarke
marcus at freebsd.org
Wed Nov 10 22:02:41 UTC 2010
On 11/10/10 4:47 PM, Harald Servat wrote:
>
>
> 2010/11/10 Joe Marcus Clarke <marcus at freebsd.org
> <mailto:marcus at freebsd.org>>
>
> On 11/9/10 4:41 PM, Harald Servat wrote:
> > 2010/11/9 Harald Servat <redcrash at gmail.com
> <mailto:redcrash at gmail.com>>
> >
> >>
> >>
> >> 2010/11/9 Joe Marcus Clarke <marcus at freebsd.org
> <mailto:marcus at freebsd.org>>
> >>
> >> On 11/8/10 8:12 AM, Harald Servat wrote:
> >>>> 2010/11/8 Denise H. G. <darcsis at gmail.com
> <mailto:darcsis at gmail.com>>
> >>>>
> >>>>>
> >>>>> On 2010/11/08 at 19:47, Harald Servat <redcrash at gmail.com
> <mailto:redcrash at gmail.com>> wrote:
> >>>>>>
> >>>>>> Hello,
> >>>>>> I find that empathy (latest version available in packages)
> is not
> >>> able
> >>>>> to
> >>>>>> connect to the MSN network. It reports "Unable to connect".
> Another
> >>> user
> >>>>> and
> >>>>>> myself have opened a thread about the topic in the freebsd
> forums but
> >>> I
> >>>>>> don't know if you take a look at it, this is the reason of
> this emai.
> >>>>>>
> >>>>>> Have you find the same issues in empathy? Do you have any
> idea on
> >>> how
> >>>>> to
> >>>>>> fix them?
> >>>>>>
> >>>>>> Thank you very much.
> >>>>>> ................
> >>>>>
> >>>>> Hello,
> >>>>>
> >>>>> Same problem here. I've googled the problem and found it
> perhaps is
> >>>>> not FreeBSD specific. Many empathy users on Linux platforms have
> >>>>> reported similar problems. And my solution is to use
> net-im/emesene
> >>>>> for MSN messaging ... though it may not be a perfect one...
> >>>>>
> >>>>> It seems this has something to do Empathy dealing with MSN
> protocol.
> >>>>> It uses a Python library to do the job (the same one Pidgin
> uses for
> >>>>> MSN) but unfortunately the library does not agree with
> empathy in one
> >>>>> way or another...
> >>>>>
> >>>>> --
> >>>>> If you have watched a TV series only once, and you watch
> >>>>> it again, it will be a rerun of the same episode.
> >>>>>
> >>>>
> >>>> You're right, there are other platforms that show the same
> problem. I
> >>> tried
> >>>> the solutions they report, but none worked on my installation,
> that's
> >>> what
> >>>> make me think that this could be freebsd specific.
> >>>
> >>> Can you try with papyon 0.5.2 (recently updated). This fixed a
> rather
> >>> nasty bug. I'm getting much further along in MSN connection now.
> >>>
> >>> Joe
> >>>
> >>>>
> >>>> It looks like we'll have to wait for the next release of empathy.
> >>> Meanwhile,
> >>>> I'll take a look at emesene.
> >>>>
> >>>> Thank you!
> >>>>
> >>>
> >>>
> >>> --
> >>> Joe Marcus Clarke
> >>> FreeBSD GNOME Team :: gnome at FreeBSD.org
> >>> FreeNode / #freebsd-gnome
> >>> http://www.FreeBSD.org/gnome
> >>>
> >>
> >>
> >> Ok, I'll give a try when I'm in my FreeBSD box.
> >>
> >> Thank you!
> >>
> >> --
> >> _________________________________________________________________
> >> Fry: You can see how I lived before I met you.
> >> Bender: You lived before you met me?!
> >> Fry: Yeah, lots of people did.
> >> Bender: Really?!
> >>
> >>
> > Joe,
> >
> > I'm seeing the same behavior even using papyon 0.5.2 (I've just
> upgraded
> > this port).
>
> Make sure all telepathy processes have been killed. Then, from empathy,
> to go Help > Debug, and look at the MSN messages. What errors do
> you get?
>
>
> Joe,
>
> from a cold boot, empathy was unable to log into my msn account.
> Looking at Help > Debug I can find two debug types "Empathy" and
> "misson-control". The former shows me a gray windows with the "The
> selected connection manager does not support the remote debugging
> extension". The latter, shows me two messages, both of them are the same
> (maybe because I tried to connect twice, one at the start of empathy and
> once when I hit the "reload" button):
>
> request_connection_cb: RequestConnection failed: Message did not receive
> a reply (timeout by message bus)
>
> Does it help? Can I provide something else to debug it?
This sounds like a telepathy-butterfly problem. Try reinstalling that port.
Joe
--
Joe Marcus Clarke
FreeBSD GNOME Team :: gnome at FreeBSD.org
FreeNode / #freebsd-gnome
http://www.FreeBSD.org/gnome
More information about the freebsd-gnome
mailing list