Please add lifecycle exception for terminal
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Ubuntu Terminal App |
Undecided
|
Unassigned | |||
| qtmir (Ubuntu) |
Undecided
|
Unassigned | |||
Bug Description
I've had this conversation with various relevant parties and no had any objections, so filing a bug to request the feature is added.
The Terminal app is currently limited in its functionality because it gets suspended by application lifecycle.
This means you cannot run simple tools like tail or top, or indeed more complex things like ssh without them getting reaped as part of lifecycle when you switch away from the app. This makes the Terminal pretty much useless for most use cases.
I'd like to get a lifecycle exception which would only be in effect if "Developer mode" is switched on in system settings. This would enable users to control the lifecycle exception, and we ensure long running tasks aren't an issue by default because the switch is defaulted off.
| Sam Bull (dreamsorcerer) wrote : | #2 |
I still think that with the lifecycle, it could be usable if it suspended processes when the app was suspended, and restored them when the app is resumed (equivalent to Ctrl+Z, then 'fg' ). At the moment it just kills processes when suspended. I think most use cases like top, watch, or ssh would work just fine like this.
| Sam Bull (dreamsorcerer) wrote : | #3 |
Sorry, my mistake, it already suspends the process. So, it will simply need to resume the process (equivalent to running 'fg') when the app is resumed. This would likely handle most usecases without needing a lifecycle exception, or enabling developer mode.
| Sam Bull (dreamsorcerer) wrote : | #4 |
Now being tracked in a new lifecycle bug.
Status changed to 'Confirmed' because the bug affects multiple users.