I have seen the other reports similar to this one, but not for 12.04. Apologies if it's simply a dupe.
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: plymouth 0.8.2-2ubuntu28
ProcVersionSignature: Ubuntu 3.2.0-4.10-generic 3.2.0-rc5
Uname: Linux 3.2.0-4-generic i686
ApportVersion: 1.90-0ubuntu1
Architecture: i386
Date: Wed Dec 14 14:09:26 2011
DefaultPlymouth: /lib/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth
ExecutablePath: /sbin/plymouthd
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha i386 (20111211)
MachineType: Dell Inc. OptiPlex GX280
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-4-generic root=UUID=a60abfd5-6e70-453b-be4e-f89073caa5c2 ro quiet splash vt.handoff=7
ProcCmdline: /sbin/plymouthd --mode=boot --attach-to-session
ProcEnviron: PATH=(custom, no user)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-4-generic root=UUID=a60abfd5-6e70-453b-be4e-f89073caa5c2 ro quiet splash vt.handoff=7
SegvAnalysis:
Segfault happened at: 0xb4e5b7 <ply_event_loop_process_pending_events+455>: test %ecx,0x4(%esi)
PC (0x00b4e5b7) ok
source "%ecx" 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 () from /lib/libply.so.2
ply_event_loop_run () from /lib/libply.so.2
?? ()
__libc_start_main () from /lib/i386-linux-gnu/libc.so.6
?? ()
TextPlymouth: /lib/plymouth/themes/ubuntu-text/ubuntu-text.plymouth
Title: plymouthd crashed with SIGSEGV in ply_event_loop_process_pending_events()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
dmi.bios.date: 02/09/2005
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A04
dmi.board.name: 0H8164
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 15
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA04:bd02/09/2005:svnDellInc.:pnOptiPlexGX280:pvr:rvnDellInc.:rn0H8164:rvr:cvnDellInc.:ct15:cvr:
dmi.product.name: OptiPlex GX280
dmi.sys.vendor: Dell Inc.
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.