On Friday 21 September 2001 08:04, David Bishop wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On Friday 21 September 2001 05:58 am, Volker Schlecht wrote: > > A few weeks ago, I reported bug #108698 against konqueror, which has > > been tagged unreproducible by Ivan. I have since waited for 2.2.1 to > > be released, hoping that they would silently fix it. > > > > The bug report only mentions viewing the contents of .tar.gz's, > > however currently, using konqueror 2.2.1 from unstable (on an > > otherwise woody system) that happens with normal directories also. > > > > I have checked bugs.kde.org to see if such a problem had been already > > reported, but I couldn't find any mention of it. > > > > Does anyone here have the same problem, or any suggestions by what it > > could be caused? > > Just tested on directory with 8 html files, no problem. Took a couple > seconds to generate previews, but nothing serious, and immediately cpu > usage dropped back to normal. Just tried with a .tar.gz file as well, > worked even faster than I expected. This is on a pii 350, nothing special > (oh, and I'm straight sid). Sorry :-) > > - -- > "To me vi is Zen. To use vi is to practice zen. Every command is > a koan. Profound to the user, unintelligible to the uninitiated. > You discover truth everytime you use it." [EMAIL PROTECTED] > > [EMAIL PROTECTED] > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.0.6 (GNU/Linux) > Comment: For info see http://www.gnupg.org > > iD8DBQE7q1b314eKrYdPXKkRAlU8AKCQqsJ7wkKtRDzkKXA7cv8pgcam4wCeMW9/ > 1AJQXk9h+HUMZ9kg2X9bxN0= > =sgG2 > -----END PGP SIGNATURE-----
I also have had problems with konqueror loading up and puking. The problem here was loading a webpage I had locally with 7-10 jpg pix inserted into the page. Konq started to load and basically locked up the box. Like you, it would free for seconds and I could usually escape back to console and kill x from there. It still happens. Konq will also hog resources on basic pages like http://lwn.net, I noted this when I noticed my setiathome client drop to less then 4% cpu. At one point, I ended up killing x and restarting to free up cpu usage. I can smirf with opera and it is better. Yet this seems to be irregular. I can't reproduce these results often. I'm now running woody, and I guess I'll wait and see what 2.2.1 will bring here. gl and tatah -- Jaye Inabnit\ARS ke6sls\/A GNU-Debian linux user\/ http://www.qsl.net/ke6sls If it's stupid, but works, it ain't stupid. I SHOUT JUST FOR FUN. Free software, in a free world, for a free spirit. Please Support freedom!
