plymouthd crashed with SIGSEGV in ply_list_find_node()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
plymouth (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
No info
ProblemType: Crash
DistroRelease: Ubuntu 16.10
Package: plymouth 0.9.2-3ubuntu15
ProcVersionSign
Uname: Linux 4.4.0-9136-generic x86_64
ApportVersion: 2.20.3-0ubuntu7
Architecture: amd64
Date: Tue Sep 20 11:14:29 2016
DefaultPlymouth: /usr/share/
ExecutablePath: /sbin/plymouthd
InstallationDate: Installed on 2016-04-25 (148 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: Dell Inc. XPS L322X
ProcCmdLine: BOOT_IMAGE=
ProcCmdline: @sbin/plymouthd --mode=boot --pid-file=
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=
SegvAnalysis:
Segfault happened at: 0x7fee7a3154f8 <ply_list_
PC (0x7fee7a3154f8) ok
source "(%rax)" (0xffffffff) not located in a known VMA region (needed readable region)!
destination "%rsi" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: plymouth
StacktraceTop:
ply_list_find_node () from /lib/x86_
?? () from /lib/x86_
?? () from /lib/x86_
ply_event_
ply_event_loop_run () from /lib/x86_
TextPlymouth: /usr/share/
Title: plymouthd crashed with SIGSEGV in ply_list_
UpgradeStatus: Upgraded to yakkety on 2016-08-29 (21 days ago)
UserGroups:
dmi.bios.date: 08/28/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A10
dmi.board.name: 0PJHXN
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: XPS L322X
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 #1569257, 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.