Stopped apps don't restart when launched from another app

[Alan Pope 🍺🐧🐱 🦄]

Steps to reproduce:-

1) Open twitter webapp and sign in
2) Open browser
3) Open some other apps to ensure browser gets cleaned up by app lifecycle
4) Switch to twitter
5) Click on a link in a tweet

Expected behaviour:-

* Clicked link opens in browser

Actual behaviour:-

* Nothing

Note, you can swipe back to browser to "wake" it up from suspend, then back to twitter, click the link and it _will_ switch back to browser and open the link.

[Michał Sawicz (saviq)]

This might involve url-dispatcher, too (like focusing → resuming before sending the url over dbus).

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Joe Odukoya (jodukoya)]

Kevin -
Can you explain why the status for Unity8 and URL-dispatcher has been changed to 'Opinion'.
Note: This is not a challenge - just trying to understand.

[kevin gunn (kgunn72)]

@Joe - using "opinion" in order to leave a project in the loop, just in case. however, at some point when we are fairly certain the bug fix is totally isolated to a particular package, we can just remove the project/package from the "effected list"
and this helps a little with filtering now too since "opinion" is something i filter out locally.
hope that helps.

[Gerry Boland (gerboland)]

qtmir.applications: ApplicationManager::onProcessStarting - appId= "webbrowser-app"
ApplicationManager::onProcessStarting application already found with appId "webbrowser-app"
qtmir.mir: SessionAuthorizer::connection_is_allowed - this= SessionAuthorizer(0x1494bec) pid= 24699
qtmir.applications: ApplicationManager::authorizeSession - pid= 24699
ApplicationManager REJECTED connection from app with pid 24699 as no desktop_file_hint specified
qtmir.applications: ApplicationManager::onProcessFailed - appId= "webbrowser-app" duringStartup= true
qtmir.applications: ApplicationManager::onProcessStopped - appId= "webbrowser-app"

Problem is to be that webbrowser is being re-launched by upstart, but AppMan wasn't expecting that and so rejects the newly starting app instance.