Launchpad has imported 9 comments from the remote bug at https://bugs.freedesktop.org/show_bug.cgi?id=47960.
If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. ------------------------------------------------------------------------ On 2012-03-27T12:39:23+00:00 Ken VanDine wrote: Created attachment 59127 WOCKY_DEBUG=xmpp with contact info stripped out In my test scenario, I have a local squid proxy properly configured to handle HTTP CONNECT, tested with pidgin and it works. MS Live accounts works as well using telepathy-haze. However attempting to connect to gtalk or jabber.org accounts, according to the squid access log, never attempts to connect to the configured proxy. Downstream bug report: https://bugs.launchpad.net/ubuntu/precise/+source/telepathy-gabble/+bug/893031 Reply at: https://bugs.launchpad.net/ubuntu/+source/libproxy/+bug/893031/comments/18 ------------------------------------------------------------------------ On 2012-03-28T08:01:24+00:00 Nicilas wrote: Can you provide your system configuration, and the returned configuration as seen by libproxy: proxy xmpp-client://myserfer proxy https://myserfer HTTP Connect for bare jabber is currently not supported by libproxy (not support fro any non https:// protocols). Also, be aware that Pidgin erroneously reads the HTTP_PROXY rather then SECURE_PROXY gnome setting for doing HTTP Connect. Reply at: https://bugs.launchpad.net/ubuntu/+source/libproxy/+bug/893031/comments/20 ------------------------------------------------------------------------ On 2012-03-28T11:59:38+00:00 Ken VanDine wrote: proxy xmpp-client://myserfer direct:// proxy https://myserfer http://localhost:3128 Looking through the gabble source, I don't see anywhere that it uses libproxy, not even an includes for proxy.h. How does it interact with libproxy? Previously it had been suggested that it wasn't working because our version of libproxy in Ubuntu was too old, 0.3.x. We now have the 0.4.7, the latest and it still doesn't work. So this isn't a bug so much as it is not supported yet? Reply at: https://bugs.launchpad.net/ubuntu/+source/libproxy/+bug/893031/comments/21 ------------------------------------------------------------------------ On 2012-03-28T12:30:14+00:00 Nicilas wrote: (In reply to comment #2) > proxy xmpp-client://myserfer > direct:// > proxy https://myserfer > http://localhost:3128 > > Looking through the gabble source, I don't see anywhere that it uses libproxy, > not even an includes for proxy.h. How does it interact with libproxy? > > Previously it had been suggested that it wasn't working because our version of > libproxy in Ubuntu was too old, 0.3.x. We now have the 0.4.7, the latest and > it still doesn't work. > > So this isn't a bug so much as it is not supported yet? Gabble uses a library called Wocky which is base on GIO. And GIO has a libproxy and gnome plugin. I usually suggest using libproxy for distro that can run both KDE and Gnome on the same install, the Gnome plugin ignores the environment. Currently the support for HTTP Connect is very restricted because the GIO developers did not agree it was a correct way of doing generic socket proxying. Here is how you can make it work. First thing to know is that wocky will do HTTP Connect only when you are running in Old SSL mode. Which mean the first thing you do is an TLS handshake (so it cannot be differentiated from a HTTPS connection). Then you need a correct configuration, which you have. If you are using a google account configured with older version of Empathy, I suggest to remove it and re-create it. This will add the fallback-servers parameter to your account. Note that HTTP Connect is never the first, so connection may take a little while depending on how fat the other attempts fails. You can check the params using mc-tool show ... Here's what you should see: (GStrv) fallback-servers = ["talkx.l.google.com", "talkx.l.google.com:443,oldssl", "talkx.l.google.com:80"] Unless someone broke the fallbacks, wocky will try the server talk.google.com (use to do SRV, but was changed recently). In case of failure, it will fallback to talkx.l.google.com using normal TLS, if it fails again, it will try talkx.l.google.com:443 using OLD SSL mode, and if that still fails it will try cleartext on port 80 (I think this one always fails these days, not sure). In the future, libproxy should try HTTP Connect for any type of connection, and have a direct fallback, but that couldn't be done without changing libproxy internals a lot. Also, the HTTP Connect GLIB plugin should be provided by libsoup. Feel free to contribute if you have time. Reply at: https://bugs.launchpad.net/ubuntu/+source/libproxy/+bug/893031/comments/22 ------------------------------------------------------------------------ On 2012-03-28T12:42:19+00:00 Ken VanDine wrote: My account does have the fallback-servers set with oldssl, but does this mean that if it can connect without going through the configured proxy it will do that? I am not actually required to use the proxy to connect, but set it up just for testing this bug. If it just ignores the proxy setting because it can connect without it, my test environment isn't really good for validating this bug. Reply at: https://bugs.launchpad.net/ubuntu/+source/libproxy/+bug/893031/comments/23 ------------------------------------------------------------------------ On 2012-03-28T12:50:52+00:00 Nicilas wrote: (In reply to comment #4) > My account does have the fallback-servers set with oldssl, but does this mean > that if it can connect without going through the configured proxy it will do > that? With the current implementation, yes. > > I am not actually required to use the proxy to connect, but set it up just for > testing this bug. If it just ignores the proxy setting because it can connect > without it, my test environment isn't really good for validating this bug. Right, to test it, you need to isolate yourself from the internet. Maybe you can try by disable dns (comment the nameserver lines in resolve.conf) and set your proxy server dns (if you have one) in /etc/hosts. If the proxy is on the same host, well at least you will see the proxy being called even if it fails in the end. Reply at: https://bugs.launchpad.net/ubuntu/+source/libproxy/+bug/893031/comments/24 ------------------------------------------------------------------------ On 2012-04-03T15:21:40+00:00 Nicilas wrote: Should I conclude this bug was invalid ? Reply at: https://bugs.launchpad.net/ubuntu/+source/libproxy/+bug/893031/comments/26 ------------------------------------------------------------------------ On 2012-04-24T08:06:11+00:00 Ken VanDine wrote: Created attachment 60534 All-24-04-12_11-03-19.log I tried that, with no nameserver set. Other apps work fine through the proxy, firefox, ubuntuone, etc. But when connecting with empathy it still doesn't even try to hit the proxy. I am attaching the log. Reply at: https://bugs.launchpad.net/ubuntu/+source/libproxy/+bug/893031/comments/29 ------------------------------------------------------------------------ On 2019-12-03T19:56:38+00:00 Gitlab-migration wrote: -- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/telepathy/telepathy-gabble/issues/221. Reply at: https://bugs.launchpad.net/ubuntu/+source/libproxy/+bug/893031/comments/42 ** Changed in: telepathy-gabble Importance: Unknown => Medium ** Bug watch added: gitlab.freedesktop.org/telepathy/telepathy-gabble/issues #221 https://gitlab.freedesktop.org/telepathy/telepathy-gabble/issues/221 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libproxy in Ubuntu. https://bugs.launchpad.net/bugs/893031 Title: Empathy is not working behind the proxy servers SINCE Ubuntu 11.10 Status in telepathy-gabble: Unknown Status in libproxy package in Ubuntu: Fix Released Status in telepathy-gabble package in Ubuntu: Fix Released Status in libproxy source package in Precise: Fix Released Status in telepathy-gabble source package in Precise: Confirmed Bug description: Empathy is unable to connect behind the proxy servers whatever way we try. It doesn't utilize the proxy settings given globally to the system. There is no proxy option in the program also. I tried connecting to empathy from Ubuntu 11.10 in three systems behind a proxy server and in all cases it failed. I tried all of the following but none worked: 1. Changing settings with gconf-editor ( Walk down the tree to system -> http_proxy . Search for use_http_proxy and check it. ) Even after doing that there is no change in behaviour of empathy 2. gksudo gedit /etc/bash.bashrc export http_proxy=http://proxyhost:port/ export ftp_proxy=http://proxyhost:port/ save and exit This also didnt help anything 3. Using tsocks and editing its config files also. In that case the result was: "tsocks dbus-launch empathy" fails to retrieve the accounts list. "tsocks empathy" launches empathy, but it is unable to connect.. Please generate a patch for this problem and release new version of the program. To manage notifications about this bug go to: https://bugs.launchpad.net/telepathy-gabble/+bug/893031/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
