Mxit not working in Empathy 2.30.0.1

Bug #573857 reported by thenailedone
96
This bug affects 19 people
Affects Status Importance Assigned to Milestone
Empathy
Expired
Medium
Telepathy Haze
Confirmed
Undecided
Unassigned
empathy (Ubuntu)
Triaged
Low
Unassigned

Bug Description

Binary package hint: empathy

Mxit for Empathy is not working (does not connect).

Pidgin client for Linux works well the difference thus far seems to be that as soon as the client in Pidgin is configured you get another options dialogue where you have to add an anti-bot code (enter the numbers in the image deal) and you must also select your country etc. This does not happen when using Empathy and I think this is the main problem...

Empathy 2.30.0.1 on Lucid Lynx.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: empathy 2.30.0.1-0ubuntu3
ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-21-generic i686
Architecture: i386
Date: Sun May 2 21:51:29 2010
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
ProcEnviron:
 LANG=en_US.utf8
 SHELL=/bin/bash
SourcePackage: empathy

Revision history for this message
thenailedone (thenailedone) wrote :
Revision history for this message
hawk (rudidu) wrote :

I can confirm this. Mxit protocol functions perfectly with pidgin (albeit throught a plugin.) Empathy supposedly supports Mxit but is impossible to connect to my account.

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

you could try it with empathy 2.30.1 which is now in Lucid.

Revision history for this message
hawk (rudidu) wrote :

Nope, still doesn't work. Same behavior.

Revision history for this message
Michael Heyns (mike-bean-heyns) wrote :

This is requested from the user using purple_request_fields(), and I see that telepathy-haze doesn't implement that API
(http://git.collabora.co.uk/?p=telepathy-haze.git;a=blob;f=src/request.c).

description: updated
Changed in empathy:
status: New → Confirmed
Changed in empathy (Ubuntu):
status: New → Confirmed
Changed in telepathy-haze:
status: New → Confirmed
Angel Abad (angelabad)
Changed in empathy:
importance: Undecided → Unknown
status: Confirmed → Unknown
Changed in empathy:
status: Unknown → Confirmed
Revision history for this message
Relebogile Chiloane (m4tic) wrote :

Still not working empathy 2.30.2

Changed in empathy:
importance: Unknown → Medium
Revision history for this message
Omer Akram (om26er) wrote :

setting to triaged since there is a upstream bug linked

Changed in empathy (Ubuntu):
importance: Undecided → Low
status: Confirmed → Triaged
Revision history for this message
Omer Akram (om26er) wrote :

does mxit work in ubuntu-10.10? if not we should remove the support from empathy

Revision history for this message
Bryan Turner (turner62) wrote :

Even in 10.10 (Maverick)... Seriously I think that people should use pidgin again. At least it worked

Revision history for this message
hawk (rudidu) wrote :

Still broken in Empathy 2.32.1 :/

Using pidgin - at least the protocols it ships with actually work.

Either remove support for mxit, or fix it.

Revision history for this message
Daniel Cheung (daniel-2345) wrote :

The empathay should be updated and fixed on the 12.04 Precise but NO! They didn't fix it. Empathay with a Mxit option here just lying around ffor nothing!!

Revision history for this message
Jodie Robinson (jodiematthewrobinson) wrote :

Empathy is still being a complete retard in this regard. Why can't we just pull the Mxit option out of the available list until such time as it is working?

To me this looks quite unprofessional. I can imagine some new person starting up a live session, looking under the messaging menu, seeing Mxit and being unable to login. To me things like that are quite off-putting...

I'm using elementary OS Luna by the way.

Revision history for this message
hawk (rudidu) wrote : Re: [Bug 573857] Re: Mxit not working in Empathy 2.30.0.1

It's been a problem for years now, the devs just don't care.
On 19 Dec 2012 7:56 PM, "Jodie Robinson" <email address hidden>
wrote:

> Empathy is still being a complete retard in this regard. Why can't we
> just pull the Mxit option out of the available list until such time as
> it is working?
>
> To me this looks quite unprofessional. I can imagine some new person
> starting up a live session, looking under the messaging menu, seeing
> Mxit and being unable to login. To me things like that are quite off-
> putting...
>
> I'm using elementary OS Luna by the way.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/573857
>
> Title:
> Mxit not working in Empathy 2.30.0.1
>
> Status in Chat app, and Telepathy user interface:
> Confirmed
> Status in Telepathy Haze:
> Confirmed
> Status in “empathy” package in Ubuntu:
> Triaged
>
> Bug description:
> Binary package hint: empathy
>
> Mxit for Empathy is not working (does not connect).
>
> Pidgin client for Linux works well the difference thus far seems to be
> that as soon as the client in Pidgin is configured you get another
> options dialogue where you have to add an anti-bot code (enter the
> numbers in the image deal) and you must also select your country etc.
> This does not happen when using Empathy and I think this is the main
> problem...
>
> Empathy 2.30.0.1 on Lucid Lynx.
>
> ProblemType: Bug
> DistroRelease: Ubuntu 10.04
> Package: empathy 2.30.0.1-0ubuntu3
> ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2
> Uname: Linux 2.6.32-21-generic i686
> Architecture: i386
> Date: Sun May 2 21:51:29 2010
> InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386
> (20100429)
> ProcEnviron:
> LANG=en_US.utf8
> SHELL=/bin/bash
> SourcePackage: empathy
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/empathy/+bug/573857/+subscriptions
>

Changed in empathy:
status: Confirmed → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Related questions

Remote bug watches

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