Ubuntu

Does not use system proxy settings

Reported by jorge on 2008-12-03
934
This bug affects 189 people
Affects Status Importance Assigned to Milestone
Empathy
Invalid
Undecided
Unassigned
Telepathy Haze
Confirmed
Medium
telepathy-gabble
Confirmed
Medium
telepathy-idle
Confirmed
Medium
empathy (Ubuntu)
Medium
Unassigned
Declined for Maverick by Sebastien Bacher
Lucid
Medium
Unassigned
empathy (Unity Linux)
Invalid
Undecided
Unassigned

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

I tried using telepathy, through Empathy as frontend to use VOIP functions.
However, the interface provided no place to specify proxy.

Telepathy doesn't seems to support proxy for IM, while most popular applications like Pidgin/Purple do.

Steps to Reproduce:
1. Install Empathy with related telepathy-gabble support behind a network requiring authenticated proxy
2. Create a new account and try to login.

Actual Results:
Empathy is unable to connect to required protocol's network.

Expected Results:
Should connect to required network, and should offer a proxy dialog or use system settings.

Build Date & Platform:
Used PPA repository at http://ppa.launchpad.net/telepathy/ubuntu hardy main
Package: telepathy-gabble 0.7.6.1~ppa8.04+1

Adjusting title.

Supporting proxies that need a username/password (HTTP error 407) will require the following changes:

* Gabble gains http-proxy-username and http-proxy-password parameters

* Either or both of:

  (a) Mission Control takes the configured GNOME proxy username and password, and passes them on to Gabble in the same way that the server and port are currently done

  (b) Empathy gains http-proxy-server, http-proxy-port, http-proxy-username and http-proxy-password parameters in the Advanced area of account config

(Ideally, in the long term, Gabble should be able to ask the UI to ask the user for a username and password interactively, but that's tricky D-Bus API work.)

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

xoco (arthur.ivanov) wrote :

totaly agree.
9.04 devel

same issue

$ env | grep -i proxy
http_proxy=http://xxx.xxx.xxx.xxx:3128/
ftp_proxy=ftp://xxx.xxx.xxx.xxx:3128/

ICQ connect - ok
Jabber still trying connect directly ..

xoco (arthur.ivanov) wrote :

wireshark capture it:
Internet Protocol, Src: 10.1.200.60 (10.1.200.60), Dst: 209.85.137.125 (209.85.137.125)
Transmission Control Protocol, Src Port: 38009 (38009), Dst Port: xmpp-client (5222), Seq: 0, Len: 0

209.85.137.125 valid IP not proxy ;(

jorge (xxopxe) wrote :

Oookay... Having the default messaging application not support a plain proxy is sort of, ehrm, silly. Specially if it used to work. I'm pretty astonished this just went trough.
I'd request pumping this one to, if not "critical", to "grave".

naheed (naheed) wrote :

Still the problem exist in Jaunty as of May 20, 2009. Cannot login inside corporate lan (global proxy is set). Works fine on open network.

Changed in empathy (Ubuntu):
importance: Undecided → High
status: New → Confirmed
summary: - Empathy wont connect trough a proxy
+ Does not use system proxy settings

<wasabi> haze-Message: [error] msn: Connection error: Access denied: HTTP proxy server forbids port 1863 tunneling.
<wjt> :)
<wjt> well, haze doesn't support the proxy CM parameter
 so libpurple *is* poking gconf behind my back

The default system proxy is being used for CONNECT. There is no option to disable the proxy. If the system proxy server doesn't support CONNECT, users are out of luck. Haze should provide config options to make libpurple not do this.

Same for me on Jaunty as of June 16, 2009.

I think this bug should be considered a show stopper for making Empathy the default IM client in Karmic.

Gabor Kelemen (kelemeng) wrote :
Pedro Villavicencio (pedro) wrote :

looks like it, linking the report.

Changed in empathy (Ubuntu):
status: Confirmed → Triaged
Changed in empathy:
status: Unknown → Confirmed
molybtek (ubuntu-truong) wrote :

With version 2.27.91.1, ICQ and Yahoo picks up the proxy settings in Gnome, however MSN and GTalk/Jabber still ignores the proxy settings and tries to connect direct.

Mario Lameiras (skzo) wrote :

With version 2.27.92, I still have this problem with msn and jabber. This a main issue, with using empathy...

alsuren (alsuren) wrote :

just a few possibly related bugs:

http://bugs.freedesktop.org/show_bug.cgi?id=17073
(freedesktop bugzilla is the correct place for this kind of bug. If someone could do a big trawl for related bugs, that would be good, but I've got to dash.)

https://bugs.maemo.org/show_bug.cgi?id=960
https://bugs.maemo.org/show_bug.cgi?id=718
(maemo also uses telepathy for jabber)

Hope this helps.

jorge (xxopxe) wrote :

Oh, and i think the situation is worse than the new title suggest: not only it does't use system setting, there's no way to set a proxy in the app either.

The inability to set proxy for Empathy forces me to use another chat program (Pidgin).

tphillippe (trjphill) wrote :

Confirmed for Karmic beta 1 and
Empathy 2.28.0.1

Forced to use Pidgin.

Ephraim (thilo) wrote :

Still in RC it's not working.

SonniesEdge (sonniesedge) wrote :

Yup, latest updated RC and I can only use Empathy from home. Trying to use it at work or university through their proxies is a no go.

Nizzzia (nizzzia) wrote :

Just another confirmation of the most annoying bug in Karmic. That's really ridiculous, how come the default application does not support proxy. Devels keep working on improving interface in MUC, support for adium theming and other less relevant things, while the application is not usable. Nonsense

Roni (ronibalthazar) wrote :

Confirmed on both Karmic installations: Fresh install and upgraded from jaunty

Changed in empathy (Ubuntu):
status: Triaged → Confirmed
SonniesEdge (sonniesedge) wrote :

This has been marked as "resolved" by upstream and more importantly, the buck has been passed up to the Mission Control project, run by the free desktop people... http://telepathy.freedesktop.org/wiki/Mission%20Control

jcapinc (jeffs-linux) wrote :

Why would they switch to something like empathy if it has such a huge bug? Port lockdowns are commonplace in public WiFi installations, Proxies are the only resort in that instance. It baffles me that this is this way!

Confirmation of bug. im having it to, there is no visible solution

Diego d'Ippolito (lokar) wrote :

Confirmed on both Karmic installations: Fresh install and upgraded from jaunty.
I totally agree with jcapinc.

Sam Illingworth (mazz0) wrote :

I have this problem but I don't have any proxy set in Gnome, it all happens invisibly somewhere on the corporate LAN. Is this likely to be the same issue?

Hedgehog_57 (hedgehog57) wrote :

Sam: We don't know how access to internet is made in Your office. Maybe You have some sort of transparent proxy. Mabe configuration is made in Your browser itself. Or You have WPAD script in Your corporate environment.

And maybe i have misunderstood You because of my bad english. What have meant when You said "it all happens invisibly somewhere on the corporate LAN" ?

Ryan Stuart (ryanstuart) wrote :

This is very disappointing. I installed the new version of Ubuntu (9.10 amd64) on my new laptop (Dell Studio XPS) today. For an operating system that has spent time on high profile projects recently like Paper Cuts etc, to have something so basic fail is unbelievable. How am I meant to argue with my friends that Ubuntu is a viable alternative to Windows when it can't get something as simple as IM right?

gaestur (usx) wrote :

Confirmed for Karmic.

Brian Curtis (bcurtiswx) wrote :

someone having the problem please type "apport-collect 304889" in their terminal

molybtek (ubuntu-truong) wrote :

apport-collect doesn't work through proxy either...

Architecture: i386
DistroRelease: Ubuntu 9.10
Package: empathy 2.28.1.1-0ubuntu1
PackageArchitecture: i386
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_US.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
Tags: ubuntu-unr
Uname: Linux 2.6.31-14-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

tags: added: apport-collected
Brian Curtis (bcurtiswx) on 2009-11-15
Changed in empathy (Ubuntu):
status: Confirmed → Triaged

Architecture: i386
DistroRelease: Ubuntu 9.10
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release Candidate i386 (20091020.3)
NonfreeKernelModules: nvidia
Package: empathy 2.28.1.1-0ubuntu1
PackageArchitecture: i386
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=en_GB.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
Uname: Linux 2.6.31-14-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

SaNuke (sanuke) wrote :

Confirmed, in my Ubuntu 9.10 unr on eeepc and amd64 on Desktop PC - still not work with proxy.

Michael (michaelplazzer) wrote :

Ditto i386, fresh install

Architecture: i386
CheckboxSubmission: ef0a65cd688e8392f694bbaccf733936
CheckboxSystem: b1865df84255b8716d3bcc269ff410d1
DistroRelease: Ubuntu 9.10
Package: empathy 2.28.1.1-0ubuntu1
PackageArchitecture: i386
ProcEnviron:
 LANGUAGE=en_US.UTF-8
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
Uname: Linux 2.6.31-14-generic i686
UserGroups: adm admin audio cdrom dialout dip fax fuse libvirtd lpadmin netdev plugdev sambashare scanner tape uml-net video
XsessionErrors:
 (gnome-settings-daemon:2739): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (nautilus:3241): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed
 (polkit-gnome-authentication-agent-1:3300): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed

Vinay Wagh (wagh-vinay) on 2010-01-16
Changed in empathy (Ubuntu):
status: Triaged → Confirmed
Changed in telepathy-idle:
status: Unknown → Confirmed
Changed in telepathy-gabble:
status: Unknown → Confirmed
Changed in telepathy-haze:
status: Unknown → Confirmed
Changed in empathy (Ubuntu):
status: Confirmed → Triaged
Changed in empathy (Ubuntu Lucid):
assignee: nobody → Canonical Desktop Team (canonical-desktop-team)
Changed in empathy (Ubuntu Lucid):
importance: High → Medium
Changed in empathy (Ubuntu):
assignee: Canonical Desktop Team (canonical-desktop-team) → nobody
Changed in empathy (Ubuntu Lucid):
assignee: Canonical Desktop Team (canonical-desktop-team) → nobody
Praseem (praseem007) on 2010-08-31
Changed in empathy (Ubuntu Lucid):
status: Triaged → New
Changed in empathy (Ubuntu Lucid):
status: New → Confirmed
Changed in telepathy-gabble:
importance: Unknown → Medium
Changed in telepathy-haze:
importance: Unknown → Medium
Changed in telepathy-idle:
importance: Unknown → Medium
Changed in empathy:
importance: Unknown → High
status: Confirmed → Unknown
115 comments hidden view all 170 comments

Telepathy Butterfly (MSN) already supports SOCKS5 and HTTP Connect proxy with authentication. I'm working on adding HTTP Connect proxy to Wocky (while SOCKS5/4a/4 is provided by GLib 2.26 and newer).

I suggest we attach dependency to this bug for tracking. Contrary to what Pidgin do, Telepathy connection manager rely on system proxy settings only for now (which are optained using libproxy).

Changed in telepathy-haze:
importance: Medium → Unknown
Changed in telepathy-idle:
importance: Medium → Unknown
Changed in telepathy-gabble:
importance: Medium → Unknown
Changed in telepathy-gabble:
importance: Unknown → Medium
Changed in telepathy-idle:
importance: Unknown → Medium
Changed in telepathy-haze:
importance: Unknown → Medium
Changed in empathy (Ubuntu):
status: Triaged → In Progress
Fabio (fabiove) on 2011-05-10
Changed in empathy (Ubuntu):
status: In Progress → Confirmed
24 comments hidden view all 170 comments
Felipe Contreras (felipec) wrote :

I already explained many times how to fix this *right now* (in fact more than one year ago). See comment #76.

The fact of the matter is that Ubuntu people don't care, otherwise they would have marked it as critical as I suggested in comment #79. "It will be on the next release cycle" somebody said as an excuse. And here we are a year later.

Michael (michaeljt) wrote :

Ahem, Felipe, do you have commit rights, either upstream or down? That doesn't relate to the quality of what you are saying, but in this situation having a committer to back your changes is as important as their actual quality.

Felipe Contreras (felipec) wrote :

Commit rights are irrelevant. Nobody has commit rights in the Linux kernel except Linus. Does that mean everybody else's opinion don't matter.

See comment #92, #93 and #94; the fix is known to work.

Michael (michaeljt) wrote :

Perhaps I am misunderstanding something, but as a telepathy-idle user is that relevant to me? In a pinch I will go back to pidgin of course, but I would prefer a proper fix in empathy.

Felipe Contreras (felipec) wrote :

@Michael telpathy-haze has support for IRC too.

AIM, facebook, gadugadu, groupwise, IRC, ICQ, jabber, local XMPP, MSN, QQ, sametime, sipe, yahoo, zephyr, mxit, and sip; IOW what libpurple (Pidgin) supports.

Brian Curtis (bcurtiswx) wrote :

This is not a unity specific issue. This is Ubuntu in general. Invalidating that.

Changed in empathy (Unity Linux):
status: New → Invalid
Brian Curtis (bcurtiswx) wrote :

As an update to everyone interested. There are tons of limitations as to getting this bug complete. As of right now proxy works for Gabble (mind glib-networking has to be installed), there is some interest in porting idle to GIO which may allow proxying to work. For a lot of other connection managers this either isn't possible or severely limited. haze is a libpurple implementation, and telepathy has no control over that. Plus haze can't allow popups for password questions and therefore even if libpurple supported it, it would have severe limitations.

This is not an empathy bug but a bug with the connection manager themselves, and therefore I'm closing all empathy instances.

Changed in empathy (Ubuntu):
status: Confirmed → Invalid
Changed in empathy (Ubuntu Lucid):
status: Confirmed → Invalid
Changed in empathy:
importance: High → Undecided
status: Unknown → New
status: New → Invalid
Felipe Contreras (felipec) wrote :

@Brian No, proxy support works on gabble only for certain kinds of configurations. For example a global HTTP proxy doesn't work. See comment #118.

haze is *not* a libpurple implementation, and telepathy *does have* control over that.

And what do you mean "can't allow popups for password questions"?

Brian Curtis (bcurtiswx) wrote :

http://telepathy.freedesktop.org/wiki/Components
haze is an implementation of libpurple, which telepathy does NOT have control over.

Libpurple will allow for password prompts on proxies, haze can not use these (idk why, this is all info from uptream)

Also , gabble I have been told "just works".

Felipe Contreras (felipec) wrote :

No, telepathy-haze is just another Telepathy Connection Manager. Read the text you just shared:

Haze: A connection manager based on Pidgin's libpurple, supporting all protocols in Pidgin (AIM, ICQ, Yahoo, MSN, etc) at a basic level, but already very usable.

libpurple uses GConf's system proxy settings, which contain authentication.

And you have been told wrong, here's a screenshot with the latest gabble not working (latest glib, with glib-networking, with libproxy support):
http://people.freedesktop.org/~felipec/gabble-proxy.png

See?

Works fine with libproxy-simple though.

Mike Mestnik (cheako) wrote :

Hello,
  I've just reconfirmed this bug exists with several Telepathy ?backends? when attempting to use a SOCKS proxy... an HTTP connect proxy is configured to forward connections through the available socks proxy.

I've switched to Pidgin and this is confirmed to work, however it's in no way a solution to any problem... at best it's a cheap work around. Here is one solution...

Place these into /etc/rc.local and run it:
daemon -n socat5223 -- socat -ly TCP-LISTEN:5223,fork,reuseaddr SOCKS4A:127.0.0.1:talk.google.com:5223,socksport=9050
daemon -n socat5222 -- socat -ly TCP-LISTEN:5222,fork,reuseaddr OPENSSL:127.0.0.1:5223,verify=0

You'll need both the daemon and socat packages installed. Then one should be able to set localhost as the server to connect to. socat can also make use of HTTP connect proxies, I believe.

Why you wouldn't put this into your application is beyond me, it's a little bit of shell scripting and it would close the bug... you could even make use of UNIX domain sockets. It's only politics that keeps this bug open, ppls own agendas getting in the way of implementing options/features users are requesting. "Why would an application developer care about the available features on an HTTP proxy they would likely never use?" The use should be able to configure and use proxies, don't know why this is so difficult a concept to understand.

Wow. 3 and half years!

denix (denics) wrote :

still the same situation with Empathy 3.2.0.1 and Ubuntu 11.10

Changed in empathy (Ubuntu):
status: Invalid → Confirmed
Ir0nsh007er (ir0n) wrote :

Not working here Empathy 3.2.0.1 Ubuntu 11.10

!!!!!!!

C de-Avillez (hggdh2) wrote :

And still not an Empathy issue. There is nothing to be done on Empathy, fixes have to be written to the various protocol handlers.

Invalidating (again) the Empathy task.

Changed in empathy (Ubuntu):
status: Confirmed → Invalid
jorge (xxopxe) wrote :

Uh, I don't know what a "protocol handler" is, nor I care were fixes have to be written. As a user, what is broken is Empathy. It has a bug: I have a proxy, Empathy does not work.

Michal (michal.post) wrote :

> And still not an Empathy issue. There is nothing to be done on Empathy
@hggdh2: With all due respect, I cannot agree with you.

Consider this (real!) scenario:
In my company, I use IM multi protocol client on Ubuntu. I need to have 4 accounts:
1. local (jabber) --> local intranet server1 [must use DIRECT http, must NOT use proxy]
2. gtalk (jabber) --> internet via http proxy [must use http via PROXY]
3. exchange (sipe) --> local intranet server2 [must use directly http, must NOT use proxy]
4. one more (gg) --> internet via http proxy [must use http via PROXY]

Obviously, this can be done only if IM client let's me to setup http_proxy per account. Empathy does not. It is missing this feature.
This is the reason, why I (and a lot of my colleagues in50 000+ employees company) are using Pidgin instead of Empathy which is the default Ubuntu IM client. Of course not all of employees are using Ubuntu, but all of them are potentially affected by this bug. Only in this one company. There are several others companies, campuses etc in similar situation.

Please also note, that many popular applications have builtin proxy settings (Firefox, Pidgin, ...).
It's not a critical feature for IM, but for multi communicator it's important.

Kind Regards,
Michal

C de-Avillez (hggdh2) wrote :

@Michal: there is a disconnect here: technically -- which where the bug tasks come in -- this is not an Empathy issue: Empathy does not do network. Network activities are performed by the so-called Connection Managers (which I called protocol handlers), usually the telepathy-<whatever> modules.

Support for proxy must be added in these modules, not on Empathy. This may be -- or not -- a major undertaking; I do not know.

But, no matter what, the best place to ask for it is "upstream" (where the authors reside). For each of the current valid tasks on this bug, there is a link to the upstream bug. I had a quick look at them, and it seems pretty much nothing has been done by the developers regarding proxy usage. Comments there would probably help more than here.

And I do agree that lacking proxy support is not good. But this is a bug, a technical report of an error/issue. No matter what you (or jorge above) think, we have to have the correct modules listed.

Empathy (overall) suffers with the lack of proxy support. But there is nothing to be done for Empathy itself here -- so it is Invalid as a bug task. On the other hand, telepathy-gabble, telepathy-haze, and telepathy-idle are correctly set.

Michal (michal.post) wrote :

@hggdh2:
Thank you for the clarification.
Have a good day.

7 comments hidden view all 170 comments

Correct me if I'm wrong, but GNOME 3 proxy settings don't have any fields to enter the authentication information, so Simon McVittie's option (a) is not currently possible.

6 comments hidden view all 170 comments
Felipe Contreras (felipec) wrote :

> But there is nothing to be done for Empathy itself here -- so it is Invalid as a bug task.

This is not true. The upstream "support" would just use the GNOME proxy settings, and it would not be possible to configure the proxy per-account, for that you would still need changes in Empathy.

If you assume this is only to read the system settings, then yes, this is not a bug in Empathy, it has to be implemented in all the telepathy connection managers but the list above (haze, gabble, and idle) is not nearly complete. Plus, none of those bugs have any priority, severity, or even any comment there.

At this point it would be useful to do what Fedora does, have keep this bug open as a metabug, or tracking bug, and when all the telepathy CM's are fixed, then this is closed.

Moreover, the upstream tracking bugs are wrong.

Bug #22065 is not to use system proxy settings in telepathy-haze, in fact, it's for exactly the opposite; have an option to *disable* the proxy for this particular account, for which actually, you would need changes in Empathty. In fact, if you read the comments above in this bug report, you would see that people confirm that telepathy-haze is actually the only one that works.

You could fix this bug *today* if you wanted to, by just distributing telepathy-haze, and not the other connection managers. So there's something Ubuntu can do to fix this, but you just don't want to.

Bug #16034 has nothing to do with system proxy settings, which supposedly telepathy-gabble already supports (although not that smoothly). It is about user/password authentication to the proxy.

Interestingly enough if you read comment #2, a telepathy developer suggests as an option to modify Empathy to allow configuring the proxy settings in a *per account* way:

> (b) Empathy gains http-proxy-server, http-proxy-port, http-proxy-username and http-proxy-password parameters in the Advanced area of account config

Bug #12376 is correct, but as you can see, there's nothing going on over there.

So, do you want to fix this or not? If you want to fix this, then closing the bug is like shuffling it under the carpet... It won't achieve anything.

7 comments hidden view all 170 comments

(In reply to comment #3)
> Correct me if I'm wrong, but GNOME 3 proxy settings don't have any fields to
> enter the authentication information, so Simon McVittie's option (a) is not
> currently possible.

Simon comment was posted in 2008, Gnome 3 didn't yet exist to make proxy support worst.

6 comments hidden view all 170 comments
C de-Avillez (hggdh2) wrote :

@Felipe:

(1) may I suggest you to find the correct upstream bugs and update the link here? Or open upstream bugs as needed;

(2) may I also suggest you to carry your reasoning upstream?

(3) which bug is it you state is closed?

Pedro Villavicencio (pedro) wrote :

According to https://bugzilla.gnome.org/show_bug.cgi?id=602824 the work should be on the lower layers. I'm happy to open tasks against the telepathy projects or any others though.

Felipe Contreras (felipec) wrote :

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.

Le mercredi 30 novembre 2011 à 15:55 +0000, Felipe Contreras a écrit :
> * telepathy-haze
>
> This works fine.

Stop claiming that switching to Haze is the solution of all the world's
problems. Haze can be an option for protocols not having a proper CM but
it would be completely stupid to switch to it for XMPP: no call, no file
transfer, no muc, no desktop sharing...

> * 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.

I agree that Haze could be used. Actually we're going to switch to Haze
for MSN accounts in 3.4 as butterfly (and the other Python CMs) are not
properly maintained and lake all the recent Telepathy APIs.

> * telepathy-gabble
>
> Seems to have proxy support through GIO, but there are issues.

Which issues exactly? Are there in Gabble? in GIO?

> * telepathy-idle
>
> No proxy support on the horizon.

Idle has switched to GIO (fdo #37145) so SHOULD be at the same state as
Gabble.

> * telepathy-rakia
>
> No proxy support on the horizon. Or bug report about it.

Please feel free to open one.

> * telepathy-sunshine
>
> No proxy support on the horizon. Or bug report about it.

Same as Butterfly.

Felipe Contreras (felipec) wrote :

On Wed, Nov 30, 2011 at 6:37 PM, Guillaume Desmottes <email address hidden> wrote:
> Le mercredi 30 novembre 2011 à 15:55 +0000, Felipe Contreras a écrit :
>> * telepathy-haze
>>
>> This works fine.
>
> Stop claiming that switching to Haze is the solution of all the world's
> problems. Haze can be an option for protocols not having a proper CM but
> it would be completely stupid to switch to it for XMPP: no call, no file
> transfer, no muc, no desktop sharing...

Being able to log in is more important than anything else.

>> * 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.
>
> I agree that Haze could be used. Actually we're going to switch to Haze
> for MSN accounts in 3.4 as butterfly (and the other Python CMs) are not
> properly maintained and lake all the recent Telepathy APIs.

Makes sense.

>> * telepathy-gabble
>>
>> Seems to have proxy support  through GIO, but there are issues.
>
> Which issues exactly? Are there in Gabble? in GIO?

All the issues related to libproxy for starters, like not being able
to get a popper configuration with GNOME 2, and thus all the DE's that
already rely on those GConf settings, like Xfce. And all the issues
related to GNOME 3 configuration, like the fact that all
authentication is missing.

Plus, in my machine, even with GNOME 3's control center it's confusing
what should be the settings, and even when I put exactly the right
settings, it takes a long long time to log in.

>> * telepathy-idle
>>
>> No proxy support on the horizon.
>
> Idle has switched to GIO (fdo #37145) so SHOULD be at the same state as
> Gabble.

Yes, many things should be in certain way *in theory*, but then why is
fdo #12376 still open? Because nobody has actually tried *in
practice*.

Here, let me try... Nope... doesn't work. What a surprise.

>> * telepathy-rakia
>>
>> No proxy support on the horizon.  Or bug report about it.
>
> Please feel free to open one.

Why would I do that? As I stated multiple times, this is not *needed*
to solve the issue at hand.

You can disagree all you want with me, but the fact of the matter is
that after more than 3 years this bug has existed, the issue remains
there, and users are *completely* prevented to use Empathy.

This is the problem going the GNOME way of trying to have everything
perfectly. When is that going to happen? 2020?

--
Felipe Contreras

3 comments hidden view all 170 comments

Nice little workaround for IRC, and hence for idle (at least it does the job at a pinch): http://wiki.tcl.tk/3125

graemev (graeme-launchpad) wrote :

Just Installed 11.10 and it's STILL using empathy ... and it STILL doesn't work ... this must be 3 years since this 1st happened. At the very least Ubuntu could switch back to Pidgin , which does work.

ubck (now) wrote :

Recently installed 12.04 LTS and I see this issue.
When I don't use a proxy at home, I can connect to gtalk and yahoo but the same configuration doesn't work when using a proxy at work.

LinkedIn
------------

Bug,

I'd like to add you to my professional network on LinkedIn.

- Tomas

Tomas Scally
Software Engineer at INSSJP
Argentina

Confirm that you know Tomas Scally:
https://www.linkedin.com/e/-vj0ici-habulm1l-3b/isd/9898799252/naWwixxu/?hs=false&tok=1bOQ3ATN_-wBw1

--
You are receiving Invitation to Connect emails. Click to unsubscribe:
http://www.linkedin.com/e/-vj0ici-habulm1l-3b/heVhI-18DALiOIbXiaX7rqK8rGC5NUBwKlnX9cW/goo/304889%40bugs%2Elaunchpad%2Enet/20061/I3302755741_1/?hs=false&tok=2A2XukvNH-wBw1

(c) 2012 LinkedIn Corporation. 2029 Stierlin Ct, Mountain View, CA 94043, USA.

graemev (graeme-launchpad) wrote :

Wow that linkedIn spam is nasty ... sneaks in like it's from LinkedIn.

Anyhow situation appears to be that Empathy state they cannot run in the environment offered by Ubuntu, other IM clients can run. The bug should move to Ubuntu distro ... "you are using an IM client which reports it's not supported in the given environment" ..so either Ubuntu are willing to fix the environment or they must choose a client which will work?

(In reply to comment #2)
> The real fix would
> probably be making idle use glib's GSocketClient to leverage the recently
> added transparent proxy capabilities

This should now work (since 0.1.11), but that wasn't what was requested:

(In reply to comment #0)
> There's several bouncers that
> support socks or by addition of a custom command "CONNECT" in the IRC
> protocol that is used for selecting the target network that should be
> used.

Support for these would require use of a non-system-wide proxy.

Michael (michaeljt) wrote :

People affected by this might want to look at using redsocks and iptables to set up a transparent system proxy configuration. I have done that and am more and more convinced that that is the way to go, rather than making individual applications do proxy support.

(In reply to comment #3)
> (In reply to comment #0)
> > There's several bouncers that
> > support socks or by addition of a custom command "CONNECT" in the IRC
> > protocol that is used for selecting the target network that should be
> > used.
>
> Support for these would require use of a non-system-wide proxy.

For the SOCKS case, Bug #70333 outlines one possible way to achieve that. I don't think any of the Telepathy maintainers are likely to implement that any time soon, but I'd review patches.

robertsms (robertsms) wrote :

@Michael (michaeljt)
I have met the same problem for a long time. Could you give me a alternative solution please?
I do not quite understand how to setup the tsocks or iptables to solve the problem. Thank you!

Michael (michaeljt) wrote :

@Robert (robertsms)
I'm afraid I haven't really explored other ways of doing this. Anyone else? Otherwise you will probably want to look at the "redsocks" documentation.

I don't have this problem anymore since I am not forced to use proxy now.
Sorry. I used to use pidgin as a work around.
Cheers
18 paź 2013 05:36 "robertsms" <email address hidden> napisał(a):

> @Michael (michaeljt)
> I have met the same problem for a long time. Could you give me a
> alternative solution please?
> I do not quite understand how to setup the tsocks or iptables to solve the
> problem. Thank you!
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> 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
>

Quentin (qvandekerckhove) wrote :

Hello,

Empathy works fine for me with a proxy when I setup only HTTP and HTTPS
proxy settings of the ubuntu network proxy.

On Fri, Oct 18, 2013 at 11:17 AM, Michal <email address hidden> wrote:

> I don't have this problem anymore since I am not forced to use proxy now.
> Sorry. I used to use pidgin as a work around.
> Cheers
> 18 paź 2013 05:36 "robertsms" <email address hidden> napisał(a):
>
> > @Michael (michaeljt)
> > I have met the same problem for a long time. Could you give me a
> > alternative solution please?
> > I do not quite understand how to setup the tsocks or iptables to solve
> the
> > problem. Thank you!
> >
> > --
> > You received this bug notification because you are subscribed to the bug
> > report.
> > 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
> >
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> 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
>

Displaying first 40 and last 40 comments. View all 170 comments or add a comment.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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