npviewer.bin crashed with SIGSEGV

[luiscgraciap]

Binary package hint: nspluginwrapper

I dont know because present this error, simply the error appears suddenly

ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: nspluginwrapper 1.2.2-0ubuntu6
ProcVersionSignature: Ubuntu 2.6.31-20.58-generic
Uname: Linux 2.6.31-20-generic x86_64
Architecture: amd64
CrashCounter: 1
Date: Thu Apr 8 17:33:19 2010
Disassembly: => 0xff999ea8: No se puede acceder a la memoria en la dirección 0xff999ea8
ExecutablePath: /usr/lib/nspluginwrapper/i386/linux/npviewer.bin
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
ProcCmdline: /usr/lib/nspluginwrapper/i386/linux/npviewer.bin --plugin /usr/lib/flashplugin-installer/libflashplayer.so --connection /org/wrapper/NSPlugins/libflashplayer.so/5018-1
ProcEnviron:
 LANG=es_CO.utf8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0xff999ea8: No se puede acceder a la memoria en la dirección 0xff999ea8
 PC (0xff999ea8) not located in a known VMA region (needed executable region)!
 source "0xff999ea8" (0xff999ea8) not located in a known VMA region (needed readable region)!
SegvReason:
 executing unknown VMA
 reading unknown VMA
Signal: 11
SourcePackage: nspluginwrapper
StacktraceTop:
 ?? ()
 ?? () from /usr/lib/flashplugin-installer/libflashplayer.so
 ?? () from /usr/lib/flashplugin-installer/libflashplayer.so
 ?? () from /usr/lib/flashplugin-installer/libflashplayer.so
 ?? () from /usr/lib/flashplugin-installer/libflashplayer.so
Title: npviewer.bin crashed with SIGSEGV
UserGroups: adm admin audio cdrom dialout dip fax fuse lpadmin netdev plugdev sambashare tape vboxusers video

[Apport retracing service (apport)]

StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()

[Pedro Villavicencio (pedro)]

Thanks for your bug report. Please try to obtain a backtrace http://wiki.ubuntu.com/DebuggingProgramCrash and attach the file to the bug report. This will greatly help us in tracking down your problem.

[Pedro Villavicencio (pedro)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to New. Thanks again!.