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

Robert Bruce Park robert.park at canonical.com
Thu Dec 20 22:10:41 UTC 2012


** Also affects: ubuntu-nexus7
   Importance: Undecided
       Status: New

** Changed in: ubuntu-nexus7
       Status: New => Confirmed

** Changed in: plymouth (Ubuntu Raring)
       Status: New => Triaged

** Changed in: ubuntu-defaults-nexus7 (Ubuntu Raring)
   Importance: High => Critical

** Changed in: ubuntu-nexus7
     Assignee: (unassigned) => Oliver Grawert (ogra)

** Changed in: plymouth (Ubuntu Raring)
     Assignee: (unassigned) => Oliver Grawert (ogra)

** Changed in: plymouth (Ubuntu Raring)
   Importance: High => Critical

-- 
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:
  Confirmed
Status in “plymouth” package in Ubuntu:
  Triaged
Status in “ubuntu-defaults-nexus7” package in Ubuntu:
  In Progress
Status in “plymouth” source package in Raring:
  Triaged
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




More information about the foundations-bugs mailing list