Running process gets killed when put to background

[Sam Bull]

1. Run 'top'.
2. Use right edge swipe to switch away from terminal app.
3. Switch back to terminal app after a few seconds and see that the running process has been stopped.

The process can be manually restored by running fg, but should be automatically restored when switching back to the app, ideally with no interruption to the terminal output (i.e. no '[stopped]' etc. messages).

[Adrian Lewis (adrian-lewis)]

the terminal app is unusable in its current state. When we switch away the current process is stopped and fg hangs the terminal.

[Richard Ulrich (richi-paraeasy)]

This is especially annoying when running is a script that mounts/unmounts some directories for a chroot.

[AlainKnaff (kubuntu-misc)]

It is also annoying for apps that put the terminal into a special mode (for curses, and such).

Example: vi

When coming back to the terminal, vi gets stopped automatically, and terminal (stty) settings are restored by bash to their default mode. When foregrounding vi again with fg, it doesn't restore the stty settings that it needs, and from thereon its output is all messed up.

Happens not only if you switch to another application or scope, but also when locking the screen.

This is a useability nightmare when using via as a notepad during shopping, and putting the phone into your pockets between jotting down notes at various places.

[AlainKnaff (kubuntu-misc)]

Confirmed, as experienced by several people

[AlainKnaff (kubuntu-misc)]

A workaround for this:
  exec ssh localhost

:-)

(you first need to append you id_dsa.pub key to your authorized_keys though...)

And, if you only need to execute vi once:

 exec vi myfile.txt

If you quit vi, it closes the terminal though.

[SouthBay (southbay-temp)]

Another workaround is to switch your UI from "Staged mode" to "Windowed mode". Can be done editing configs directly or using the Ubuntu Touch Tweak Tool. All Terminal tabs then run within a desktop-like window and are not stopped in the background.

If you maximize the application's window so it takes up all of the device's screen, there's little difference in the interface. Also window size seems to be sticky, so the next time you run Terminal (or any other app), it will run in a maximized window.

[Set Hallstrom (sakrecoer)]

This bug could be a duplicate of #1502197

[AlainKnaff (kubuntu-misc)]

Is #1502197 really the same bug? Depending on how you read #1502197 , this might actually be exactly the opposite...
_Current_ behavior is, processes are automatically put in the background as soon as you switch away from the terminal. What we want is that they stay in the foreground. Bug #1502197 seems to _want_ processes to be run in the background... (or at best, the wording is very ambiguous...)

[AlainKnaff (kubuntu-misc)]

(In reply to comment #6)

Thanks for this tip. This does indeed solve the issue, but unfortunately at a price: Now the keyboard no longer "pushes up" the terminal when it appears (leaving the last entered text legible), but instead partly covers the terminal (obscuring the last entered text), which make the terminal rather unusable :-(