plymouthd crashed with SIGSEGV in ply_trigger_add_handler()

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

Bug Description

I'm running Saucy Development with Mir enabled from the PPA.

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: plymouth 0.8.8-0ubuntu7
ProcVersionSignature: Ubuntu 3.10.0-1.8-generic 3.10.0-rc7
Uname: Linux 3.10.0-1-generic i686
ApportVersion: 2.10.2-0ubuntu3
Architecture: i386
Date: Sat Jun 29 22:35:10 2013
DefaultPlymouth: /lib/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth
ExecutablePath: /sbin/plymouthd
InstallationDate: Installed on 2013-06-29 (0 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha i386 (20130627)
MachineType: Sony Corporation VGN-NS21Z_S
MarkForUpload: True
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.10.0-1-generic root=UUID=3eba4262-e907-4f66-9ee3-8235f88ebae4 ro quiet splash
ProcCmdline: @sbin/plymouthd --mode=boot --attach-to-session
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.10.0-1-generic root=UUID=3eba4262-e907-4f66-9ee3-8235f88ebae4 ro quiet splash
SegvAnalysis:
 Segfault happened at: 0xb7722618 <ply_trigger_add_handler+56>: mov (%eax),%eax
 PC (0xb7722618) 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/27/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: R1040Y3
dmi.board.asset.tag: N/A
dmi.board.name: VAIO
dmi.board.vendor: Sony Corporation
dmi.board.version: N/A
dmi.chassis.asset.tag: N/A
dmi.chassis.type: 10
dmi.chassis.vendor: Sony Corporation
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR1040Y3:bd08/27/2009:svnSonyCorporation:pnVGN-NS21Z_S:pvrC6U0X6A8:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
dmi.product.name: VGN-NS21Z_S
dmi.product.version: C6U0X6A8
dmi.sys.vendor: Sony Corporation

Revision history for this message
Spyros Kavvadias (thunk) wrote :
information type: Private → Public
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.

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.