Bug 200679 - multi-threaded nohup jobs borked if konsole open on logout
Summary: multi-threaded nohup jobs borked if konsole open on logout
Status: RESOLVED WORKSFORME
Alias: None
Product: konsole
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Fedora RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: Konsole Developer
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-07-18 17:38 UTC by S. Umar
Modified: 2011-10-13 11:10 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description S. Umar 2009-07-18 17:38:15 UTC
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.
Comment 1 S. Umar 2009-08-10 14:33:54 UTC
This bug is still present in KDE-4.3.0.
Comment 2 Jekyll Wu 2011-10-08 08:17:33 UTC
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?