[Bug 1084063] Re: plymouth in raring causes system hardlock if console_setup is not run in the initramfs on nexus7 prior to starting plymouthd
nathan
nathan95 at live.it
Wed Jan 6 18:57:00 UTC 2016
** Changed in: plymouth (Ubuntu)
Status: In Progress => Invalid
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to plymouth in Ubuntu.
https://bugs.launchpad.net/bugs/1084063
Title:
plymouth in raring causes system hardlock if console_setup is not run
in the initramfs on nexus7 prior to starting plymouthd
Status in Plymouth:
Invalid
Status in ubuntu-nexus7:
Fix Released
Status in plymouth package in Ubuntu:
Invalid
Status in ubuntu-defaults-nexus7 package in Ubuntu:
Invalid
Status in plymouth source package in Raring:
Won't Fix
Status in ubuntu-defaults-nexus7 source package in Raring:
Won't Fix
Bug description:
while i can see the splash fine if i add a break= statement to my kernel commandline and manually ctrl-d out of the initrd shell,
using plymouth without a break statement causes a hard reboot of the system.
To manage notifications about this bug go to:
https://bugs.launchpad.net/plymouth/+bug/1084063/+subscriptions
More information about the foundations-bugs
mailing list