Comment 2 for bug 131767

I've had this same problem on two different machines now. Both were laptops using wireless, and disabling cache fixed the problem.
On one machine, konqueror would work if the ethernet (eth0) cable was plugged in but not if it was running on wireless (wlan0). On the other machine, it worked with ethernet (eth0 again) and the madwifi driver (ath0) but not the ndiswrapper driver (wlan0). This leads me to believe that the interface name is somehow important with this bug(?)

Note that firefox works fine in all cases.