npviewer.bin crashed with SIGSEGV in g_list_find()

[Drex]

Binary package hint: nspluginwrapper

Happened on Chevy's website while looking at the Aveo5.

ProblemType: Crash
Architecture: amd64
CrashCounter: 1
Date: Thu Dec 20 19:49:38 2007
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/lib/nspluginwrapper/i386/linux/npviewer.bin
NonfreeKernelModules: nvidia
Package: nspluginwrapper 0.9.91.5-1ubuntu1
PackageArchitecture: amd64
ProcCmdline: /usr/lib/nspluginwrapper/i386/linux/npviewer.bin --plugin /usr/lib/flashplugin-nonfree/libflashplayer.so --connection /org/wrapper/NSPlugins/libflashplayer.so/22278-1
ProcCwd: /home/jonathan
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=C
 SHELL=/bin/bash
Signal: 11
SourcePackage: nspluginwrapper
StacktraceTop:
 g_list_find () from /usr/lib32/libglib-2.0.so.0
 g_object_newv () from /usr/lib32/libgobject-2.0.so.0
 g_object_new_valist () from /usr/lib32/libgobject-2.0.so.0
 g_object_new () from /usr/lib32/libgobject-2.0.so.0
 gdk_pixbuf_new_from_data ()
Title: npviewer.bin crashed with SIGSEGV in g_list_find()
Uname: Linux jonathan-desktop 2.6.22-14-generic #1 SMP Sun Oct 14 21:45:15 GMT 2007 x86_64 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video

[Apport retracing service (apport)]

StacktraceTop:g_list_find () from /usr/lib32/libglib-2.0.so.0
g_object_newv () from /usr/lib32/libgobject-2.0.so.0
g_object_new_valist () from /usr/lib32/libgobject-2.0.so.0
g_object_new () from /usr/lib32/libgobject-2.0.so.0
gdk_pixbuf_new_from_data () from /usr/lib32/libgdk_pixbuf-2.0.so.0

[sam tygier (samtygier)]

i have also seen this on amd64

[Greg Grossmeier (greg.grossmeier)]

Just happened on amd64 while watching Jono's video of a dog thrashing to metal (a flash video).

[Hew (hew)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 141613, so it 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. Feel free to continue to report any other bugs you may find.