plymouthd crashed with SIGSEGV in script_obj_deref_direct()
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| plymouth (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
Never noticed it.
ProblemType: Crash
DistroRelease: Ubuntu 15.10
Package: plymouth 0.9.0-0ubuntu9
ProcVersionSign
Uname: Linux 4.2.0-27-generic x86_64
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
Date: Wed Feb 17 13:10:37 2016
DefaultPlymouth: /lib/plymouth/
ExecutablePath: /sbin/plymouthd
InstallationDate: Installed on 2014-09-07 (527 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
MachineType: LENOVO 20B3001VPG
ProcCmdLine: BOOT_IMAGE=
ProcCmdline: @sbin/plymouthd --mode=boot --pid-file=
ProcFB:
0 inteldrmfb
1 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=
SegvAnalysis:
Segfault happened at: 0x7f7748605600 <script_
PC (0x7f7748605600) 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_
UpgradeStatus: Upgraded to wily on 2015-11-27 (81 days ago)
UserGroups:
dmi.bios.date: 03/20/2015
dmi.bios.vendor: LENOVO
dmi.bios.version: GPET64WW (1.64 )
dmi.board.
dmi.board.name: 20B3001VPG
dmi.board.vendor: LENOVO
dmi.board.version: 0B98401 Pro
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.
dmi.modalias: dmi:bvnLENOVO:
dmi.product.name: 20B3001VPG
dmi.product.
dmi.sys.vendor: LENOVO

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.