gnome-alsamixer crashed with SIGSEGV in g_cclosure_marshal_VOID__VOID()

[hazard]

Binary package hint: gnome-alsamixer

I just upgraded from Ubuntu 9.04 to Ubuntu 9.10 and there is no sound. After I open alsa mixer it suddenly crashed and gave this error.

ProblemType: Crash
Architecture: i386
Date: Fri Oct 30 23:31:11 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/gnome-alsamixer
NonfreeKernelModules: nvidia
Package: gnome-alsamixer 0.9.7~cvs.20060916.ds.1-2
ProcCmdline: gnome-alsamixer
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.28-14.47-generic
SegvAnalysis:
 Segfault happened at: 0x804cd44: mov (%ebx),%eax
 PC (0x0804cd44) ok
 source "(%ebx)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-alsamixer
StacktraceTop:
 ?? ()
 g_cclosure_marshal_VOID__VOID ()
 g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
 ?? () from /usr/lib/libgobject-2.0.so.0
 g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0
Title: gnome-alsamixer crashed with SIGSEGV in g_cclosure_marshal_VOID__VOID()
Uname: Linux 2.6.28-14-generic i686
UserGroups: adm admin audio cdrom dialout dip lpadmin netdev plugdev sambashare video

[bhaskaran (bhaskaran)]

I just upgraded from Ubuntu 9.04 to Ubuntu 9.10 and there is no sound. After I open alsa mixer it suddenly crashed.

[Glasterfairyan (glasterfairyan)]

Same problem here and I don't seem to be getting any further with it. I can hear sound if my speakers are turned up full but it's ridiculously quiet.

[Apport retracing service (apport)]

StacktraceTop:gam_mixer_show_props_dialog (gam_mixer=0x0)
g_cclosure_marshal_VOID__VOID ()
g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
?? () from /usr/lib/libgobject-2.0.so.0
g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0

[Brian Murray (brian-murray)]

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 448180, 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. Please continue to report any other bugs you may find.