plymouthd crashed with SIGSEGV in ply_event_loop_process_pending_events()

[KaiserSoze]

Binary package hint: plymouth

.

ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: plymouth 0.8.1-4
ProcVersionSignature: Ubuntu 2.6.32-19.28-generic 2.6.32.10+drm33.1
Uname: Linux 2.6.32-19-generic i686
Architecture: i386
Date: Fri Apr 2 09:26:25 2010
DefaultPlymouth: /lib/plymouth/themes/kubuntu-logo/kubuntu-logo.plymouth
ExecutablePath: /sbin/plymouthd
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
MachineType: Packard Bell BV EasyNote_BU45
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-19-generic root=UUID=2d599b57-c5f3-4b7e-80f9-a3109900544d ro quiet splash
ProcCmdline: /sbin/plymouthd --mode=boot --attach-to-session
ProcEnviron: PATH=(custom, no user)
ProcFB: 0 inteldrmfb
SegvAnalysis:
 Segfault happened at: 0x9fefe1 <ply_event_loop_process_pending_events+513>: test %eax,0x4(%esi)
 PC (0x009fefe1) ok
 source "%eax" ok
 destination "0x4(%esi)" (0x00000004) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: plymouth
StacktraceTop:
 ply_event_loop_process_pending_events ()
 ply_event_loop_run () from /lib/libply.so.2
 ?? ()
 __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
 ?? ()
TextPlymouth: /lib/plymouth/themes/ubuntu-text/ubuntu-text.plymouth
Title: plymouthd crashed with SIGSEGV in ply_event_loop_process_pending_events()
UserGroups:

dmi.bios.date: 05/11/2007
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 206
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: T13FV
dmi.board.vendor: Packard Bell BV
dmi.board.version: 1.0
dmi.chassis.type: 10
dmi.chassis.vendor: Packard Bell BV
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr206:bd05/11/2007:svnPackardBellBV:pnEasyNote_BU45:pvrPB72E06310:rvnPackardBellBV:rnT13FV:rvr1.0:cvnPackardBellBV:ct10:cvr:
dmi.product.name: EasyNote_BU45
dmi.product.version: PB72E06310
dmi.sys.vendor: Packard Bell BV

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #553745, 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.