Version: 4.6 (using KDE 4.6.2) OS: Linux When I try to use the PAC file for proxy configuration which our team uses at work, it causes freezing in Firefox, Rekonq, Choqok, and Plasmoids like the Weather Forecast plasmoid. We have a few different PAC files here at work and they all cause this issue. It is obvious that this proxy configuration is being shared system wide. Strangely enough Google Chrome is immune. These applications do not crash, but they hang for 30-40 seconds at a time whenever I try to access a web page. As soon as I go back and remove the PAC file and tell KDE to "Connect directly to the Internet" the problem goes away. Reproducible: Always Steps to Reproduce: In Network Settings, tell KDE to use a PAC file and apply the change. Actual Results: After applying this change, these apps would immediately suffer from the freeze ups.
ehh... why would configuring PAC file in KDE's proxy configuration cause Firefox to freeze. Firefox does not use KDE's proxy configuration at all. It has its own code for connecting to the network. So if you have a problem when you configure Firefox with the PAC file and you also have the same issue in KDE, then the issue is elsewhere. Unless I misunderstood your report here...
Firefox with the firefox-kde-support (Kubuntu) package is able to use the gloabl KDE proxy configuration from the looks of it. You are correct however in that when I use Firefox's internal proxy configuration I can use the PAC file and the other browsers are not affected. This is the workaround I am using currently. Rekonq, Choqok, and even the Weather plasmoid are affected by this whenever I try to use a PAC file with the KDE global proxy configuration.
Is this still an issue with KDE 4.7 and up ? The proxy code, especially the one related to PAC has been vastly improved in KDE 4.7.
Cannot duplicate. Feel free to reopen this ticket if the issue persists in KDE 4.7 and up. As stated in comment #3, the PAC support in KDE has been completely rewritten for KDE 4.7 and up.