plymouthd crashed with SIGSEGV in script_obj_deref_direct()
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| plymouth (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
Description: Ubuntu 15.10
Release: 15.10
Package-name:
plymouth:
Installed: 0.9.0-0ubuntu9
Candidate: 0.9.0-0ubuntu9
Version table:
*** 0.9.0-0ubuntu9 0
500 http://
100 /var/lib/
ProblemType: Crash
ProblemType: Crash
DistroRelease: Ubuntu 15.10
Package: plymouth 0.9.0-0ubuntu9
ProcVersionSign
Uname: Linux 4.2.0-25-generic x86_64
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
Date: Fri Jan 29 09:18:39 2016
DefaultPlymouth: /lib/plymouth/
ExecutablePath: /sbin/plymouthd
InstallationDate: Installed on 2014-11-25 (429 days ago)
InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
MachineType: Dell Inc. Inspiron 5521
ProcCmdLine: BOOT_IMAGE=
ProcCmdline: @sbin/plymouthd --mode=boot --pid-file=
ProcEnviron:
LANG=en_IN
LANGUAGE=en_IN:en
PATH=(custom, no user)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=
SegvAnalysis:
Segfault happened at: 0x7fa596d8f600 <script_
PC (0x7fa596d8f600) ok
source "$0x1" ok
destination "(%rdi)" (0x00000000) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: plymouth
StacktraceTop:
script_
script_
script_
script_
_start ()
TextPlymouth: /lib/plymouth/
Title: plymouthd crashed with SIGSEGV in script_
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
dmi.bios.date: 07/31/2015
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A14
dmi.board.name: 0K08H3
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.
dmi.modalias: dmi:bvnDellInc.
dmi.product.name: Inspiron 5521
dmi.product.
dmi.sys.vendor: Dell Inc.

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.