Version: (using KDE 4.2.4) Compiler: gcc-4.3.2 OS: Linux Installed from: Fedora RPMs We have been having this problem since KDE 4.x and still present in 4.2.4. If one starts nohup job in konsole that runs on multiple processors, e.g. "nohup run &", and then tries to logout without closing the konsole window, the job is either killed or reduced to a single thread which seems to hang. If you close the konsole window before logout all works fine. The same thing happens if konsole is opened via dolphin, in which case, the job is borked even if one closes the konsole window before logout (job attached to a running process dolphin?). It seems like the nohup job is associated with the konsole process and something is done to it to preserve its state on logout. Thanks.
This bug is still present in KDE-4.3.0.
Do this problem still exist for the reporter in recent version of konsole? I do not fully understand the problem and failed to reproduce it. Could the reporter give more specific and clear steps to reproduce it?