[Bug 1160079] Re: plymouth aborts in cloud images

Fri Apr 4 00:43:53 UTC 2014

This bug was fixed in the package plymouth - 0.8.8-0ubuntu16

---------------
plymouth (0.8.8-0ubuntu16) trusty; urgency=medium

  [ Steve Langasek ]
  * Fix debian/patches/tty1-after-boot.patch: when we have multiple
    non-default console options on the kernel commandline,
    local_console_terminal will not be set, so we should avoid the resulting
    assert.  LP: #1160079, LP: #1235231.

  [ Dimitri John Ledkov ] LP: #1292458
  * debian/patches/use-upstart-private-socket.patch: instead of using
    system dbus, use private upstart socket in the plymouth-upstart-bridge.
  * debian/plymouth.plymouth-upstart-bridge.upstart: start
    plymouth-upstart-bridge on startup, and thus gather a more complete
    boot.log.
  * debian/patches/dont-bail-on-dummy-terms.patch: don't bail
    plymouth-upstart-bridge if TERM is not set and/or running on a dummy
    terminal, as we can run on those. This makes console-log useful in
    lxc-containers and actually contain messages from upstart jobs
    starting and stopping.
  * debian/patches/no-print-empty-description.patch: do not store
    description when dbus returns empty string, and thus stop printing
    empty "Starting... done" messages. LP: #1185560.
  * debian/plymouth.plymouth-upstart-bridge.upstart: update stop on
    conditions to stop when plymouth-shutdown finishes.
  * Make ubuntu-logo theme support scale factor, provide one plymouth
    theme with scale 1 and another with scale 2, until scale factor can be
    dynamically detected.
  * Mark plymouth-upstart-bridge to respawn.
 -- Dimitri John Ledkov <xnox at ubuntu.com>   Thu, 03 Apr 2014 16:37:29 +0100

** Changed in: plymouth (Ubuntu)
       Status: Confirmed => Fix Released

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

Title:
  plymouth aborts in cloud images

Status in “plymouth” package in Ubuntu:
  Fix Released

Bug description:
  On cloud-images for EC2 and Windows Azure, plymouth aborts:

  On EC2:
  [   22.254620] init: udev-fallback-graphics main process (476) terminated with status 1
  [   23.567151] init: plymouth main process (222) killed by ABRT signal
  [   23.568554] init: plymouth-splash main process (500) terminated with status 2
  [   34.348406] init: plymouth-log main process (683) terminated with status 1
  [   34.383796] init: failsafe main process (684) killed by TERM signal
  [   35.339450] init: plymouth-upstart-bridge main process (743) terminated with status 1
  ...
  [   91.558062] init: upstart-udev-bridge main process (318) terminated with status 1
  [   91.558099] init: upstart-udev-bridge main process ended, respawning
  [   91.558307] init: upstart-socket-bridge main process (451) terminated with status 1
  [   91.558338] init: upstart-socket-bridge main process ended, respawning
  [   93.223765] udevd[1892]: starting version 175
  [  145.040013] [sched_delayed] sched: RT throttling activated

  On Windows Azure:
  [   20.976606] init: udev-fallback-graphics main process (779) terminated with status 1
  [   21.080416] init: plymouth main process (305) killed by ABRT signal
  [   21.080873] init: plymouth-splash main process (795) terminated with status 2
  [   26.593268] EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null)
  [  146.622805] init: plymouth-log main process (885) terminated with status 1
  [  146.682413] init: plymouth-upstart-bridge main process (917) terminated with status 1
  [  266.641541] init: failsafe main process (887) killed by TERM signal

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: plymouth 0.8.8-0ubuntu6
  ProcVersionSignature: Ubuntu 3.8.0-14.24~lp1157952v1-generic 3.8.4
  Uname: Linux 3.8.0-14-generic x86_64
  ApportVersion: 2.9.2-0ubuntu2
  Architecture: amd64
  BootLog: Error: [Errno 2] No such file or directory: '/var/log/boot.log'
  CurrentDmesg: [  267.056969] init: plymouth-stop pre-start process (1343) terminated with status 1
  Date: Mon Mar 25 22:39:09 2013
  DefaultPlymouth: Error: command ['readlink', '/etc/alternatives/default.plymouth'] failed with exit code 1:
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99
  MachineType: Microsoft Corporation Virtual Machine
  MarkForUpload: True
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-14-generic root=UUID=b3710ec6-2639-4979-9c91-6adf61c4289a ro console=tty1 console=ttyS0 earlyprintk=ttyS0 rootdelay=300
  ProcFB:

  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-14-generic root=UUID=b3710ec6-2639-4979-9c91-6adf61c4289a ro console=tty1 console=ttyS0 earlyprintk=ttyS0 rootdelay=300
  SourcePackage: plymouth
  TextPlymouth: /lib/plymouth/themes/ubuntu-text/ubuntu-text.plymouth
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/23/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 090006
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: 7.0
  dmi.chassis.asset.tag: 0247-9366-4976-0268-3671-4900-85
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: 7.0
  dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr090006:bd05/23/2012:svnMicrosoftCorporation:pnVirtualMachine:pvr7.0:rvnMicrosoftCorporation:rnVirtualMachine:rvr7.0:cvnMicrosoftCorporation:ct3:cvr7.0:
  dmi.product.name: Virtual Machine
  dmi.product.version: 7.0
  dmi.sys.vendor: Microsoft Corporation
  --- 
  ApportVersion: 2.9.2-0ubuntu4
  Architecture: amd64
  BootLog: Error: [Errno 2] No such file or directory: '/var/log/boot.log'
  CurrentDmesg:
   [  166.490641] init: plymouth main process (1087) killed by ABRT signal
   [  166.492124] init: plymouth-splash main process (1100) terminated with status 2
  DefaultPlymouth: Error: command ['readlink', '/etc/alternatives/default.plymouth'] failed with exit code 1:
  DistroRelease: Ubuntu 13.04
  Ec2AMI: ami-3c5bc055
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: us-east-1d
  Ec2InstanceType: t1.micro
  Ec2Kernel: aki-88aa75e1
  Ec2Ramdisk: unavailable
  Lspci:

  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99
  MarkForUpload: True
  Package: plymouth 0.8.8-0ubuntu6
  PackageArchitecture: amd64
  ProcCmdLine: root=LABEL=cloudimg-rootfs ro console=hvc0
  ProcFB:

  ProcKernelCmdLine: root=LABEL=cloudimg-rootfs ro console=hvc0
  ProcModules:
   acpiphp 23954 0 - Live 0x0000000000000000 (F)
   dm_crypt 22820 0 - Live 0x0000000000000000 (F)
   isofs 39815 0 - Live 0x0000000000000000 (F)
   microcode 22881 0 - Live 0x0000000000000000 (F)
  ProcVersionSignature: User Name 3.8.0-14.24-generic 3.8.4
  Tags:  raring ec2-images
  TextPlymouth: /lib/plymouth/themes/ubuntu-text/ubuntu-text.plymouth
  Uname: Linux 3.8.0-14-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip floppy netdev plugdev video

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