[Bug 594839] Re: Plymouthd SIGSEGV on Lucid Xen Instance

[Josh Goodall]

I encountered this problem, with more severe side-effects, on Linode.

When plymouth segfaults, it causes mountall to give up:
mountall: Skipping mounting /var since Plymouth is not available

which is a nasty way for a boot to die.


Removing --attach-to-session appears to be a workaround.

-- 
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/594839

Title:
  Plymouthd SIGSEGV on Lucid Xen Instance

Status in “plymouth” package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: plymouth

  Lucid is installed on a Xen instance.  At boot time plymouthd SEGVs
  when requested to show the splash screen

  init: plymouth-splash main process (347) terminated with status 2
  init: plymouth main process (102) killed by SEGV signal
  init: plymouth-log main process (435) terminated with status 1

  plymouthd gets started from the plymouth upstart job with configuration at /etc/init/plymouth.conf
  and has the following options

  /sbin/plymouthd --mode=boot --attach-to-session

  As a work around you can remove the --attach-to-session option.

  The root cause of the problem is that state->boot_buffer gets creamed at src/main.c:1498 in attach_to_running_session.
  Since attach_to_running_session doesn't allocate the buffer it should probably leave it alone when it fails.

  lsb-release -rd:
  Description:	Ubuntu 10.04 LTS
  Release:	10.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/594839/+subscriptions