Comment 18 for bug 538213

Speaking of which.

How the fsck can we get RID of this blasted plymouth bugfest entirely?

It appears to have a about a zillion packages that are dependent on it, so synaptic won't ditch it without tossing most of Lucid. What a screw-up.

I'm thinking something along the lines of this:

  updatedb
  locate plymouth | xargs rm

Got a better suggestion? This is just too painful. I *live* in text editors, and having them randomly crash the entire X session every 2-3 minutes is just stupid.

-ml