Bug 968005

Created attachment 754040 [details]
File: backtrace

Created attachment 754041 [details]
File: cgroup

Created attachment 754042 [details]
File: dso_list

Created attachment 754043 [details]
File: environ

Created attachment 754044 [details]
File: limits

Created attachment 754045 [details]
File: maps

Created attachment 754046 [details]
File: open_fds

Created attachment 754047 [details]
File: proc_pid_status

Created attachment 754048 [details]
File: var_log_messages

I tried to choose my bluetooth headset

reporter:       libreport-2.1.4
backtrace_rating: 4
cmdline:        gnome-control-center sound
core_backtrace: 
crash_function: vasprintf
executable:     /usr/bin/gnome-control-center
kernel:         3.9.4-300.fc19.x86_64
package:        control-center-3.8.2-1.fc19
reason:         Process /usr/bin/gnome-control-center was killed by signal 11 (SIGSEGV)
runlevel:       N 5
uid:            500

Using an external USB mixer, Behringer Xenyx 1204USB, which provides a set of inputs and outputs over USB. When opening GNOME control center's sound config panel, and selecting the USB mixer's input device as system default, it crashes.

lsusb: Bus 003 Device 002: ID 08bb:2902 Texas Instruments PCM2902 Audio Codec

reporter:       libreport-2.1.4
backtrace_rating: 4
cmdline:        gnome-control-center sound
core_backtrace: 
crash_function: vasprintf
executable:     /usr/bin/gnome-control-center
kernel:         3.9.4-301.fc19.x86_64
package:        control-center-3.8.2-1.fc19
reason:         Process /usr/bin/gnome-control-center was killed by signal 11 (SIGSEGV)
runlevel:       unknown
uid:            1000

select "settings" from user menu.... "settings" starts normally... select "sound" from settings window ... couple seconds later the window vanishes (killed by signal 11)
Please note: this machine has a pair of Alesis M1Active 320 USB speakers, and sound does work, but can not access sound settings.

reporter:       libreport-2.1.5
backtrace_rating: 4
cmdline:        gnome-control-center --overview
crash_function: vasprintf
executable:     /usr/bin/gnome-control-center
kernel:         3.9.5-301.fc19.x86_64
package:        control-center-3.8.3-1.fc19
reason:         Process /usr/bin/gnome-control-center was killed by signal 11 (SIGSEGV)
runlevel:       N 5
uid:            1000

1. Connect bluetooth headphones.
2. Open sound settings in michrophone tab.
3. Crash.

reporter:       libreport-2.1.5
backtrace_rating: 4
cmdline:        gnome-control-center sound
core_backtrace: 
crash_function: vasprintf
executable:     /usr/bin/gnome-control-center
kernel:         3.9.6-301.fc19.x86_64
package:        control-center-3.8.3-1.fc19
reason:         Process /usr/bin/gnome-control-center was killed by signal 11 (SIGSEGV)
runlevel:       N 5
uid:            1000

Connected Behringer 1204USB mixer via USB. When tried to select that device from the GNOME mixer, it crashes.

Another user experienced a similar problem:

Open sound settings from panel volume control icon. Switch to “Input” tab and click “M-Audio Delta Audiophile 2496 Analog Stereo.”

reporter:       libreport-2.1.10
backtrace_rating: 4
cmdline:        gnome-control-center sound
crash_function: vasprintf
executable:     /usr/bin/gnome-control-center
kernel:         3.12.5-200.fc19.x86_64
package:        control-center-3.8.5-1.fc19
reason:         gnome-control-center killed by SIGSEGV
runlevel:       N 5
type:           CCpp
uid:            1000

This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 19 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.