Comment 32 for bug 572279

Hello!

The bug is not fixed at all! After one of several kernel updates, the bug reappears!

Plymouth seems to be the cause.

To fix : sudo dpkg-reconfigure plymouth solve temporally the problem to the new kernel upgrade...

I'm also on a debian testing. I've never seen this bug on debian because debian don't use plymouth...

How can we safely remove plymouth?