Unity8 unable to find the dash, which is also running in the background

'restart unity8-dash' was enough to get it to work again.

qtmir.mir: SessionListener::starting - this= SessionListener(0x1204274) session= 0xad40098c
qtmir.mir: SessionListener::focused - this= SessionListener(0x1204274) session= 0xad40098c
qtmir.mir: SessionAuthorizer::connection_is_allowed - this= SessionAuthorizer(0x12035bc) pid= 2335
qtmir.mir: SessionListener::starting - this= SessionListener(0x1204274) session= 0xad401e04
qtmir.mir: SessionListener::focused - this= SessionListener(0x1204274) session= 0xad401e04
qtmir.mir: SessionListener::stopping - this= SessionListener(0x1204274) session= 0xad401e04
qtmir.mir: SessionListener::focused - this= SessionListener(0x1204274) session= 0xad40098c
qtmir.mir: SessionAuthorizer::connection_is_allowed - Gave up waiting for signal listeners
qtmir.mir: SessionAuthorizer::configure_display_is_allowed - this= SessionAuthorizer(0x12035bc) pid= 2335
qtmir.mir: SessionAuthorizer::screencast_is_allowed - this= SessionAuthorizer(0x12035bc) pid= 2335
qtmir.mir: SessionAuthorizer::prompt_session_is_allowed - this= SessionAuthorizer(0x12035bc) pid= 2335
qtmir.mir: SessionListener::starting - this= SessionListener(0x1204274) session= 0xad300ab4
qtmir.mir: SessionListener::focused - this= SessionListener(0x1204274) session= 0xad300ab4
qtmir.mir: SessionAuthorizer::connection_is_allowed - this= SessionAuthorizer(0x12035bc) pid= 2463
qtmir.mir: SessionAuthorizer::configure_display_is_allowed - this= SessionAuthorizer(0x12035bc) pid= 2463
qtmir.mir: SessionAuthorizer::screencast_is_allowed - this= SessionAuthorizer(0x12035bc) pid= 2463
qtmir.mir: SessionAuthorizer::prompt_session_is_allowed - this= SessionAuthorizer(0x12035bc) pid= 2463
qtmir.mir: SessionListener::starting - this= SessionListener(0x1204274) session= 0xad301004
qtmir.mir: SessionListener::focused - this= SessionListener(0x1204274) session= 0xad301004

qtmir.applications: UnityApplicationPlugin::registerTypes - this= UnityApplicationPlugin(0x1338018) uri= Unity.Application
qtmir.applications: applicationManagerSingleton - engine= QQmlEngine(0x12529f0) scriptEngine= QObject(0x0)
qtmir.applications: ApplicationManager::ApplicationManager (this=%p) qtmir::ApplicationManager(0x134aef8)

This is from the log file - it looks like 2 processes started & connected to Mir, before AppMan was ready.

We need to check if we're emitting the SIGSTOP message to upstart after AppMan is ready, so that upstart starts the dash & OSK at the right time

Or else we make the Mir reject incoming connections until AppMan is ready

>We need to check if we're emitting the SIGSTOP message to upstart
> after AppMan is ready, so that upstart starts the dash & OSK at the right time

That would be preferable, yes. Or we emit a custom signal when AppMan ready, but is there any reason to allow stuff to launch before AppMan is ready? Maybe the OSK?

> Or else we make the Mir reject incoming connections until AppMan is ready

That would mean the dash would abort when it launched too early, cause a .crash and delay launching it for real.

needs to land for developer training as well

This bug was fixed in the package qtmir - 0.4.4+15.04.20141215-0ubuntu1

---------------
qtmir (0.4.4+15.04.20141215-0ubuntu1) vivid; urgency=low

  [ Daniel d'Andrada ]
  * Update README and readd option to disable building tests

  [ Gerry Boland ]
  * Emit SIGSTOP when AppMan fully initialized, when Mir is ready is too
    soon (LP: #1394208)
 -- Ubuntu daily release <email address hidden> Mon, 15 Dec 2014 08:27:44 +0000

Is this going to land in RTM ww51-2014?
It is very much needed: (univ-train).

This bug was fixed in the package unity8 - 8.02+15.04.20141215.3-0ubuntu1

---------------
unity8 (8.02+15.04.20141215.3-0ubuntu1) vivid; urgency=low

  [ Albert Astals Cid ]
  * ScopesList: Use the default scope style for the header

  [ Daniel d'Andrada ]
  * Refactor Dialogs.qml to use proper in-scene dialogs
  * Make Greeter nicely handle being resized

  [ Albert Astals ]
  * Rework how we set the ranges so we get some more asynchronousity
    from item views (LP: #1384374)
  * clickscope is back to being unfavoritable (LP: #1400762)
  * Fix clicking on the manage dash list after having moved the current
    scope
  * Make the drag range be a multiple of the drag "rate" value.
    Workarounds https://bugs.launchpad.net/mir/+bug/1399690

  [ Gerry Boland ]
  * MockAppMan: emit SIGSTOP so AP test apps are run (LP: #1394208)
 -- Ubuntu daily release <email address hidden> Mon, 15 Dec 2014 22:43:16 +0000

Hi Alex,

I do not know whether it will be landed in the ww51-2014. Last weekend,
I re-installed everything, and the problem still existed. It happened even
during the video recording on my desktop. It was quite embarrassing. I
will have one more try. Could you please help to push it to make it happen?

Thanks & best regards,
XiaoGuo

On Tue, Dec 16, 2014 at 8:52 AM, Alex Kaluzhny <email address hidden>
wrote:
>
> Is this going to land in RTM ww51-2014?
> It is very much needed: (univ-train).
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1397801).
> https://bugs.launchpad.net/bugs/1394208
>
> Title:
> Unity8 unable to find the dash, which is also running in the
> background
>
> Status in the base for Ubuntu mobile products:
> Confirmed
> Status in qtmir package in Ubuntu:
> Fix Released
> Status in unity8 package in Ubuntu:
> In Progress
> Status in qtmir package in Ubuntu RTM:
> Triaged
> Status in unity8 package in Ubuntu RTM:
> Triaged
>
> Bug description:
> phablet@ubuntu-phablet:~$ system-image-cli -i
> current build number: 165
> device name: krillin
> channel: ubuntu-touch/ubuntu-rtm/14.09-proposed
> last update: 2014-11-19 00:20:27
> version version: 165
> version ubuntu: 20141118.1
> version device: 20141106-572f18d
> version custom: 20141118-439-21-159
>
> After doing a reboot, Unity8 started fine but the dash looked like it
> failed to start (see the attached pic). After checking for
> unity8-dash, it's actually running in the background, just that unity8
> is unable to find it.
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/canonical-devices-system-image/+bug/1394208/+subscriptions
>

--
XiaoGuo, Liu (刘晓国）
Mobile: +86-13911181302

This bug is in our list for land for next RTM release, should happen soon

May I know roughly when this fix will go to the next RTM release? We are currently depending on this fix to make an image. Hopefully, it could be released soon. We will do more testing on it. Thanks!

The RTM release process is slow. This fix is in the next batch of fixes to land. If things go well, will land by the end of the week. If not, unfortunately it'll have to be after the holidays.

Hi Gerry, is there clearer now when this fix can land?

Anthony, this didn't make it into OTA-1 any more. It is in a silo, however, due to the number of silos QA wasn't able to test/sign off all of them. This fix is one of those that didn't make it. It'll be the first thing to land in OTA-2 (if there is such a thing).

Regarding vivid, it's already landed there.

The fix for this was just released as unity8_8.02+15.04.20141218~rtm-0ubuntu1, qtmir_0.4.4+15.04.20141218~rtm-0ubuntu1.