So i've reproduced this on a normal desktop, even with a previous plymouth (so behaviour is not a regression as far as i can tell so far)
over e.g. ssh connection
1) stop lightdm; start plymouth in shutdown mode
2) start plymouth-upstart-bridge
3) press esc to get messages/console instead of splash
4) restart a job, e.g. restart cups
Starting/stopping plymouth bridge messages are printed, followed by the upstart job name.
Next i've set "console log" on plymouth-upstart-bridge, and started/stopping messages went away to /var/log/upstart/plymouth-upstart-bridge.log, however the naked upstart job name was still printed to the console.
Stopping plymouth-upstart-bridge makes the messages go away. I'm still trying to trace if it's plymouthd or plymouth-upstart-bridge spewing things onto the console.
So i've reproduced this on a normal desktop, even with a previous plymouth (so behaviour is not a regression as far as i can tell so far)
over e.g. ssh connection upstart- bridge
1) stop lightdm; start plymouth in shutdown mode
2) start plymouth-
3) press esc to get messages/console instead of splash
4) restart a job, e.g. restart cups
Starting/stopping plymouth bridge messages are printed, followed by the upstart job name.
Next i've set "console log" on plymouth- upstart- bridge, and started/stopping messages went away to /var/log/ upstart/ plymouth- upstart- bridge. log, however the naked upstart job name was still printed to the console.
Stopping plymouth- upstart- bridge makes the messages go away. I'm still trying to trace if it's plymouthd or plymouth- upstart- bridge spewing things onto the console.