unity8 should only allow launching once

Bug #1193412 reported by Omer Akram
6
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.

Revision history for this message
Michał Sawicz (saviq) wrote :

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.

Changed in unity:
status: New → Invalid
Michał Sawicz (saviq)
summary: - Starting unity from terminal should restart it
+ unity8 should only allow launching once
Revision history for this message
Stephen M. Webb (bregma) wrote : Re: [Bug 1193412] Re: Starting unity from terminal should restart it

> 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.

A --replace option makes perfect sense in the case that Unity is hung in a session. While it's true that a series of
command could be entered from the command line to shut down the old running Unity 8 session and start a new one, among
the faults with that approach are these.

(1) It requires an in-depth knowledge of the internal architecture of session management on the part of the poor
struggling user who is experiencing a hung session.

(2) Every extra step after the first is an extra step that isn't necessary and one more place things can go wrong in the
field -- and remember: if things can go wrong in the field, they will do so in a way that maximizes inconvenience.

(3) It is inconsistent with known published documented procedures already widely disseminated in the community.

Michał Sawicz (saviq)
affects: unity → unity8
Changed in unity8:
status: Invalid → Confirmed
importance: Undecided → Medium
no longer affects: unity/8.0
Michał Sawicz (saviq)
Changed in unity8 (Ubuntu):
importance: Undecided → Medium
status: New → Confirmed
Michał Sawicz (saviq)
no longer affects: unity8
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.