Description of problem: Konqueror got unresponsive so I've killed it. Meanwhile, in another window, a page tried to open a popup ... new window with the old (killed) tabs appeared, then both windows disappeared and I got the crashreport. So, the possible way to reproduce (haven't tried yet) is 1) have two konqueror windows opened 2) kill one of the windows 3) in the second window, go to some page that opens popups 4) let the popup to be opened (agree to restore the session) Version-Release number of selected component: kde-baseapps-4.11.5-1.fc20 Additional info: reporter: libreport-2.1.11 backtrace_rating: 4 cmdline: konqueror -session 1022e2a728e1e2000138313389600000010643264_1387384695_336167 crash_function: KonqMainWindow::slotIntro executable: /usr/bin/konqueror kernel: 3.12.6-300.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (1 frames) #0 KonqMainWindow::slotIntro at /usr/src/debug/kde-baseapps-4.11.5/konqueror/src/konqmainwindow.cpp:5248
Created attachment 853117 [details] File: backtrace
Created attachment 853118 [details] File: cgroup
Created attachment 853119 [details] File: core_backtrace
Created attachment 853120 [details] File: dso_list
Created attachment 853121 [details] File: environ
Created attachment 853122 [details] File: exploitable
Created attachment 853123 [details] File: limits
Created attachment 853124 [details] File: maps
Created attachment 853125 [details] File: open_fds
Created attachment 853126 [details] File: proc_pid_status
Created attachment 853127 [details] File: var_log_messages
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.