npviewer.bin crashed with SIGSEGV

[KrzysiekT]

Binary package hint: nspluginwrapper

again a problem with flash, with ad on some page

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: nspluginwrapper 1.2.2-0ubuntu6
ProcVersionSignature: Ubuntu 2.6.35-19.28-generic 2.6.35.3
Uname: Linux 2.6.35-19-generic x86_64
Architecture: amd64
CrashCounter: 1
Date: Sat Sep 4 02:38:38 2010
EcryptfsInUse: Yes
ExecutablePath: /usr/lib/nspluginwrapper/i386/linux/npviewer.bin
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
ProcCmdline: /usr/lib/nspluginwrapper/i386/linux/npviewer.bin --plugin /usr/lib/flashplugin-installer/libflashplayer.so --connection /org/wrapper/NSPlugins/libflashplayer.so/3822-1
ProcEnviron:
 LANG=pl_PL.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0xf61d4733: mov 0x24(%edx),%eax
 PC (0xf61d4733) ok
 source "0x24(%edx)" (0xf2e5a054) in non-readable VMA region: 0xf2e58000-0xf2e66000 ---p None
 destination "%eax" ok
SegvReason: reading VMA None
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
 ?? () from /usr/lib/flashplugin-installer/libflashplayer.so
Title: npviewer.bin crashed with SIGSEGV
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Vallery Lancey (muscovy)]

Thank you for reporting this bug to help make Ubuntu better. You seem to have reported the same bug twice, so to avoid confusion, I'm going to mark this copy as a duplicate of the other. Farther discussion will take place at https://bugs.launchpad.net/ubuntu/+source/nspluginwrapper/+bug/629945

Thank you!

[KrzysiekT (cytruss-xl)]

  W dniu 04.09.2010 03:14, Alexander Lancey pisze:
> *** This bug is a duplicate of bug 629945 ***
> https://bugs.launchpad.net/bugs/629945
>
> Thank you for reporting this bug to help make Ubuntu better. You seem to
> have reported the same bug twice,
Thanks