gnome-volume-control crashed with SIGABRT in raise() - WHEN TRIED TO TEST SPEAKERS

[Daniel Quirino]

Clean UBUNTU 11.04, boot from pen drive, fresh install (first boot), no drivers or software installed.

Gone to SOUND PREFERENCES, clicked on HARDWARE, TEST SPEAKERS, (DIGITAL STEREO (HDMI) was the default) it showed the 2 speakers, but no sound when tested. So i changed to DIGITAL SURROUND 5.1 (HDMI). When clicked on TEST SPEAKERS, it crashed.

From now on, all options i tries (DIGITAL STEREO (HDMI), DIGITAL STEREO (HDMI) nr2, DIGITAL STEREO (HDMI) nr3, DIGITAL STEREO (HDMI) nr4, DIGITAL SURROUND 5.1 (HDMI), DIGITAL SURROUND 5.1 (HDMI) nr2, DIGITAL SURROUND 5.1 (HDMI) nr3, DIGITAL SURROUND 5.1 (HDMI) nr4) crashes when click on TEST SPEAKERS.

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: gnome-media 2.32.0-0ubuntu7
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic x86_64
Architecture: amd64
CrashCounter: 1
Date: Sun Sep 25 15:06:42 2011
ExecutablePath: /usr/bin/gnome-volume-control
LiveMediaBuild: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
ProcCmdline: gnome-volume-control --page=applications
ProcEnviron:
 SHELL=/bin/bash
 LANGUAGE=en_US:en
 LANG=en_US.UTF-8
Signal: 6
SourcePackage: gnome-media
StacktraceTop:
 raise () from /lib/x86_64-linux-gnu/libc.so.6
 abort () from /lib/x86_64-linux-gnu/libc.so.6
 g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? ()
Title: gnome-volume-control crashed with SIGABRT in raise()
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 #842453, 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.