Comment 150 for bug 304889

Revision history for this message
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.