Reopening Apport task for improving the data in the report. It should have the list of omitted pids passed with -o, and the running processes (ps aux).
I added some set -x and "ps aux" to /etc/init.d/sendsigs, and found out the following:
* plymouthd --mode=shutdown is always running
* no process adds itself to sendsigs.omit{,.d} lists, which seems intended and correct
* All of the actual omitted pids are gained from initctl list and filtering out its pids.
- This always contains "/etc/init.d/rc 6" and hwclock.
- This sometimes contains the plymouthd --mode=shutdown process, and sometimes not. In the latter case the apport hook is fired, and plymouthd actually gets killed by sendsigs.
So as far as I can see, "initctl list" sometimes does not show the pid of plymouthd --shutdown. Is it supposed to? If so, then that would be the bug. If initctl list is not reliable, then we need to find another approach to filter out upstart jobs in sendsigs.
Reopening Apport task for improving the data in the report. It should have the list of omitted pids passed with -o, and the running processes (ps aux).
I added some set -x and "ps aux" to /etc/init. d/sendsigs, and found out the following:
* plymouthd --mode=shutdown is always running
* no process adds itself to sendsigs.omit{,.d} lists, which seems intended and correct
* All of the actual omitted pids are gained from initctl list and filtering out its pids.
- This always contains "/etc/init.d/rc 6" and hwclock.
- This sometimes contains the plymouthd --mode=shutdown process, and sometimes not. In the latter case the apport hook is fired, and plymouthd actually gets killed by sendsigs.
So as far as I can see, "initctl list" sometimes does not show the pid of plymouthd --shutdown. Is it supposed to? If so, then that would be the bug. If initctl list is not reliable, then we need to find another approach to filter out upstart jobs in sendsigs.