@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.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to empathy in Ubuntu.
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 robert...@gmail.com napisał(a):
@Michael (michaeljt)
I have met the same problem for a long time. Could you give me a
alternative solution
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 304...@bugs.launchpad.net wrote:
I don't have this problem anymore since I am not forced to use proxy now.
Sorry. I used to use
@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 a member of Desktop
Packages,
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.
--
You received this bug
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
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.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
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.
--
You received this bug notification because you are a member of Desktop
Packages, which is
Nice little workaround for IRC, and hence for idle (at least it does the
job at a pinch): http://wiki.tcl.tk/3125
--
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
@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?
--
You received this bug notification because you are a member of
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.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to empathy
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.
*
Le mercredi 30 novembre 2011 à 15:55 +, 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
On Wed, Nov 30, 2011 at 6:37 PM, Guillaume Desmottes gdesm...@gnome.org wrote:
Le mercredi 30 novembre 2011 à 15:55 +, 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
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
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
--
You received this bug notification because you are a
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
@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.
@hggdh2:
Thank you for the clarification.
Have a good day.
--
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
still the same situation with Empathy 3.2.0.1 and Ubuntu 11.10
** Changed in: empathy (Ubuntu)
Status: Invalid = Confirmed
--
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
Not working here Empathy 3.2.0.1 Ubuntu 11.10
!!!
--
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
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
22 matches
Mail list logo
