[dolphin] [Bug 423376] New: Terminal programs started in Dolphin continue running after Dolphin exits, writing to .xsession-errors

[Isaac]

https://bugs.kde.org/show_bug.cgi?id=423376

            Bug ID: 423376
           Summary: Terminal programs started in Dolphin continue running
                    after Dolphin exits, writing to .xsession-errors
           Product: dolphin
           Version: 19.12.3
          Platform: Other
                OS: Linux
            Status: REPORTED
          Severity: normal
          Priority: NOR
         Component: general
          Assignee: dolphin-bugs-null at kde.org
          Reporter: 8SwitchSoftware at gmail.com
                CC: kfm-devel at kde.org
  Target Milestone: ---

SUMMARY

When you start a Terminal program from Dolphin, it continues running in the
background even after you close Dolphin. It receives zeroes as input and its
output is directed to .xsession-errors. This continues until the disk is full
(unless the user notices and stops it).

STEPS TO REPRODUCE
1. Write a short program that reads input and writes the same thing back as
output. E.g. something like this:

BEGIN:
cin >> var;
cout << var;
goto BEGIN;


2. Compile it (I used: g++ test.cpp)

3. Go to the a.out file in Dolphin and double click on it.

4. Click on "Execute". The program will now run in the background but won't do
anything (since it's not getting any input). You can see the program listed as
a child process of Dolphin in KSysGuard.

5. Close Dolphin.

OBSERVED RESULT

The child process will continue running in the background (after Dolphin
exits). You can see it will start taking up a whole CPU thread in KSysGuard (or
"top" in Terminal). .xsession-errors will begin filling up with zeroes. It
seems like after dolphin exits, the process starts being fed a steady stream of
zeroes and its output is being redirected to .xsession-errors.

EXPECTED RESULT

I don't know what would be a good way to fix this. Would there be a way to make
all child processes of Dolphin close when Dolphin closes? This might not be
good though as other GUI applications are often started in Dolphin and they
ought to continue running. Perhaps a feature can be added to prevent Dolphin
from starting these sorts of programs to begin with?

Or maybe when Dolphin runs a program like this it should open the Terminal
along with it (much like Windows does when you start a Terminal program from
Explorer).

SOFTWARE/OS VERSIONS

Linux: 5.7.0-050700-generic
KDE Plasma: 5.18.5 
KDE Frameworks Version: 5.68.0
Qt Version: 5.12.8

ADDITIONAL INFORMATION

I'm using Kubuntu 20.04.

-- 
You are receiving this mail because:
You are on the CC list for the bug.