plymouthd crashed with SIGSEGV in script_obj_deref_direct()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
plymouth (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
The crash report come upon startup of a fully patched 15.04 installation..
ProblemType: Crash
DistroRelease: Ubuntu 15.04
Package: plymouth 0.9.0-0ubuntu9
ProcVersionSign
Uname: Linux 3.19.0-9-generic x86_64
ApportVersion: 2.16.2-0ubuntu4
Architecture: amd64
Date: Tue Mar 24 19:51:12 2015
DefaultPlymouth: /lib/plymouth/
ExecutablePath: /sbin/plymouthd
InstallationDate: Installed on 2015-03-24 (0 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150318)
MachineType: Hewlett-Packard HP Compaq 6730b (KU489ET#ABD)
ProcCmdLine: BOOT_IMAGE=
ProcCmdline: @sbin/plymouthd --mode=boot --pid-file=
ProcEnviron:
LANG=de_DE.UTF-8
PATH=(custom, no user)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=
SegvAnalysis:
Segfault happened at: 0x7fb5066b4600 <script_
PC (0x7fb5066b4600) ok
source "$0x1" ok
destination "(%rdi)" (0x62662f736369
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: plymouth
StacktraceTop:
script_
script_
script_
script_
_start ()
TextPlymouth: /lib/plymouth/
Title: plymouthd crashed with SIGSEGV in script_
UdevLog: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: '/var/log/udev'
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
dmi.bios.date: 09/18/2008
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68PDD Ver. F.08
dmi.board.name: 30DD
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 96.18
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnHewlett-
dmi.product.name: HP Compaq 6730b (KU489ET#ABD)
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 #927636, 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.