plymouthd crashed with SIGSEGV in script_obj_deref_direct()
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| plymouth (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
NA
ProblemType: Crash
DistroRelease: Ubuntu 15.10
Package: plymouth 0.9.0-0ubuntu9
Uname: Linux 4.2.0-040200rc8
ApportVersion: 2.18.1-0ubuntu1
Architecture: amd64
Date: Tue Sep 15 15:24:53 2015
DefaultPlymouth: /lib/plymouth/
ExecutablePath: /sbin/plymouthd
InstallationDate: Installed on 2015-08-28 (18 days ago)
InstallationMedia: Ubuntu-Kylin 15.10 "Wily Werewolf" - Alpha amd64 (20150826)
MachineType: ASUSTeK COMPUTER INC. X550JK
ProcCmdLine: BOOT_IMAGE=
ProcCmdline: @sbin/plymouthd --mode=boot --pid-file=
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=
SegvAnalysis:
Segfault happened at: 0x7f8a1f2b0600 <script_
PC (0x7f8a1f2b0600) 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: No upgrade log present (probably fresh install)
UserGroups:
dmi.bios.date: 07/09/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: X550JK.302
dmi.board.
dmi.board.name: X550JK
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.name: X550JK
dmi.product.
dmi.sys.vendor: ASUSTeK COMPUTER 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 #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.