Hi,

Were I only skilled enough to do so!!

I'm OK at reporting problems, but not much beyond that. Is there another way
I could help?

Thanks, Rick :-)

On Tue, Apr 5, 2011 at 4:42 AM, Colin Watson <email address hidden> wrote:

> On Mon, Apr 04, 2011 at 07:36:36PM -0000, Greg Auger wrote:
> > I just got redirected to this bug (by Apport) despite having
> > 0.8.2-2ubuntu21 installed.
>
> Could you file a new bug using Apport and post the bug number, please?
> I want to analyse the stack trace separately, even if Apport thinks that
> it looks like this one.
>
> (This is the kind of bug that I expect could be caused in a few
> different ways; it wouldn't surprise me if I'd plugged some of the holes
> but missed others.)
>
> --
> You received this bug notification because you are a direct subscriber
> of a duplicate bug (710974).
> https://bugs.launchpad.net/bugs/553745
>
> Title:
>  plymouthd crashed with SIGSEGV in
>  ply_event_loop_process_pending_events()
>
> Status in The Plymouth splash screen:
>  Confirmed
> Status in “plymouth” package in Ubuntu:
>  Fix Released
> Status in “plymouth” source package in Lucid:
>  Triaged
> Status in “plymouth” source package in Maverick:
>  Triaged
> Status in “plymouth” source package in Natty:
>  Fix Released
>
> Bug description:
>  Binary package hint: plymouth
>
>  just upgraded to lucid, first reboot tried to start accounts
>
>  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
>  NonfreeKernelModules: wl
>  Architecture: i386
>  Date: Thu Apr  1 22:14:11 2010
>  DefaultPlymouth: /lib/plymouth/themes/kubuntu-logo/kubuntu-logo.plymouth
>  ExecutablePath: /sbin/plymouthd
>  MachineType: Dell Inc. Inspiron 1545
>  ProcCmdLine: root=UUID=73530dc8-e3cc-4147-b801-4725b2f88141 ro quiet
> splash vga=792
>  ProcCmdline: /sbin/plymouthd --mode=boot --attach-to-session
>  ProcEnviron: PATH=(custom, no user)
>  ProcFB: 0 inteldrmfb
>  SegvAnalysis:
>   Segfault happened at: 0xfb5fe1
> <ply_event_loop_process_pending_events+513>: test   %eax,0x4(%esi)
>   PC (0x00fb5fe1) 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: 07/17/2009
>  dmi.bios.vendor: Dell Inc.
>  dmi.bios.version: A10
>  dmi.board.name: 0G848F
>  dmi.board.vendor: Dell Inc.
>  dmi.chassis.type: 8
>  dmi.chassis.vendor: Dell Inc.
>  dmi.modalias:
> dmi:bvnDellInc.:bvrA10:bd07/17/2009:svnDellInc.:pnInspiron1545:pvr:rvnDellInc.:rn0G848F:rvr:cvnDellInc.:ct8:cvr:
>  dmi.product.name: Inspiron 1545
>  dmi.sys.vendor: Dell Inc.
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/plymouth/+bug/553745/+subscribe
>