Bug 122580

Summary: all kde applications are automatically stopped under midnight commander's shell
Product: [Unmaintained] kdelibs Reporter: Leo Savernik <l.savernik>
Component: kdeinitAssignee: kdelibs bugs <kdelibs-bugs>
Status: RESOLVED FIXED    
Severity: normal CC: adaptee
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Compiled Sources   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Leo Savernik 2006-02-23 19:41:23 UTC 
Version:            (using KDE KDE 3.5.1)
Installed from:    Compiled From Sources

Since KDE 3.5 or maybe 3.4, kde processes cannot be started in the background on midnight commander's subshell.

Steps to reproduce:
1. Have an instance of midnight commander running.
2. Hit Ctrl+O to switch to the shell.
3. Enter 'kwrite <somefilethatexists> &' (note the trailing ampersand)

Expected results:
The prompt returns immediately and kwrite shows up.

Actual results:
The prompt returns immediately, but nothing happens. If you press enter after a few seconds, you read something like:

[2]+  Stopped                 kwrite tabbox.cpp

You can get it running by invoking "fg", but this in turn suspends mc.

This is a big problem as you cannot select a file in mc anymore and directly hand it over to kwrite (or any other kde application), while continue browsing in mc.
Comment 1 Thiago Macieira 2006-02-26 02:29:29 UTC 
It's possible the application is being stopped by SIGTTIN, if it tried to read from the terminal...
Comment 2 Oswald Buddenhagen 2008-05-30 13:28:34 UTC 
something similar happens with gdb, so i'm tending to believe this to be a problem in mc. fwiw, mc devs are kinda dissatisfied with the subshell handling, too.
Comment 3 Jekyll Wu 2011-12-30 23:58:48 UTC 
The problem doesn't seem to exist when using KDE SC 4.8 RC1 and mc 4.8.1
Comment 4 Jekyll Wu 2012-07-07 14:24:18 UTC 
Feel free to reopen this report if the problem still happens in recent versions (KDE SC 4.8.4 or higher).