plymouthd crashed with SIGSEGV in script_obj_deref_direct()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
plymouth (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
i915 errors in kernel log
ProblemType: Crash
DistroRelease: Ubuntu 15.10
Package: plymouth 0.9.0-0ubuntu9
ProcVersionSign
Uname: Linux 4.2.0-16-generic x86_64
NonfreeKernelMo
ApportVersion: 2.19.1-0ubuntu2
Architecture: amd64
Date: Thu Oct 15 00:31:52 2015
DefaultPlymouth: /lib/plymouth/
ExecutablePath: /sbin/plymouthd
MachineType: Hewlett-Packard 300-016d
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:
Segfault happened at: 0x7f65292ae600 <script_
PC (0x7f65292ae600) ok
source "$0x1" ok
destination "(%rdi)" (0x00000001) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: plymouth
StacktraceTop:
script_
script_
script_
script_
?? () from /lib/x86_
TextPlymouth: /lib/plymouth/
Title: plymouthd crashed with SIGSEGV in script_
UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
UpgradeStatus: Upgraded to wily on 2015-10-06 (8 days ago)
UserGroups:
dmi.bios.date: 12/15/2014
dmi.bios.vendor: AMI
dmi.bios.version: 80.03
dmi.board.
dmi.board.name: 2B38
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 1.02
dmi.chassis.
dmi.chassis.type: 3
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnAMI:
dmi.product.name: 300-016d
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 #1417523, 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.