lightdm on touch leaves a unity-system-compositor process around

[Oliver Grawert]

using "stop lightdm" on an ubuntu touch device leaves the unity-system-compositor process running, starting lightdm later again fires up a new unity-system-compositor process.

(adding something like "pkill unity-system-compositor" into the post-stop script block in the upstart job actually causes a hard reboot of the device (as any occasion when stopping the u-s-c, doesnt only happen when stopped from lightdm)

[Oliver Grawert (ogra)]

see also bug 1285236

[Robert Ancell (robert-ancell)]

Can you attach /var/log/lightdm/*.log after this occurs?

[Oliver Grawert (ogra)]

Note that this setup uses a wrapper script to start unity-system-compositor ... attaching this as well (i guess lightdm doesnt have the right PID for u-s-c due it being spawned from a subshell)

[Michael Terry (mterry)]

Adding an 'exec' to the last line of usc-wrapper fixes this. It means we give all of the variables in /etc/environment to the u-s-c process, but that's probably fine.

[Michael Terry (mterry)]

Oh neat, that's not a problem. I was wrong about how exec behaves apparently

[Launchpad Janitor (janitor)]

[Expired for lightdm (Ubuntu) because there has been no activity for 60 days.]