Ah, I was able to recreate the problem of 'plymouth --ping' hanging with the following test case on an Ubuntu 16.04 system.
1) Run 'sudo /sbin/plymouthd --mode=boot --attach-to-session --pid-file=/run/plymouth/pid' 2) Observe plymouthd is running ('ps aux | grep plymouth') 3) stop the plymouthd process 'sudo kill -STOP $PID' 4) Run 'plymouth --ping --debug'
bdmurray@clean-xenial-amd64:~$ plymouth --ping --debug [ply-event-loop.c:759] ply_event_loop_stop_watching_fd:stopping watching fd 6 [ply-event-loop.c:775] ply_event_loop_stop_watching_fd:removing destination for fd 6
Ah, I was able to recreate the problem of 'plymouth --ping' hanging with the following test case on an Ubuntu 16.04 system.
1) Run 'sudo /sbin/plymouthd --mode=boot --attach-to-session --pid-file= /run/plymouth/ pid'
2) Observe plymouthd is running ('ps aux | grep plymouth')
3) stop the plymouthd process 'sudo kill -STOP $PID'
4) Run 'plymouth --ping --debug'
bdmurray@ clean-xenial- amd64:~ $ plymouth --ping --debug loop.c: 759] ply_event_ loop_stop_ watching_ fd:stopping watching fd 6 loop.c: 775] ply_event_ loop_stop_ watching_ fd:removing destination for fd 6
[ply-event-
[ply-event-