Ubuntu
plymouth package

plymouthd crashed with SIGSEGV in ply_trigger_add_handler()

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

Bug Description

Bug in Ubuntu 13.04

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: plymouth 0.8.8-0ubuntu6
ProcVersionSignature: Ubuntu 3.8.0-15.25-generic 3.8.4
Uname: Linux 3.8.0-15-generic i686
ApportVersion: 2.9.2-0ubuntu5
Architecture: i386
CrashCounter: 1
Date: Sun Mar 31 10:21:07 2013
DefaultPlymouth: /lib/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth
ExecutablePath: /sbin/plymouthd
InstallationDate: Installed on 2013-03-16 (14 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha i386 (20130316)
MachineType: Acer Aspire 4750
MarkForUpload: True
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-15-generic root=UUID=08a39ce5-1f27-41ba-bd5c-f2a8502636a6 ro quiet splash 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.8.0-15-generic root=UUID=08a39ce5-1f27-41ba-bd5c-f2a8502636a6 ro quiet splash vt.handoff=7
SegvAnalysis:
 Segfault happened at: 0xb76c4ac8 <ply_trigger_add_handler+56>: mov (%eax),%eax
 PC (0xb76c4ac8) 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: 02/18/2011
dmi.bios.vendor: Phoenix Technologies Ltd.
dmi.bios.version: V1.19
dmi.board.asset.tag: No Asset Tag
dmi.board.name: Aspire 4750
dmi.board.vendor: Acer
dmi.board.version: V1.19
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: Acer
dmi.chassis.version: V1.19
dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrV1.19:bd02/18/2011:svnAcer:pnAspire4750:pvrV1.19:rvnAcer:rnAspire4750:rvrV1.19:cvnAcer:ct9:cvrV1.19:
dmi.product.name: Aspire 4750
dmi.product.version: V1.19
dmi.sys.vendor: Acer

Revision history for this message
utpal (utpal-dr) 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.
Subscribing...

Other bug subscribers

Remote bug watches

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