** Package changed: kdebase-workspace (Ubuntu) => kde-workspace (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm in Ubuntu.
https://bugs.launchpad.net/bugs/665195
Title:
plymouthd alive when umountroot runs (prevents cle
It's not unpredictable; it just requires that, once the gdm or kdm job
starts, it takes care of stopping plymouth before it exits.
There is no simpler design that satisfies the boot-time requirements.
--
plymouthd alive when umountroot runs (prevents clean unmount)
https://bugs.launchpad.net/bug
I'm getting the feeling that the mechanism used to keep plymouth up /
down appropriately AND avoid a VT change all the while is brittle; there
are too many unpredictable interactions between plymouth, plymouth-stop,
[gkx]dm and "rc*.d stop".
That's why I filed against plymouth in the first place -
someone should check whether this also affects kdm - it probably does.
--
plymouthd alive when umountroot runs (prevents clean unmount)
https://bugs.launchpad.net/bugs/665195
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm in ubuntu.
Ah, sorry for misreading. The thing is that plymouthd is supposed to be
run *twice* on the system, once at startup and once at shutdown. I
assumed that what you were seeing was a plymouthd process running at
shutdown like it's supposed to; the open /var/log/boot.log (and the
--mode=boot argument
