unity8 should only allow launching once
Bug #1193412 reported by
Omer Akram
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
unity8 (Ubuntu) |
Confirmed
|
Medium
|
Unassigned |
Bug Description
Currently if we start Unity8 from terminal on the phone, it starts a new instance. Instead the case should be handled a better way, either a second instance should not be allowed or the already running unity should be killed before.
summary: |
- Starting unity from terminal should restart it + unity8 should only allow launching once |
affects: | unity → unity8 |
Changed in unity8: | |
status: | Invalid → Confirmed |
importance: | Undecided → Medium |
no longer affects: | unity/8.0 |
Changed in unity8 (Ubuntu): | |
importance: | Undecided → Medium |
status: | New → Confirmed |
no longer affects: | unity8 |
To post a comment you must log in.
I believe this should be handled via an upstart session - before starting a new instance, you "stop unity8" to make sure there isn't one running, and then launch it with whatever you need.
A --replace option I don't think is wanted / needed - it only makes sense for a split display server / window manager / compositor where you want to replace the window manager in the currently running display server. With Unity8 on Mir it's all going to be the same process, so the effect is the same as killing and replacing.
Unity8 should, though, bail out if there is an instance already running.