Description of problem:
No matter how I defined proxy, no connection is made with
Konqueror. Local web addresses work ok.
Version-Release number of selected component (if applicable):
KDE: 4.0.3 (KDE 4.0.3)
Konqueror: 4.0.3 (KDE 4.0.3)
Steps to Reproduce:
1. Define proxy
2. Try use konq. to connect web
Server are not found
Firefox with same proxy settings works.
Seems to be upstream bug, see URL, though I report it anyway here too.
The non-duplicate upstream bug: http://bugs.kde.org/show_bug.cgi?id=155707
*** Bug 444991 has been marked as a duplicate of this bug. ***
There's a patch in the upstream bug report, I'll try a test build with that
patch, let's see how it goes.
Actually there are (at least) 2 patches:
* a kdelibs patch:
Several versions of that patch by different authors, this is the latest, not
sure if it's the best though.
* a kdebase patch to fix the proxy dialog in Konqueror:
We may want some of the changes from this (also against kdelibs) too:
> We may want some of the changes from this (also against kdelibs) too:
Actually we don't need this one. The changes to kio_http are superseded by the
first patch I listed:
and the other changes have been already applied in KDE 4.0.4.
New version of the kdelibs patch by Sergey Saukh:
> don't drop connection on post requests;
> close connection if request's proxy url differs from state's (previous
> * a kdebase patch to fix the proxy dialog in Konqueror:
This one was actually applied months ago (before 4.0 branched):
so only the kdelibs patch is relevant.
Should be fixed in kdelibs-4.0.4-3.fc9:
kdepimlibs-4.0.4-1.fc9, kdesdk-4.0.4-2.fc9, kdebase-runtime-4.0.4-1.fc9, kdeartwork-4.0.4-1.fc9, kdeadmin-4.0.4-1.fc9, kdemultimedia-4.0.4-1.fc9, kdegraphics-4.0.4-1.fc9, kde-l10n-4.0.4-1.fc9, kdeedu-4.0.4-2.fc9, kdebase-workspace-4.0.4-4.fc9, kdenetwork-4.0.4-2.fc9, kdeutils-4.0.4-1.fc9, kdetoys-4.0.4-1.fc9, kdelibs-4.0.4-4.fc9, kdegames-4.0.4-2.fc9, kdebindings-4.0.4-1.fc9, kdeaccessibility-4.0.4-1.fc9, kdebase-4.0.4-2.fc9 has been pushed to the Fedora 9 testing repository. If problems still persist, please make note of it in this bug report.
If you want to test the update, you can install it with
su -c 'yum --enablerepo=updates-testing update kdepimlibs kdesdk kdebase-runtime kdeartwork kdeadmin kdemultimedia kdegraphics kde-l10n kdeedu kdebase-workspace kdenetwork kdeutils kdetoys kdelibs kdegames kdebindings kdeaccessibility kdebase'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F9/FEDORA-2008-3664
kdebase-workspace-4.0.4-4.fc9, kdebase-4.0.4-2.fc9, kde-l10n-4.0.4-1.fc9, kdesdk-4.0.4-2.fc9, kdemultimedia-4.0.4-2.fc9, kdelibs-4.0.4-4.fc9, kdeedu-4.0.4-2.fc9, kdebase-runtime-4.0.4-1.fc9, kdepimlibs-4.0.4-1.fc9, kdenetwork-4.0.4-2.fc9, kdegraphics-4.0.4-1.fc9, kdeaccessibility-4.0.4-1.fc9, kdeartwork-4.0.4-1.fc9, kdeutils-4.0.4-1.fc9, kdebindings-4.0.4-1.fc9, kdetoys-4.0.4-1.fc9, kdegames-4.0.4-2.fc9, kdeadmin-4.0.4-1.fc9 has been pushed to the Fedora 9 stable repository. If problems still persist, please make note of it in this bug report.
I have responded to http://admin.fedoraproject.org/updates/F9/FEDORA-2008-3664,
but I thought I would put it here as well. The fixes do allow my konqueror to
now be able to use the web proxy, but it spins up kded4 process to near 100%
during the request, and it can be painfully slow compared to firefox. It
actually causes several things within the KDE interface to become unresponsive
while it is processing the proxy request and subsequent download of the
Thanks for your feedback, I forwarded it to the upstream bug.
While the high CPU use is a problem left to be fixed, this is definitely better
than proxies not working at all. ;-)
Sergey Saukh asks at http://bugs.kde.org/show_bug.cgi?id=155707#c49 :
> Such strange behaviour of kded4 can be caused by two modules - favicons and
> proxyscout. Does he use proxy autoconfiguration? If he does, does manual
> setting of proxy help?
(The best way of communicating is probably to reply upstream directly so I
don't have to copy&paste messages back and forth. ;-) )
Norman R. Weathers: Ping?
We're still waiting for an answer to upstream's question.