plymouthd crashed with SIGSEGV in ply_trigger_add_handler()

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

Bug Description

crashed on initial reboot after enabling Mir's PPA

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: plymouth 0.8.8-0ubuntu7
ProcVersionSignature: Ubuntu 3.10.0-2.10-generic 3.10.0
Uname: Linux 3.10.0-2-generic i686
ApportVersion: 2.10.2-0ubuntu4
Architecture: i386
CurrentDmesg: [ 19.777344] init: plymouth main process (170) killed by SEGV signal
Date: Wed Jul 10 17:07:03 2013
DefaultPlymouth: /lib/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth
ExecutablePath: /sbin/plymouthd
MachineType: Hewlett-Packard HP Compaq dc5100 SFF(PZ578UA)
MarkForUpload: True
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.10.0-2-generic root=UUID=8729469f-84ec-4ccc-8f50-be69760033ac ro splash quiet vt.handoff=7
ProcCmdline: @sbin/plymouthd --mode=boot --attach-to-session
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.10.0-2-generic root=UUID=8729469f-84ec-4ccc-8f50-be69760033ac ro splash quiet vt.handoff=7
SegvAnalysis:
 Segfault happened at: 0xb7786618 <ply_trigger_add_handler+56>: mov (%eax),%eax
 PC (0xb7786618) ok
 source "(%eax)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: plymouth
StacktraceTop:
 ply_trigger_add_handler () from /lib/i386-linux-gnu/libply.so.2
 ?? ()
 ?? ()
 ply_event_loop_process_pending_events () from /lib/i386-linux-gnu/libply.so.2
 ply_event_loop_run () from /lib/i386-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: 08/25/2005
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 786C2 v01.07
dmi.board.name: 09E8h
dmi.board.vendor: Hewlett-Packard
dmi.chassis.type: 4
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnHewlett-Packard:bvr786C2v01.07:bd08/25/2005:svnHewlett-Packard:pnHPCompaqdc5100SFF(PZ578UA):pvr:rvnHewlett-Packard:rn09E8h:rvr:cvnHewlett-Packard:ct4:cvr:
dmi.product.name: HP Compaq dc5100 SFF(PZ578UA)
dmi.sys.vendor: Hewlett-Packard

Revision history for this message
Charlie_Smotherman (cjsmo) 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 #750405, 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-i386-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.