Version: 4.1.1 (KDE 4.1.1) "release 31.2" (using 4.1.1 (KDE 4.1.1) "release 31.2", KDE:KDE4:Factory:Desktop / openSUSE_11.0) Compiler: gcc OS: Linux (i686) release 2.6.25.11-0.1-pae Konqueror does not quit properly when I close the window or do File->Quit (Ctrl+Q). Though its window gets closed, its process remains live and I've to kill it through system monitor else (all) the session(s) get(s) restored next time I login. By restored I mean that even after login Konqueror processes are started but not UI is shown and I cannot use them. This only happens if I open a web page; i.e. if I use Konqueror for file browsing (or do nothing with it, just open/close) it quits... really.
Just wanted to add that this happened with 4.1.0 also.
I bet this is a duplicate of bug 170461 that I reported yesterday. Please check the following: If you start konqueror without any arguments, then visit a webpage, then close it, does it quit? Expected behavior would be to quit. Also, if you start konqueror in the command line with a url as an argument ("konqueror www.kde.org") and close it, will it quit? Expected behavior would be not to quit (due to bug 170461).
(In reply to comment #2) > I bet this is a duplicate of bug 170461 that I reported yesterday. Please check > the following: > > If you start konqueror without any arguments, then visit a webpage, then close > it, does it quit? Expected behavior would be to quit. Started Konqueror by "konqueror&" and opened a web page... it did not quit. > > Also, if you start konqueror in the command line with a url as an argument > ("konqueror www.kde.org") and close it, will it quit? Expected behavior would > be not to quit (due to bug 170461). > Started Konqueror by "konqueror www.kde.org&" and closed it... it quited. (Both cases tried 3 times)
hmm... strange, it seems like exactly the opposite behavior than in bug 170461. Another question, do you happen to have the javascript debugger enabled? There was also bug 169881, which could be related.
At least the konqueror settings dialog is saying that the "Enable debugger" is not checked.
*** This bug has been marked as a duplicate of bug 167826 ***
Not a duplicate of bug 167826. It's actually caused by the patch for bug 169881 (see details there).
Mark this as a dupe of the right bug. *** This bug has been marked as a duplicate of bug 170461 ***