konqueror really slow

Hi,

on lots of pages (eg. freebsd.org), konqueror is really slow
like hanging at 
16 of 18 pictures for a long time (means: firefox get the
_whole_ page during 
that time that konqueror waits).

Anything that can be done about it, like setting some
timeout parameters to 
common sense values?
Why is the page not shown during load? This would at least
give a better 
visual feedback. This would allow clicking on the next link
instead of 
waiting for some d*** picture...

HS


-- 
To UNSUBSCRIBE, email to debian-kde-REQUESTlists.debian.org
with a subject of "unsubscribe". Trouble?
Contact listmasterlists.debian.org

Hendrik Sattler schrieb:
> on lots of pages (eg. freebsd.org), konqueror is really
slow like hanging at 
> 16 of 18 pictures for a long time (means: firefox get
the _whole_ page during 
> that time that konqueror waits).
>
> Anything that can be done about it, like setting some
timeout parameters to 
> common sense values?
Hi,

I've been wondering about this for quite a while, but
assumed myself to 
be the only one affected. I observe it on both sarge (kde
3.3.2) and on 
a notebook running edge (kde 3.5.3).

I like Konqueror and would use it more often, if it
performed better. 
Currently I'm even accessing my router's web-interface via
mozilla, 
because with konqueror it takes atleast four times longer
for pages to show.

Cheers, Marc


-- 
To UNSUBSCRIBE, email to debian-kde-REQUESTlists.debian.org
with a subject of "unsubscribe". Trouble?
Contact listmasterlists.debian.org

On Sunday 16 July 2006 2:47 pm, Marc Bantle wrote:

> > Anything that can be done about it, like setting
some timeout parameters
> > to common sense values?

> I've been wondering about this for quite a while, but
assumed myself to
> be the only one affected. I observe it on both sarge
(kde 3.3.2) and on
> a notebook running edge (kde 3.5.3).
>
> I like Konqueror and would use it more often, if it
performed better.
> Currently I'm even accessing my router's
web-interface via mozilla,
> because with konqueror it takes atleast four times
longer for pages to
> show.

I hadn't thought to try Firefox.  I wonder if it would make
any difference?

I've seen a slowdown now and again, but it seems to be
network related 
somehow.  My ISP's network was on the fritz yesterday, and
it took an 
inordinate amount of time for pages from any of my local web
interfaces (on 
this box, or any on my LAN) to come up.

It feels kind of like the bad old days when there was some
screwy problem with 
localhost not getting set up correctly, or something like
that.

If that ever happens again, I'll go try Firefox, and see if
it makes a 
difference.  This screwy localhost or whatever thing I'm
thinking of, but 
can't quite remember, used to affect File->Open dialogs
and such too, and was 
KDE wide, anytime KDE used KURL for something, which is
frequently.

I'm running 3.5.3 myself, and freebsd.org just came up in
no time flat.  I 
hadn't been there before, so it wasn't cached.

-- 
D. Michael 'Silvan' McIntyre  ----   Silvan
<dmmcintyrusers.sourceforge.net>
Linux fanatic, and certified Geek;  registered Linux user
#243621

Author of Rosegarden Companion http://ro
segarden.sourceforge.net/tutorial/


-- 
To UNSUBSCRIBE, email to debian-kde-REQUESTlists.debian.org
with a subject of "unsubscribe". Trouble?
Contact listmasterlists.debian.org

Am Sonntag, 16. Juli 2006 22:04 schrieb D. Michael
'Silvan' McIntyre:
> I hadn't thought to try Firefox.  I wonder if it would
make any difference?
>
> I've seen a slowdown now and again, but it seems to be
network related
> somehow.  My ISP's network was on the fritz yesterday,
and it took an
> inordinate amount of time for pages from any of my
local web interfaces (on
> this box, or any on my LAN) to come up.

It cannot be related to network slowdown or other network
related problem 
because stopping the loading and restarting it does not get
any more data 
than the previous try. Trying firefox immediately shows the
page, strange, 
isn't it?
I also had this on my routers page but that was name->ip
lookup related.

I wonder if this is related to pipelining. If it is, why
isn't it implemented 
in konqueror? Can't be that hard to do and if it makes the
thing much faster, 
it would make it worth the effort.

Bad thing that firefox is not my favourite choice. I would
never use it as 
main browser as the firefox developers do not seem to have
any idea of good 
work flow (or it just does not fit my idea of it). And it's
just ugly (ups, 
must be GTK-related).

HS


-- 
To UNSUBSCRIBE, email to debian-kde-REQUESTlists.debian.org
with a subject of "unsubscribe". Trouble?
Contact listmasterlists.debian.org

On Sunday 16 July 2006 22:52, Hendrik Sattler wrote:
[Firefox]
> And it's just ugly (ups, must be GTK-related).

One of these themes for Firefox may help
http://www.polinux.upv.es/mozilla/temas.php?idioma=en

That said, I use Firefox only rarely and in my experience,
Konqueror 
(3.5.3) is snappier.

Michael

-- 
Michael Schuerig
mailto:michaelschuerig.de
http://www.schuerig.d
e/michael/


-- 
To UNSUBSCRIBE, email to debian-kde-REQUESTlists.debian.org
with a subject of "unsubscribe". Trouble?
Contact listmasterlists.debian.org

Am Sonntag 16 Juli 2006 18:47 schrieb Hendrik Sattler:
> Hi,
>
> on lots of pages (eg. freebsd.org), konqueror is really
slow like hanging
> at 16 of 18 pictures for a long time (means: firefox
get the _whole_ page
> during that time that konqueror waits).
>
> Anything that can be done about it, like setting some
timeout parameters to
> common sense values?
What nameservers are listed in your resolve.conf. If you are
behind a router 
and you listed its ip as nameserver (e.g. 192.168.1.1) and
this router 
redirects you to a real nameserver KDE programms have a
problem. Try to set 
your resolv.conf to point to the real nameserver of your
provider. If your 
resolv.conf is generated automatically and you want to be
shure that your 
prevered nameservers are on first place have a look at the
programm 
resolvconf.

Hope this helps, Konqueror is a great tool.
Cheers W. Mader

On Sunday 16 July 2006 18:47, Hendrik Sattler wrote:
> Hi,
>
> on lots of pages (eg. freebsd.org), konqueror is really
slow like
> hanging at 16 of 18 pictures for a long time (means:
firefox get the
> _whole_ page during that time that konqueror waits).
>
> Anything that can be done about it, like setting some
timeout
> parameters to common sense values?
> Why is the page not shown during load? This would at
least give a
> better visual feedback. This would allow clicking on
the next link
> instead of waiting for some d*** picture...

KDE supports ipv6 but many DNS Servers are broken and
Konqueror has to 
wait until it gets a timeout. Try to disable ipv6

htt
p://www.debian-administration.org/articles/409


Cheers,
André

On Sunday 16 July 2006 18:47, Hendrik Sattler wrote:
> Hi,
>
> on lots of pages (eg. freebsd.org), konqueror is really
slow like
> hanging at 16 of 18 pictures for a long time (means:
firefox get the
> _whole_ page during that time that konqueror waits).
>
> Anything that can be done about it, like setting some
timeout
> parameters to common sense values?
> Why is the page not shown during load? This would at
least give a
> better visual feedback. This would allow clicking on
the next link
> instead of waiting for some d*** picture...

KDE supports ipv6 but many DNS Servers are broken and
Konqueror has to 
wait until it gets a timeout. Try to disable ipv6

htt
p://www.debian-administration.org/articles/409


Cheers,
André

On Sunday 16 July 2006 18:47, Hendrik Sattler wrote:
> Hi,
>
> on lots of pages (eg. freebsd.org), konqueror is really
slow like
> hanging at 16 of 18 pictures for a long time (means:
firefox get the
> _whole_ page during that time that konqueror waits).
>
> Anything that can be done about it, like setting some
timeout
> parameters to common sense values?
> Why is the page not shown during load? This would at
least give a
> better visual feedback. This would allow clicking on
the next link
> instead of waiting for some d*** picture...

KDE supports ipv6 but many DNS Servers are broken and
Konqueror has to 
wait until it gets a timeout. Try to disable ipv6

htt
p://www.debian-administration.org/articles/409


Cheers,
André