plymouthd crashed with SIGSEGV in ply_trigger_add_handler()

Bug #1200809 reported by Ken
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
plymouth (Ubuntu)
New
Undecided
Unassigned

Bug Description

Another reboot and another black screen.

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: plymouth 0.8.8-0ubuntu7
ProcVersionSignature: Ubuntu 3.10.0-2.11-generic 3.10.0
Uname: Linux 3.10.0-2-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.10.2-0ubuntu4
Architecture: amd64
CrashCounter: 1
CurrentDmesg: [ 100.404773] init: plymouth main process (1392) killed by SEGV signal
Date: Sat Jul 13 00:05:13 2013
DefaultPlymouth: /lib/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth
ExecutablePath: /sbin/plymouthd
InstallationDate: Installed on 2013-07-10 (2 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130709)
MachineType: Hewlett-Packard 520-1138cb
MarkForUpload: True
ProcCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.10.0-2-generic root=UUID=ee63e052-abe5-4316-8499-10528ed15dd7 ro recovery nomodeset rootflags=subvol=@
ProcCmdline: @sbin/plymouthd --mode=boot --attach-to-session
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
ProcFB:

ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.10.0-2-generic root=UUID=ee63e052-abe5-4316-8499-10528ed15dd7 ro recovery nomodeset rootflags=subvol=@
SegvAnalysis:
 Segfault happened at: 0x7fcfc709da4c <ply_trigger_add_handler+28>: mov (%rbx),%rdi
 PC (0x7fcfc709da4c) ok
 source "(%rbx)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: plymouth
StacktraceTop:
 ply_trigger_add_handler () from /lib/x86_64-linux-gnu/libply.so.2
 ?? ()
 ply_event_loop_process_pending_events () from /lib/x86_64-linux-gnu/libply.so.2
 ply_event_loop_run () from /lib/x86_64-linux-gnu/libply.so.2
 ?? ()
TextPlymouth: /lib/plymouth/themes/ubuntu-text/ubuntu-text.plymouth
Title: plymouthd crashed with SIGSEGV in ply_trigger_add_handler()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 11/23/2012
dmi.bios.vendor: AMI
dmi.bios.version: 7.09
dmi.board.asset.tag: 3CR22302J0
dmi.board.name: 2ADC
dmi.board.vendor: PEGATRON CORPORATION
dmi.board.version: 1.05
dmi.chassis.asset.tag: 3CR22302J0
dmi.chassis.type: 3
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnAMI:bvr7.09:bd11/23/2012:svnHewlett-Packard:pn520-1138cb:pvr1.00:rvnPEGATRONCORPORATION:rn2ADC:rvr1.05:cvnHewlett-Packard:ct3:cvr:
dmi.product.name: 520-1138cb
dmi.product.version: 1.00
dmi.sys.vendor: Hewlett-Packard

Revision history for this message
Ken (ken3-burtinsky) 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 #864430, 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
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.