On 8 May 2014 17:46, Steve Langasek <email address hidden> wrote:
> Dimitri, please have a look at this bug. I can't figure out what the
> current plymouth-shutdown job is supposed to do; it has a start
> condition of:
>
> start on (runlevel [016]
> and (stopped xdm
> or stopped uxlaunch))
>
> And I have neither xdm or uxlaunch on my system, so I don't know how
> this job ever starts at all on an Ubuntu desktop... and on a desktop
> that does have xdm, it seems that it triggers and blocks the shutdown.
>
On normal desktops plymouth-shutdown is started by rc.conf job, before
emitting runlevels 0, 1 or 6.
Which in-turn should stop lightdm (if present) and bring up plymouthd
in shutdown mode.
What is confusing however in the ps outputs attached is that in all
three process outputs:
- plymouthd in boot mode is still running
- /bin/plymouth quit has not completed
I'll experiment with such a minimal setup in a VM.
On 8 May 2014 17:46, Steve Langasek <email address hidden> wrote:
> Dimitri, please have a look at this bug. I can't figure out what the
> current plymouth-shutdown job is supposed to do; it has a start
> condition of:
>
> start on (runlevel [016]
> and (stopped xdm
> or stopped uxlaunch))
>
> And I have neither xdm or uxlaunch on my system, so I don't know how
> this job ever starts at all on an Ubuntu desktop... and on a desktop
> that does have xdm, it seems that it triggers and blocks the shutdown.
>
On normal desktops plymouth-shutdown is started by rc.conf job, before
emitting runlevels 0, 1 or 6.
Which in-turn should stop lightdm (if present) and bring up plymouthd
in shutdown mode.
What is confusing however in the ps outputs attached is that in all
three process outputs:
- plymouthd in boot mode is still running
- /bin/plymouth quit has not completed
I'll experiment with such a minimal setup in a VM.
--
Regards,
Dimitri.