I have to use a HTTP proxy at work, normally configured by an "autoconfig file" in the KDE settings and entries in /etc/environment. In both places I have set exceptions for the internal address range, but according to Wireshark Telepathy still tries to connect through the proxy.
Could it be this: https://forum.kde.org/viewtopic.php?f=230&t=110776&p=262890#p262890 David
Unfortunately not... there was no suspicious or outdated data in gsettings for the proxy, but I removed the whole section anyways without effect. Is there a good way to get some debugging data from the Jabber login process for Telepathy?
Yes. run ktp-debugger. Look at the tab marked gabble. Feel free to attach those logs but note that it may contain personal information (friends + messages) but never passwords. Also the account can have a custom proxy assigned; you can check that in the GUI; or mc-tool list + mc-tool show.
Created attachment 87930 [details] ktp-debugger output during login attempt
I checked the account, as far as I can see there is no custom http-proxy set.
As far as I can tell, Jabber advanced settings aren't being passed to telepathy at all. At least, none of the ones I set in the KDE UI have any noticeable effect, and they don't show up in Empathy's UI (changing the settings in Empathy's UI does seem to have an effect). Note that I can't tell whether KDE is reading telepathy settings properly because of Bug 351785.
Alex - I assume you're using 15.xx version, right? Then your issue is different, can I ask you to try changing the settings with Empathy and then do "mc-tool dump" and post the output? Feel free to replace any sensitive data in there.
It's actually working for me now with latest master. It might have been related to Bug 351785.
Ah, so setting a custom proxy now works, correct? Ie. your jabber advanced settings make it to telepathy and everything works as expected with a proxy, right?
Sorry, I may have got confused as to what bug I was posting on. I haven't actually tried using a proxy at all - I originally commented because I was having issues getting other settings to be recognised ("ignore SSL errors" in particular), and *that* issue has now been resolved.
Thank you for the bug report. As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists. If this bug is no longer persisting or relevant please change the status to resolved.