On 2015-02-26 02:12, Gordon Morehouse wrote: > Hi there, > > I'm not a Debian developer or maintainer. That said, I've been an > enthusiastic user for quite some time. > > I believe #768314 needs attention from someone who can decide whether it > should be upgraded to a release blocker for jessie. If this bug ships as > 'stable' there will be people quite justifiably screaming about it, and I > believe it would make Debian look bad. It is a nasty bug, happens at boot > time, can render a system temporarily (or maybe completely, depending on > number of cryptsetup volumes) unusable. If I were a sysadmin and it appeared > on my server after an upgrade or fresh installation of jessie, I would go > right back to the prior release or to another distro. > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768314 > > Best, > -Gordon M. > >
Hi Gordon, To the best of my knowledge, this bug is caused by the absence of plymouth and has been documented in the release-notes[1]. If installing plymouth does not solve the issue for you, we might be looking at a different bug. Thanks, ~Niels [1] https://www.debian.org/releases/jessie/amd64/release-notes/ch-information.en.html#plymouth-required-for-boot-prompts -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: https://lists.debian.org/[email protected]
