New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[yamuisplash] Adapt to yamui changes. Fixes JB#59812 #3
[yamuisplash] Adapt to yamui changes. Fixes JB#59812 #3
Conversation
|
Simo Piiroinen ***@***.***> writes:
> EnvironmentFile=-/var/lib/environment/compositor/*.conf
-ExecStart=/bin/sh /usr/bin/yamuisplash
-# make sure we run for at least 5 seconds for any touch initialization sequences to finish.
-ExecStartPost=/bin/sleep 5
+ExecStartPre=/bin/touch /tmp/.yamuisplash.done
Possibly. Did not think about it, just tweaked where it does what it
already did. But this is executed quite early in bootup -> is /run
already ready for use? And if it is, where/how should this /run/yamui
directory be created?
/run is available after the rootfs is mounted. /run/yamui can be created
with tmpfiles.d or `RuntimeDirectory` inside yamui.service.
|
So, actually /run is available a bit earlier than /tmp - which means using it would be a good thing. I think tmpfiles.d is out because waiting for systemd-tmpfiles-setup.service would incur about 2 second delay for showing the splascreen. RuntimeDirectory should work (but given the purpose, needs RuntimeDirectoryPreserve=yes too). Need to test that (and dropping flagfile use altogether too). |
b521155
to
3e936ac
Compare
|
Review commits squashed |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Yamui has been modified so that it is systemd aware and implements compositor D-Bus service. Switch yamuisplash systemd service type from simple to notify, and remove the not really necessary start script. As yamui will now automatically exit when the next UI wants to take over display, systemd drop-ins that were used for explicitly stopping splashscreen service can be removed. Move flagfile from /tmp to /run and remove After=tmp.mount. Add Conflicts/Before=shutdown.target as is recommended for services that utilize DefaultDependencies=no. As yamui gets executed and grabs display well before droid hal init has a chance to start android hw composer, there is no need for explicit delay and thus Before=droid-hal-init.service can be removed. However, in order to ensure deterministic display ownership transfer, unlock agent and user session need to wait until yamui is ready. Uses features that are available in yamui >= 1.2.0 Signed-off-by: Simo Piiroinen <simo.piiroinen@jolla.com>
3e936ac
to
8d6ff57
Compare
|
Removed Before=droid-hal-init.service |
Yamui has been modified so that it is systemd aware and implements compositor D-Bus service.
Switch yamuisplash systemd service type from simple to notify, and remove the not really necessary start script.
As yamui will now automatically exit when the next UI wants to take over display, systemd drop-ins that were used for explicitly stopping splashscreen service can be removed.
Signed-off-by: Simo Piiroinen simo.piiroinen@jolla.com