plymouthd crashed with SIGSEGV in ply_list_find_node()

Bug #1625536 reported by Silvio Bierman
14
This bug affects 2 people
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
ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16
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/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth
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=/boot/vmlinuz-4.4.0-9136-generic root=UUID=986d7cf4-2abe-40a6-ad34-707133fe72d5 ro quiet splash vt.handoff=7
ProcCmdline: @sbin/plymouthd --mode=boot --pid-file=/run/plymouth/pid --attach-to-session
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-9136-generic root=UUID=986d7cf4-2abe-40a6-ad34-707133fe72d5 ro quiet splash vt.handoff=7
SegvAnalysis:
 Segfault happened at: 0x7fee7a3154f8 <ply_list_find_node+8>: cmp (%rax),%rsi
 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_64-linux-gnu/libply.so.4
 ?? () from /lib/x86_64-linux-gnu/libply.so.4
 ?? () from /lib/x86_64-linux-gnu/libply-splash-core.so.4
 ply_event_loop_process_pending_events () from /lib/x86_64-linux-gnu/libply.so.4
 ply_event_loop_run () from /lib/x86_64-linux-gnu/libply.so.4
TextPlymouth: /usr/share/plymouth/themes/ubuntu-text/ubuntu-text.plymouth
Title: plymouthd crashed with SIGSEGV in ply_list_find_node()
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.version: 0.1
dmi.modalias: dmi:bvnDellInc.:bvrA10:bd08/28/2013:svnDellInc.:pnXPSL322X:pvr:rvnDellInc.:rn0PJHXN:rvrA00:cvnDellInc.:ct8:cvr0.1:
dmi.product.name: XPS L322X
dmi.sys.vendor: Dell Inc.

Revision history for this message
Silvio Bierman (sbierman) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

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.

information type: Private → Public
tags: removed: need-amd64-retrace
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in plymouth (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.