ubuntu-app-test fails to launch apps at all [CRITICAL **: Unable to get PID for 'ubuntu-app-test' application]

[Daniel van Vugt]

ubuntu-app-test fails to launch apps:

$ ubuntu-app-test mir_demo_client_egltriangle

** (process:19625): WARNING **: Starting 'ubuntu-app-test' failed with error: 0

** (process:19625): CRITICAL **: Unable to get PID for 'ubuntu-app-test' application

$ ubuntu-app-test mir_demo_client_flicker

** (process:19660): CRITICAL **: Unable to get PID for 'ubuntu-app-test' application

$ ubuntu-app-test glmark2-es2-mir

** (process:19671): CRITICAL **: Unable to get PID for 'ubuntu-app-test' application

[Daniel van Vugt (vanvugt)]

If it's relevant, I launch everything and do all development from an ssh login. Until recently ubuntu-app-launch worked fine in this configuration (bug 1654915).

[Launchpad Janitor (janitor)]

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

[Ted Gould (ted)]

This WFM with this silo: https://bileto.ubuntu.com/#/ticket/2577

It was probably the trusted overlay prompts not being ported to systemd, so you were fighting a Upstart/Systemd battle that would only end in tears.

[Stephen M. Webb (bregma)]

The silo does not help for me. Mir applications fail to connect, but not with the error described in this bug. Instead I get various errors about being unable to connect to the Mir server, which vary depending on the test client used.

Further investigation shows connections to the Mir server are failing with the error "Error processing request: Invalid prompt session" when the proxy socket is used, but if the regular MIR_SOCKET value is forced the connection succeeds.

I had to use strace to glean the actual connection failure message since it gets swallowed somewhere in the Mir client.

[Brandon Schaefer (brandontschaefer)]

I was able to hit this issue when U8 crashed while ubuntu-app-test was open. Leaving behind in:
/run/user/1000/systemd/transient/ubuntu-app-launch-application-legacy-ubuntu-app-test-.service

Once this was stuck there even relogging seems to be causing this issue. If you remove that file then it works again.

To reproduce this issue:
1) In U8 on a terminal start ubuntu-app-test with any application
2) Copy the /run/user/1000/systemd/transient/ubuntu-app-launch-application-legacy-ubuntu-app-test-.service somewhere
3) Relog into U8
4) Copy the *.service file back into /run/user/1000/systemd/transient/
5) Try to use ubuntu-app-test again from a terminal in U8

Then you'll hit this error.

[Brandon Schaefer (brandontschaefer)]

An actual way to reproduce:

1) Start ubuntu-app-test through a terminal on U8
2) sudo kill -9 <unity8-pid>
3) Try to start ubuntu-app-test

Error, and you'll see that *.service file is there