Comment 120 for bug 982889

So, the proposed change from #115 doesn't work if plymouth is started from the initramfs, like when cryptsetup is used. In such a case no 'started plymouth-splash' is ever emitted, so something else needs to be used:

00:34 < tjaalton> slangasek: heh, yeah. I was wondering if there was some more generic event to abuse here
00:36 < slangasek> tjaalton: not really, we need to create one - either by fixing it in upstart, or by adding a
                   secondary job that's 'start on startup or started plymouth-splash', checks for plymouth-splash
                   running already, and emits an appropriate common event
00:36 < tjaalton> slangasek: right, that could work
00:36 < tjaalton> as an interim solution
00:37 < slangasek> tjaalton: and by 'checks for plymouth splash running', I mean checking the output of 'status
                   plymouth-splash'

fixing upstart means "synthesizing 'started' events for jobs started from initramfs", but in the meantime the other approach could be used.