Since upgrading to 4.9.2, I've found that konqueror doesn't want to close. If I simply run "konqueror" from a konsole window, wait for the output to stop, and then close the window (Alt-F4, for example, or Ctrl-Q), I get: konqueror(19813) KonqMainWindow::addClosedWindowToUndoList: konqueror(19813) KonqClosedWindowItem::KonqClosedWindowItem: "Closed_Window64263744" And then nothing. The konqueror window stays up. (Sometimes kwin then tells me it's not responding and gives me a chance to terminate it, sometimes not unless I click on the "X".) This did not happen in 4.9.1. Thanks, Reproducible: Always Steps to Reproduce: 1. Open konqueror 2. Try to close it, e.g., Ctrl-Q Actual Results: hang Expected Results: close
What is the default page that shows up when Konqueror launches ? That is what does Settings->Configure Konqueror->When Konqueror starts say ?
See comment #1.
"Show Introduction Page". Sorry about the delay. One thing I noticed is that if I left it hung long enough, it eventually closed. And since then, it has closed properly ever since. So the "hang" is gone, though the question remains: why did it hang? I guess it's going to be harder to figure out now. Maybe I should try logging out and logging back in at some point, though it may have only been after the upgrade from 4.9.1.
I'm seeing the same thing here. Regardless of what the url is. Even w/multiple windows open. I click the window close button or press Alt-F4, it pauses, then pops up the "konqueror is not responding cilck ok to terminate all" window. If I cancel that and wait a while, it eventually closes the window in question, but until that happens all windows are unresponsive. This is new behavior in 4.9.2. I upgraded from 4.9.0 which did not exhibit this behavior.
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
I provided the information requested, I believe, though I can no longer reproduce this problem with newer konquerors.
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!