plymouthd crashed with SIGSEGV in ply_event_loop_process_pending_events()

[Ken Forbes]

bug occured when opening Update Manager

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: plymouth 0.8.2-2ubuntu28
ProcVersionSignature: Ubuntu 3.2.0-20.32-generic 3.2.12
Uname: Linux 3.2.0-20-generic i686
NonfreeKernelModules: wl
ApportVersion: 1.95-0ubuntu1
Architecture: i386
Date: Thu Mar 15 12:15:00 2012
DefaultPlymouth: /lib/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth
ExecutablePath: /sbin/plymouthd
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
MachineType: Hewlett-Packard HP Mini
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-20-generic root=UUID=667f1bee-5990-450c-b831-f9d91ee70da1 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.2.0-20-generic root=UUID=667f1bee-5990-450c-b831-f9d91ee70da1 ro quiet splash vt.handoff=7
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: plymouth
TextPlymouth: /lib/plymouth/themes/ubuntu-text/ubuntu-text.plymouth
Title: plymouthd crashed with SIGSEGV in ply_event_loop_process_pending_events()
UpgradeStatus: Upgraded to precise on 2012-03-05 (18 days ago)
UserGroups:

dmi.bios.date: 11/07/2008
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 361A0 Ver. F.05
dmi.board.name: 361A
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 02.0D
dmi.chassis.asset.tag: CNU85143Q3
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnHewlett-Packard:bvr361A0Ver.F.05:bd11/07/2008:svnHewlett-Packard:pnHPMini:pvrF.05:rvnHewlett-Packard:rn361A:rvrKBCVersion02.0D:cvnHewlett-Packard:ct10:cvr:
dmi.product.name: HP Mini
dmi.product.version: F.05
dmi.sys.vendor: Hewlett-Packard

[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 #849414, 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.