plymouth crashed on startup of ubuntu-mate with systemd
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
plymouth (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
to reproduce install ubuntu mate and get updates until systemd is the defualt init system. then boot into ubuntu mate using the kernel.
systemd:
Installed: 219-4ubuntu5
Candidate: 219-4ubuntu5
Version table:
*** 219-4ubuntu5 0
500 http://
100 /var/lib/
plymouth:
Installed: 0.9.0-0ubuntu9
Candidate: 0.9.0-0ubuntu9
Version table:
*** 0.9.0-0ubuntu9 0
500 http://
100 /var/lib/
I expected to boot without crashing on my laptop. Instead I had a crash on my laptop.
ProblemType: Crash
DistroRelease: Ubuntu 15.04
Package: plymouth 0.9.0-0ubuntu9
ProcVersionSign
Uname: Linux 3.19.0-7-generic x86_64
NonfreeKernelMo
ApportVersion: 2.16.2-0ubuntu2
Architecture: amd64
Date: Wed Mar 11 09:25:55 2015
DefaultPlymouth: /lib/plymouth/
ExecutablePath: /sbin/plymouthd
InstallationDate: Installed on 2015-03-06 (4 days ago)
InstallationMedia: Ubuntu-MATE 15.04 "Vivid Vervet" - Alpha amd64 (20150306)
MachineType: Hewlett-Packard HP Pavilion dv6 Notebook PC
ProcCmdLine: BOOT_IMAGE=
ProcCmdline: @sbin/plymouthd --mode=boot --pid-file=
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=
SegvAnalysis: Skipped: missing required field "Disassembly"
Signal: 11
SourcePackage: plymouth
TextPlymouth: /lib/plymouth/
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
dmi.bios.date: 08/31/2009
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.33
dmi.board.
dmi.board.name: 3627
dmi.board.vendor: Quanta
dmi.board.version: 18.42
dmi.chassis.type: 10
dmi.chassis.vendor: Quanta
dmi.chassis.
dmi.modalias: dmi:bvnHewlett-
dmi.product.name: HP Pavilion dv6 Notebook PC
dmi.product.
dmi.sys.vendor: Hewlett-Packard
Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1378284, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.