Summary: | Opening session after closing session causes an about 1 minute freeze in konsole | ||
---|---|---|---|
Product: | [Applications] konsole | Reporter: | Thomas Georgiou <TAGeorgiou> |
Component: | general | Assignee: | Robert Knight <robertknight> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | wstephenson |
Priority: | NOR | ||
Version: | 1.9.2 | ||
Target Milestone: | --- | ||
Platform: | Compiled Sources | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Thomas Georgiou
2007-11-07 00:45:55 UTC
Reporter says the error I have is the same as his: "QProcess: destroyed while process is still running" when starting a 2nd konsole out of an existing one. The konsole doesn't become responsive again. openSUSE 10.3, konsole 1.9.2 (svn of today) FWIW. Im using gentoo amd64 Will, Thomas: Can you run Konsole in a debugger with a breakpoint on the Qt code which produces the warning (if you are using qt-copy, this is qprocess.cpp:752) and post a backtrace? Here is a backtrace for konsole while it is still frozen http://pastebin.ca/raw/764277 Here is the backtrace breaking from qWarning() http://pastebin.ca/raw/764292 Thomas and I managed to narrow the problem down to utempter. The only place where a QProcess is created is to run /usr/sbin/utempter in KPty::login() and KPty::logout(). I don't have utempter on my system - hence I didn't run into the problem. I have temporarily disabled utempter support in Konsole (commit #733673) pending further investigation. Marking as fixed. Will look into reinstating utempter support in future if required. |