> So, I'm now running beta-1 on my box, and enjoying the hell out of all the > nifty new options (and speedups, thanks!). All of the crash bugs I was > having with alpha2 in the kcontrol panel are gone, they all work (pretty > much, I have a reproducible bug I'll be filing in a minute) flawlessly. > However, konq crashes tons more than it did, and frequently the kio_http > hangs and I have to manually kill it and restart konq before I can continue > surfing. The error I get is the exact same one I got before when going > through an authenticating proxy (http protocol died unexpectedly, pre 2.1.2 > days), but in this case it works great for a few minutes, then dies. Is > anyone else seeing this, or is this a case of me being screwed by our > auth_proxy? Or (gulp) can this be solved by blowing away my .kde dir? I'm > crossposting this with debian-kde and kfm-devel, as I'm not yet sure if this > is a packaging issue, or a "hard core" kde issue. If there's something else > I can do, please tell me and I'll do it. If it's of interest, if I run > konqueror from the command line, it outputs this when it errors: > > kio (KRun): ERROR: 0x83ad520 ERROR 43 The process for the > http://slashdot.org protocol > died unexpectedly. > > and it won't work again until I kill the kio_http slave (after closing konq). > Here's a listing of the beta1 packages I still have installed, followed by > the alpha2 (just in case that's screwing it up somehow:
I'm glad to hear that your having a mostly good experience with the beta. I personally have not had any problems with konq however I do not use a proxy from here. I'll set one up so that I can do some tests... Ivan -- ---------------- Ivan E. Moore II [EMAIL PROTECTED] http://snowcrash.tdyc.com GPG KeyID=90BCE0DD GPG Fingerprint=F2FC 69FD 0DA0 4FB8 225E 27B6 7645 8141 90BC E0DD
