gnome-alsamixer crashed with SIGSEGV in gtk_accel_group_connect_by_path()

[Doffe]

Followed instructions from
https://help.ubuntu.com/community/MacBookPro6-2/Oneiric#Install

Sound was very quiet so tried to install alsa mixer. Can not start it.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: gnome-alsamixer 0.9.7~cvs.20060916.ds.1-2ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4
Uname: Linux 3.0.0-11-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 1.23-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Sun Sep 25 16:53:40 2011
ExecutablePath: /usr/bin/gnome-alsamixer
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64+mac (20110921.2)
ProcCmdline: gnome-alsamixer
ProcEnviron:
 LANGUAGE=en_AU:en
 PATH=(custom, no user)
 LANG=en_AU.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f8b315b0f10: mov 0x20(%r12),%rdi
 PC (0x7f8b315b0f10) ok
 source "0x20(%r12)" (0x00000020) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-alsamixer
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
 gtk_accel_group_connect_by_path () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
 gtk_action_connect_accelerator () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
Title: gnome-alsamixer crashed with SIGSEGV in gtk_accel_group_connect_by_path()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #849415, so 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.