npviewer.bin crashed with SIGSEGV in pa_mainloop_run()

[Richard Ayotte]

Binary package hint: nspluginwrapper

I was viewing this page in a tab http://www.mobilecomputermag.co.uk/20080701637/msi-wind-hands-on-video-and-aspire-one/eee-pc-901-comparisons.html and crash happened when I closed the tab.

I can no longer play flash content until Firefox is restarted.

ProblemType: Crash
Architecture: amd64
Date: Wed Jul 2 05:58:17 2008
Disassembly: 0xfd3e4993:
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/lib/nspluginwrapper/i386/linux/npviewer.bin
NonfreeKernelModules: nvidia
Package: nspluginwrapper 0.9.91.5-2ubuntu2 [modified: usr/lib/nspluginwrapper/x86_64/linux/npconfig usr/lib/nspluginwrapper/i386/linux/npviewer.bin]
PackageArchitecture: amd64
ProcCmdline: /usr/lib/nspluginwrapper/i386/linux/npviewer.bin --plugin /usr/lib/flashplugin-nonfree/libflashplayer.so --connection /org/wrapper/NSPlugins/libflashplayer.so/7209-2
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: nspluginwrapper
StacktraceTop:
 ?? ()
 pa_mainloop_run () from /usr/lib32/libpulse.so.0
 ?? () from /usr/lib32/libpulse.so.0
 ?? () from /usr/lib32/libpulse.so.0
 start_thread () from /lib32/libpthread.so.0
Title: npviewer.bin crashed with SIGSEGV in pa_mainloop_run()
Uname: Linux 2.6.24-19-generic x86_64
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin mythtv netdev plugdev powerdev sambashare scanner vboxusers video

[Apport retracing service (apport)]

StacktraceTop:?? ()
pa_mainloop_run () from /usr/lib32/libpulse.so.0
?? () from /usr/lib32/libpulse.so.0
?? () from /usr/lib32/libpulse.so.0
start_thread () from /lib32/libpthread.so.0

[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!.