desktop-packages team mailing list archive

[Felipe Contreras <felipe.contreras@xxxxxxxxx>]

C de-Avillez:

First of all, let's remember that you don't have to fix all the CM's to
fix this issue. Ubuntu can fix this *today*, regardless of the status of
the telepathy CM's

(1) This is pointless, because a) it's not needed, and b) each CM has
different issues regarding proxy support.

* telepathy-haze

This works fine.

* telepathy-butterfly

It uses papyon, which looks like it's going to be discontinued. It has
basic proxy support, but it's not done through GIO, as it probably
should be.

* telepathy-gabble

Seems to have proxy support  through GIO, but there are issues.

* telepathy-idle

No proxy support on the horizon.

* telepathy-rakia

No proxy support on the horizon.  Or bug report about it.

* telepathy-sunshine

No proxy support on the horizon.  Or bug report about it.

Even if you fix all these issues in the connection-managers, this
*still* doesn't solve the problem that some people need proxy
configuration in a per-proxy way, as explained upstream bug #16034, you
would need modifications both in the connection managers, *AND* Empathy.

(2) I have already done that:

http://thread.gmane.org/gmane.comp.freedesktop.telepathy/4103

Some responses I've heard from upstream developers, are "Nobody uses
proxies", "Nobody uses HTTP connect", "Sysadmins probably never allow
HTTP connect for non 443 ports", "If you need special proxies for some
accounts, write your own PAC file". And similar.

The fact of the matter is that they have no urgency to fix this, or even
acknowledge the problems. In the meantime, people are completely unable
to use Empathy, and are forced to use Pidgin (or use telepathy-haze by
removing all the other CM's Ubuntu ships by default).

Again, Ubuntu could fix this *today*, it doesn't have to wait for
upstream to acknowledge this is an issue.

(3) I didn't get that.

Pedro Villavicencio:

That's only if you use global settings, and as I argued in the response
for (1); that's not enough. Upstream bug bug #22065 complains about
that, and upstream bug #16034 describes the solution, which requires
modifications to Empathy.

So, I repeat, do you want to fix this or not? Because you can fix it
right now.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to empathy in Ubuntu.
https://bugs.launchpad.net/bugs/304889

Title:
  Does not use system proxy settings

Status in Chat app, and Telepathy user interface:
  Invalid
Status in Jabber/XMPP connection manager:
  Confirmed
Status in Telepathy Haze:
  Confirmed
Status in A full-featured IRC connection manager for telepathy.:
  Confirmed
Status in “empathy” package in Ubuntu:
  Invalid
Status in “empathy” source package in Lucid:
  Invalid
Status in “empathy” package in Unity Linux:
  Invalid

Bug description:
  Binary package hint: empathy

  Empathy wont connect to any major service trough a proxy. I've tried Google Talk, Jabber, MSN and Yahoo.
  I set the proxy preferences in GNOME, it's a plain proxy for all protocols, without authentication.

  Pidgin works normally in the same setup.

  Ubuntu 8.10, Empathy 2.24.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/empathy/+bug/304889/+subscriptions