plymouthd crashed with SIGSEGV in ply_trigger_add_handler()

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

Bug Description

Before finishing to load the start screen I got message that stated that there was a problem. Upgrade to 13.10 and enabling mir.

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
CrashCounter: 1
CurrentDmesg: [ 16.957310] init: plymouth main process (153) killed by SEGV signal
Date: Wed Jul 10 23:35:55 2013
DefaultPlymouth: /lib/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth
ExecutablePath: /sbin/plymouthd
InstallationDate: Installed on 2013-04-14 (86 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha i386 (20130414)
MachineType: TOSHIBA dynabook SS S30 106S/2W
MarkForUpload: True
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.10.0-2-generic root=UUID=2b6783e2-ade1-4e20-80d4-c677741d7b00 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.10.0-2-generic root=UUID=2b6783e2-ade1-4e20-80d4-c677741d7b00 ro quiet splash vt.handoff=7
SegvAnalysis:
 Segfault happened at: 0xb770a618 <ply_trigger_add_handler+56>: mov (%eax),%eax
 PC (0xb770a618) 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: Upgraded to saucy on 2013-07-10 (0 days ago)
UserGroups:

dmi.bios.date: 12/20/2006
dmi.bios.vendor: TOSHIBA
dmi.bios.version: Version 3.20
dmi.board.name: Portable PC
dmi.board.vendor: TOSHIBA
dmi.board.version: Version A0
dmi.chassis.asset.tag: 0000000000
dmi.chassis.type: 10
dmi.chassis.vendor: TOSHIBA
dmi.chassis.version: Version 1.0
dmi.modalias: dmi:bvnTOSHIBA:bvrVersion3.20:bd12/20/2006:svnTOSHIBA:pndynabookSSS30106S/2W:pvrPPS301CSPN6UK:rvnTOSHIBA:rnPortablePC:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0:
dmi.product.name: dynabook SS S30 106S/2W
dmi.product.version: PPS301CSPN6UK
dmi.sys.vendor: TOSHIBA

Revision history for this message
Alejandro (aleoliva) 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.