[Bug 1084063] Re: plymouth in raring causes system hardlock if console_setup is not run in the initramfs on nexus7 prior to starting plymouthd

[Oliver Grawert]

please do not randomly set bug statuses to fix-released without poining to the actual upload that fixed the issue ... 
this particular bug is not fixed yet, it just has a workaround.

** Changed in: plymouth (Ubuntu Raring)
       Status: Fix Released => In Progress

** Changed in: ubuntu-defaults-nexus7 (Ubuntu Raring)
       Status: Fix Released => In Progress

-- 
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 Ubuntu on the Nexus 7:
  Fix Released
Status in “plymouth” package in Ubuntu:
  In Progress
Status in “ubuntu-defaults-nexus7” package in Ubuntu:
  In Progress
Status in “plymouth” source package in Raring:
  In Progress
Status in “ubuntu-defaults-nexus7” source package in Raring:
  In Progress

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/ubuntu-nexus7/+bug/1084063/+subscriptions