Sound Settings crashes when USB audio mixer selected as input

[NoahY]

This bug is a regression, I think; I was having this same problem before upgrading to 12.10, then installed a patched version of some file (can't remember which, and can't find the old bug report, sadly). Now with the upgrade, when opening Sound Settings and selecting my Alesis Multimix USB mixer, the dialog crashes with the following in syslog:

gnome-control-c[4009]: segfault at 7fffa3efcd48 ip 00007f56af59e9f2 sp 00007fffa3efcc10 error 6 in libc-2.15.so[7f56af556000+1b5000]

If I try setting the mixer as default use pacmd, Sound Settings crashes on opening.

ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: gnome-control-center 1:3.4.2-0ubuntu19
ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5
Uname: Linux 3.5.0-17-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.6.1-0ubuntu3
Architecture: amd64
Date: Wed Oct 17 16:27:58 2012
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
SourcePackage: gnome-control-center
UpgradeStatus: Upgraded to quantal on 2012-09-24 (22 days ago)
usr_lib_gnome-control-center:
 deja-dup 24.0-0ubuntu1
 indicator-datetime 12.10.2-0ubuntu3

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Def Sum (fashionised)]

Same here: "Sound Settings..." crashes immediately after clicking on it. Ubuntu 12.10 clean install, amd64, USB Audio device attached.

[Def Sum (fashionised)]

"Sound Settings..." applet working fine after disconnecting USB audio device and performing "sudo /sbin/alsa force-reload".

[The Bright Side (me-knowingme)]

Affects me too. Ubuntu 12.10, 64 bit, Gnome Shell 3.6. It happened right after installation in Unity, then started working when I installed and switched to Gnome Shell. Today, I found the Sound Settings are broken again.

Same behaviour as for Def Sum. Crashes immediately after clicking on it. Works when I unplug my USB card, but shows no card installed (only a dummy device). I tried fore-reloading alsa and plugging the USB card back in, but then it crashes again.

Any help would be highly appreciated. I really really want to configure my sound settings.

[The Bright Side (me-knowingme)]

Hey guys,

while you continue experiencing this bug, here's a workaround:
http://freedesktop.org/software/pulseaudio/pavucontrol/

This program is readily available in the Ubuntu repos and replaces Ubuntu's own Sound Settings. Look for "pavucontrol" in Synaptic or Software Centre. After installation, it's in your applications as "PulseAudio Volume Control". It does everything the Sound Settings do and works like a charm.

[Raymond (superquad-vortex2)]

does your hd webcam support spdif input ?

  device.profile.description = "Digital Stereo (IEC958)"
  device.description = "HD Webcam C910 Digital Stereo (IEC958)"
  alsa.mixer_name = "USB Mixer"
  alsa.components = "USB046d:0821"
  module-udev-detect.discovered = "1"
  device.icon_name = "camera-web-usb"
 ports:
  iec958-stereo-input: iec958-stereo-input (priority 0, available: unknown)
   properties:

[Mahendra Tallur (mahen)]

Hi ! I encounter this problem with no USB device, but with an M-Audio Delta 44 PCI soundcard (ICE 1724).

[Denis Zhdanov (altwazar)]

Affects me too.
Sound card: Emu 0204 usb

[Sebastien Bacher (seb128)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. However, your crash report is either missing or challenging to deal with as a ".crash" file. Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer.

If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart.

Now open your file manager, navigate to your /var/crash directory and open the crash report you wish to submit.
If this fails you will have to open a terminal and file your report with 'ubuntu-bug /var/crash/_my_crash_report.crash' where _my_crash_report.crash is the crash you would like to report. If you get an error that you aren't allowed to access this report you will have to file it with 'sudo ubuntu-bug /var/crash/_my_crash_report.crash'.

I'm closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently. Thanks in advance for your cooperation and understanding.

[DerekKeats (derek-dkeats)]

Has this bug been relogged? I am having the same issue, just wondering how to find it.....

[osos (ehalsti)]

Hello! I'm having same issue with an usb-device PCM2904 Audio Codec
Here's the bit from DMESG

[ 4614.831527] usb 4-1.3: new full-speed USB device number 8 using ohci_hcd
[ 4614.958235] usb 4-1.3: New USB device found, idVendor=1686, idProduct=00f1
[ 4614.958248] usb 4-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 4614.958256] usb 4-1.3: Product: G2Nu/G2.1Nu Ver.1.00 [947FDA54]
[ 4614.958262] usb 4-1.3: Manufacturer: ZOOM CORPORATION
[ 4617.060496] gnome-control-c[4979]: segfault at 7fffe976fd98 ip 00007f158f12e9f2 sp 00007fffe976fc60 error 6 in libc-2.15.so[7f158f0e6000+1b5000]

I did not have this problem on 12.04

[Gramler (maxf)]

Here too:
kernel: [ 2316.149610] gnome-control-c[5374]: segfault at 7fff6b37ff88 ip 00007fb9366979f2 sp 00007fff6b37fe50 error 6 in libc-2.15.so[7fb93664f000+1b5000]

When selecting:

Bus 006 Device 003: ID 08bb:2902 Texas Instruments Japan PCM2902 Audio Codec
(Behringer X1622USB )

It should be noted that it is not all USB devices.
This one:
Bus 003 Device 002: ID 047f:c010 Plantronics, Inc.
(Plantronics GameCom 780)
is fine.

Also - I can confirm that "pavucontrol" does function correctly and I am using it at the moment in stead of the standard control
(Tx for the tip)

[Gramler (maxf)]

Note that _no_ crash report is written on the exit of the USB audio mixer. See further details in the thread. Note that I double checked crash report settings. Crash reports are being generated on my system

[Gramler (maxf)]

One more thing: I have tried this with both the 3.5 (realtime and normal) as well as 3.6 Kernels. Same behaviour.
Not sure how I can generate more usefull debug info. Please advise.

[risingfish (risingfish)]

Kind of surprised to this still outstanding after almost 8 years. This is still happening on kernel 5.3 in Ubuntu 19.10.

[risingfish (risingfish)]

Is there any debugging I provide to help get this fixed?