plymouthd crashed with SIGSEGV in ply_event_loop_process_pending_events()

[Rick Spencer]

dist-upgrade today, this error was present on log in

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: plymouth 0.8.2-2ubuntu28
ProcVersionSignature: Ubuntu 3.2.0-20.33-generic 3.2.12
Uname: Linux 3.2.0-20-generic x86_64
ApportVersion: 1.95-0ubuntu1
Architecture: amd64
Date: Wed Mar 28 09:51:32 2012
DefaultPlymouth: /lib/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth
ExecutablePath: /sbin/plymouthd
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110919)
MachineType: ASUSTeK Computer Inc. K53SV
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-20-generic root=UUID=68acdf0d-02e3-4c78-9bd6-ea98eef41652 ro quiet splash vt.handoff=7
ProcCmdline: /sbin/plymouthd --mode=boot --attach-to-session
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
ProcFB:
 0 inteldrmfb
 1 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-20-generic root=UUID=68acdf0d-02e3-4c78-9bd6-ea98eef41652 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-01-06 (81 days ago)
UserGroups:

dmi.bios.date: 06/17/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: K53SV.302
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: K53SV
dmi.board.vendor: ASUSTeK Computer Inc.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: ASUSTeK Computer Inc.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrK53SV.302:bd06/17/2011:svnASUSTeKComputerInc.:pnK53SV:pvr1.0:rvnASUSTeKComputerInc.:rnK53SV:rvr1.0:cvnASUSTeKComputerInc.:ct9:cvr1.0:
dmi.product.name: K53SV
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK Computer Inc.

[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.