plymouthd crashed with SIGSEGV in ply_trigger_add_handler()

[fatih sukran]

plymouth not working..

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: plymouth 0.8.8-0ubuntu7
ProcVersionSignature: Ubuntu 3.10.0-2.9-generic 3.10.0
Uname: Linux 3.10.0-2-generic x86_64
ApportVersion: 2.10.2-0ubuntu3
Architecture: amd64
CrashCounter: 1
Date: Fri Jul 5 14:34:19 2013
DefaultPlymouth: /lib/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth
ExecutablePath: /sbin/plymouthd
InstallationDate: Installed on 2013-07-03 (1 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130702)
Lsusb:
 Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
 Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 001 Device 003: ID 2232:1028
MachineType: SAMSUNG ELECTRONICS CO., LTD. 300E4A/300E5A/300E7A/3430EA/3530EA
MarkForUpload: True
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.10.0-2-generic root=UUID=abb6456a-f92f-4071-bbc6-64c53470a816 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=abb6456a-f92f-4071-bbc6-64c53470a816 ro quiet splash vt.handoff=7
SegvAnalysis:
 Segfault happened at: 0x7f61e270ca4c <ply_trigger_add_handler+28>: mov (%rbx),%rdi
 PC (0x7f61e270ca4c) 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/02/2012
dmi.bios.vendor: Phoenix Technologies Ltd.
dmi.bios.version: 09QA
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 300E4A/300E5A/300E7A/3430EA/3530EA
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: FAB1
dmi.chassis.asset.tag: Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: 0.1
dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr09QA:bd11/02/2012:svnSAMSUNGELECTRONICSCO.,LTD.:pn300E4A/300E5A/300E7A/3430EA/3530EA:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rn300E4A/300E5A/300E7A/3430EA/3530EA:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
dmi.product.name: 300E4A/300E5A/300E7A/3430EA/3530EA
dmi.product.version: 0.1
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

[Apport retracing service (apport)]

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.