npviewer.bin crashed with SIGSEGV in g_option_context_get_help()

[Bordi]

Binary package hint: nspluginwrapper

user@xubuntu64:~$ lsb_release -rd
Description: Ubuntu lucid (development branch)
Release: 10.04

user@xubuntu64:~$ uname -a
Linux ubuntu64 2.6.34-020634rc3-generic #020634rc3 SMP Tue Apr 6 17:31:12 UTC 2010 x86_64 GNU/Linux

ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: nspluginwrapper 1.2.2-0ubuntu6
Uname: Linux 2.6.34-020634rc3-generic x86_64
Architecture: amd64
Date: Sun Apr 4 06:10:29 2010
ExecutablePath: /usr/lib/nspluginwrapper/i386/linux/npviewer.bin
ProcCmdline: /usr/lib/nspluginwrapper/i386/linux/npviewer.bin --plugin /usr/lib/flashplugin-installer/libflashplayer.so --connection /org/wrapper/NSPlugins/libflashplayer.so/1494-1
ProcEnviron:
 LANG=de_CH.utf8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0xf5f09761: mov (%esi),%eax
 PC (0xf5f09761) ok
 source "(%esi)" (0xf4dfd000) in non-readable VMA region: 0xf4dfd000-0xf50ab000 ---p None
 destination "%eax" ok
SegvReason: reading VMA None
Signal: 11
SourcePackage: nspluginwrapper
StacktraceTop:
 ?? () from /lib32/libglib-2.0.so.0
 g_option_context_get_help () from /lib32/libglib-2.0.so.0
 gtk_icon_theme_get_icon_sizes ()
 ?? ()
 __libc_start_main () from /lib32/libc.so.6
Title: npviewer.bin crashed with SIGSEGV in g_option_context_get_help()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XsessionErrors:
 (xfce4-mixer-plugin:1377): libxfce4mixer-CRITICAL **: xfce_mixer_get_track: assertion `GST_IS_MIXER (card)' failed
 (polkit-gnome-authentication-agent-1:1445): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed

[Apport retracing service (apport)]

StacktraceTop:
 ?? () from /lib32/libglib-2.0.so.0
 g_option_context_get_help () from /lib32/libglib-2.0.so.0
 gtk_icon_theme_get_icon_sizes ()
 main (argc=1, argv=0xff7fd494)

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