plymouthd crashed with SIGSEGV in ply_event_loop_process_pending_events()

[John Belton]

I was trying to do the "update" this morning for Ubuntu 12.04 Alpha2 and it failed informong me there wasn't a desktop (strange enough as I was using the GUI to run Update Manager), then when I attempted to report it the "plymouth" crash flagged up. I am not sure if it related to others reports but those flagged up all seem to relate to previous versions of Ubuntu.
John

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: plymouth 0.8.2-2ubuntu28
ProcVersionSignature: Ubuntu 3.2.0-14.23-generic 3.2.3
Uname: Linux 3.2.0-14-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 1.91-0ubuntu1
Architecture: amd64
CurrentDmesg:
 [ 23.002305] ADDRCONF(NETDEV_UP): eth0: link is not ready
 [ 56.552049] eth1: no IPv6 routers present
 [ 59.031149] audit_printk_skb: 27 callbacks suppressed
 [ 59.031154] type=1400 audit(1328955702.332:27): apparmor="DENIED" operation="open" parent=1 profile="/usr/lib/telepathy/mission-control-5" name="/tmp/" pid=1867 comm="mission-control" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
 [ 59.031174] type=1400 audit(1328955702.332:28): apparmor="DENIED" operation="open" parent=1 profile="/usr/lib/telepathy/mission-control-5" name="/var/tmp/" pid=1867 comm="mission-control" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
Date: Fri Feb 10 20:53:42 2012
DefaultPlymouth: /lib/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth
ExecutablePath: /sbin/plymouthd
MachineType: Dell Inc. Vostro1510
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-14-generic root=UUID=BC00A89700A859E2 loop=/hostname/disks/root.disk 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-14-generic root=UUID=BC00A89700A859E2 loop=/hostname/disks/root.disk ro quiet splash vt.handoff=7
SegvAnalysis:
 Segfault happened at: 0x7f856be90504 <ply_event_loop_process_pending_events+468>: test %r12d,0x8(%r13)
 PC (0x7f856be90504) ok
 source "%r12d" ok
 destination "0x8(%r13)" (0x00000008) 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/x86_64-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: Upgraded to precise on 2012-02-11 (0 days ago)
UserGroups:

dmi.bios.date: 03/18/2009
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A15
dmi.board.name: 0M277C
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnDellInc.:bvrA15:bd03/18/2009:svnDellInc.:pnVostro1510:pvrNull:rvnDellInc.:rn0M277C:rvr:cvnDellInc.:ct8:cvrN/A:
dmi.product.name: Vostro1510
dmi.product.version: Null
dmi.sys.vendor: Dell 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.