plymouth crashes on start of live session

[Lyn Perrine]

start the live session of the iso from zsync http://cdimage.ubuntu.com/daily-live/20150127/vivid-desktop-amd64.iso.zsync

Then press try ubuntu and wait for session to start. Only get wall paper and no launcher. Right clicking on desktop and opening a terminal and running dmesg shows that plymouth-upstart bridge was killed by term. and the systems boots with a wallpaper and no launcher. And only way I reproted this bug was right clicking on desktop for a terminal and running ubuntu-bug. No window manager appears to be running as well so is impossible to switch between windows without starting one.

plymouth:
  Installed: 0.9.0-0ubuntu8
  Candidate: 0.9.0-0ubuntu8
  Version table:
 *** 0.9.0-0ubuntu8 0
        500 http://archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages
        100 /var/lib/dpkg/status
I expected to have unity in the live environemnt instead I just haed a wallpaper.

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: plymouth 0.9.0-0ubuntu8
ProcVersionSignature: Ubuntu 3.18.0-11.12-generic 3.18.3
Uname: Linux 3.18.0-11-generic x86_64
ApportVersion: 2.15.1-0ubuntu4
Architecture: amd64
CasperVersion: 1.349
CurrentDesktop: Unity
Date: Tue Jan 27 20:25:59 2015
DefaultPlymouth: /lib/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth
LiveMediaBuild: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150127)
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcCmdLine: file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity
SourcePackage: plymouth
TextPlymouth: /lib/plymouth/themes/ubuntu-text/ubuntu-text.plymouth
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/25/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.00
dmi.board.name: H97M Pro4
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.00:bd04/25/2014:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH97MPro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.

[Ubuntu QA Website (ubuntuqa)]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1415200

[Brian Murray (brian-murray)]

Is there a crash report in /var/crash/ corresponding to the crash of plymouth-upstart-bridge?

[Steve Langasek (vorlon)]

plymouth-upstart-crash starts very early in boot, and will regularly crash before apport has initialized. This is unfortunately going to require debugging without the benefit of an apport crash report.

[Lyn Perrine (walterorlin)]

Yeah this happened before apport was intialized and /var/crash was empty.

[Mathieu Trudel-Lapierre (cyphermox)]

Do you get his as well on a recent iso image? I can't reproduce this in kvm, so it would be nice to be sure if this happens only on hardware.

[Lyn Perrine (walterorlin)]

I don't get this on the same hardware that reproduced the crash seems like something got updated and now works.