Bug 69347 - name resolving hangs kdesktop for long time
Summary: name resolving hangs kdesktop for long time
Status: CLOSED UNMAINTAINED
Alias: None
Product: kdesktop
Classification: Miscellaneous
Component: minicli (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: David Faure
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-11-30 14:55 UTC by lenar
Modified: 2009-01-02 20:26 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description lenar 2003-11-30 14:55:41 UTC
Version:           tundmatu (using KDE 3.1.93 (CVS >= 20031028),  (testing/unstable))
Compiler:          gcc version 3.3.2 (Debian)
OS:          Linux (i686) release 2.6.0-test10-mm1

When one enters something in ALT+F2 window and does it slowly enough,
kdesktop starts to resolve the address partly enetered. For example
I want to go to www.slashdot.org I enter www.sl and when I'm not quick enough
and do not enter 'a' my kdesktop hangs trying to resolve www.sl which is not resolvable
but takes quite a time to come to this conclusion. Only way to do something
is kill kdesktop and rerun it or wait some half a minute or so.

Whole kdesktop also hangs for a long time if I enter ., (dot comma) in that box. Don't know why is that.

Anyway the name resolving should not be interface-blocking as it seems to be right now.
This destroys responsivness in case I'm not using local dns cache or try to enter some
rarely used address from the other side of the world which takes long time to resolve.
Comment 1 Thiago Macieira 2003-11-30 18:37:33 UTC
I can't reproduce. No name lookups are tried when I enter "www.sl" on the minicli.

Anyways, please check your DNS settings. Those lookups shouldn't take long to report errors, even if they are invalid names:

$ time host www.sla
Host www.sla not found: 3(NXDOMAIN)

real    0m2.073s
user    0m0.003s
sys     0m0.002s
$ time host www.sl
Host www.sl not found: 3(NXDOMAIN)

real    0m0.891s
user    0m0.003s
sys     0m0.004s

Reopen if you can provide more information.
Comment 2 lenar 2003-11-30 18:49:59 UTC
Not reopening yet until I get newer build, but nevertheless those resolves happen here and even 'real 0m2.073s' is too much if it blocks my input. if this happens concurrently it would be ok and invisible from me.

And it took time here for www.sl because name resolver was not able to get answer from some name server and it just waited unil it timed out.

Right now it gives the same answer as yours in about 1-2 sec. But the situation where all authoritive name servers are down for a domain (and the information is not cached anywhere) is not so uncommon and if this blocks my interaction with my computer - it's bad.

Ok, let's wait until I can test on newer build.
Comment 3 lenar 2004-01-03 16:27:36 UTC
Got KDE CVS from 20040104. minicli hanging while resolving names still happening. Right now for example for www.tigma.ee (it might come back before anybody can test).

$ host www.tigma.ee # gives this:
;; connection timed out; no servers could be reached

after many-many seconds.

Me thinks minicli should do name resolving in special thread ... otherwise
it locks up (can't interact with user) anyway (be it second, two or ten).
Comment 4 lenar 2004-01-03 16:28:33 UTC
And reopening. This is really a problem (mainly usability).
Comment 5 FiNeX 2008-12-10 02:06:49 UTC
Kdesktop is no more mantained. Fortunatly this bug seems not to be valid for KDE 4. Please reopen if this bug is not a kdesktop one (and it is not solved) or it can be reproduced on KDE 4.
Comment 6 FiNeX 2009-01-02 20:26:10 UTC
Bug closed. Kdesktop is no more mantained.