Bug 77916 - konqueror hangs and blocks kde
Summary: konqueror hangs and blocks kde
Status: RESOLVED WORKSFORME
Alias: None
Product: konqueror
Classification: Applications
Component: khtml (show other bugs)
Version: unspecified
Platform: Debian testing Linux
: NOR normal
Target Milestone: ---
Assignee: Konqueror Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-03-18 14:08 UTC by Elias Humbolt
Modified: 2005-02-26 01:54 UTC (History)
0 users

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 Elias Humbolt 2004-03-18 14:08:12 UTC
Version:            (using KDE KDE 3.2.1)
Installed from:    Debian testing/unstable Packages
OS:          Linux

I could not find out when this hang appears exactly, but sometimes konqueror hangs and blocks whole of kde. I guess this could possibly have something to do with url completion, since I think to remember, that every time the problem appeared, the drop down with the same url like in the location bar was still opened. Perhaps it helps too, that I seem to remember, that there always was only that single URL in the drop down, that was in the location bar either.
The hang prevents me from switching back to other apps and even from entering hotkeys like ALT-F2 for starting apps by hand (xkill). I still don't get back control, when I try to kill konqueror from the console - yes, I can use ALT-STRG-F1 to get a console - but that is not for sure, since I don't know exactly which kdeinit processes to kill.
Comment 1 Jan Schaefer 2004-03-18 19:01:00 UTC
Sorry, but could you please describe this bug a little further?
What exactly did you do before Konqueror hangs?
Guessing from you text, you were writing an URL in the location bar, right?
Could you try to start Konqueror from the console, and post the output before it hangs?
Comment 2 Elias Humbolt 2004-03-19 10:12:08 UTC
I have done 2 things lately on my system and have not experienced that bug any 
more. Deleting cache, history and url history and starting a dns forwarder in 
resolv.conf, that was not running.

perhaps this bug derived from still having cache, history and url history, 
entries from 3.1.5 or from having that invalid dns entry in resolv.conf I 
deleted lately.

Sorry, that can't give you more detail, I hope I can, when the bug reappears, 
but I hope it does not. I would propose you close the bug, if you can't track 
down a reason for it by what I've told you so far and I reopen it, if it 
reapears and I got more Information then.

thank you for your quick response and sorry, that I can't give you more detail 
than this.
elias

Comment 3 Frederik Dannemare 2004-03-23 14:48:45 UTC
Could the behavior seen here actually be related to bug #74070? Elias, are you sure you haven't seen a complete KDE freeze using other apps than Konqueror? And how long did you actually give KDE, before manually killing processes? 

I am experiencing freezes (but they are temporarily - sometimes as much as a whole minute, though) when using different apps (Debian Sid, KDE 3.2.1). See #74070 for further info.
Comment 4 Elias Humbolt 2004-03-23 15:31:12 UTC
Am Dienstag, 23. März 2004 14:48 schrieb Frederik Dannemare:
> ------- You are receiving this mail because: -------
> You reported the bug, or are watching the reporter.
>
> http://bugs.kde.org/show_bug.cgi?id=77916
>
>
>
>
> ------- Additional Comments From tux sentinel dk  2004-03-23 14:48 -------
> Could the behavior seen here actually be related to bug #74070? Elias, are
> you sure you haven't seen a complete KDE freeze using other apps than
> Konqueror? And how long did you actually give KDE, before manually killing
> processes?
>
> I am experiencing freezes (but they are temporarily - sometimes as much as
> a whole minute, though) when using different apps (Debian Sid, KDE 3.2.1).
> See #74070 for further info.

bug #74070 sounds familiar. but as I noted above, This behavior disapeared 
lately after changing resolv.conf flushing history and cache. I guess it was 
a dead nameserver in resolv.conf that caused that freeze.

Well sometimes the freeze was only for several seconds (~10-20) but the other 
day it freezed until I killed konqueror (I didn't wait for the freeze to 
disappear for longer than a minute I guess). I'll try to add a dead dns to my 
resolv.conf and will report what happens now.

Comment 5 Jo Øiongen 2004-07-15 11:14:25 UTC
If there is not more to work on here shall we set this bug as resolved with "works for me"?

Cheers Jo
Comment 6 Germain Garand 2005-02-26 01:54:20 UTC
Works for the reporter after fixing a DNS issue, 
not confirmed by others in a year => WORKSFORME