[soundnua]: gnome-control-center crashed with SIGSEGV in gvc_mixer_control_change_input()

Bug #981963 reported by Frotty
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-control-center (Ubuntu)
Incomplete
Medium
Conor Curran

Bug Description

I was just chaning some values in the Sound Settings, double- and left/right clicking when it crashed.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: gnome-control-center 1:3.4.0-0ubuntu7
ProcVersionSignature: Ubuntu 3.2.0-22.35-generic 3.2.14
Uname: Linux 3.2.0-22-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.0.1-0ubuntu3
Architecture: amd64
CrashCounter: 1
Date: Sun Apr 15 00:59:04 2012
ExecutablePath: /usr/bin/gnome-control-center
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120410)
ProcCmdline: gnome-control-center sound-nua
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANG=en_US.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7f9c3f7596b2 <vfprintf+50>: mov %eax,-0x528(%rbp)
 PC (0x7f9c3f7596b2) ok
 source "%eax" ok
 destination "-0x528(%rbp)" (0x7ffff7483de8) not located in a known VMA region (needed writable region)!
 Stack memory exhausted (SP below stack segment)
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: gnome-control-center
StacktraceTop:
 ?? () from /usr/lib/control-center-1/panels/libsoundnua.so
 ?? () from /usr/lib/control-center-1/panels/libsoundnua.so
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: [soundnua]: gnome-control-center crashed with SIGSEGV in g_signal_emit_valist()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
usr_lib_gnome-control-center:
 activity-log-manager-control-center 0.9.4-0ubuntu3
 deja-dup 22.0-0ubuntu2
 gnome-bluetooth 3.2.2-0ubuntu5
 indicator-datetime 0.3.94-0ubuntu1

Revision history for this message
Frotty (frotty) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 gvc_mixer_control_change_input (control=0x7f9c43452040, input=0x7f9c4369e080) at gvc-mixer-control.c:653
 on_input_selection_changed (selection=<optimized out>, dialog=0x7f9c431562a0) at gvc-mixer-dialog.c:1472
 _g_closure_invoke_va (closure=0x7f9c433dfb70, return_value=0x0, instance=0x7f9c4355de30, args=0x7ffff7484d38, n_params=0, param_types=<optimized out>) at /build/buildd/glib2.0-2.32.0/./gobject/gclosure.c:840
 g_signal_emit_valist (instance=0x7f9c4355de30, signal_id=<optimized out>, detail=0, var_args=<optimized out>) at /build/buildd/glib2.0-2.32.0/./gobject/gsignal.c:3207
 g_signal_emit (instance=<optimized out>, signal_id=<optimized out>, detail=<optimized out>) at /build/buildd/glib2.0-2.32.0/./gobject/gsignal.c:3352

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in gnome-control-center (Ubuntu):
importance: Undecided → Medium
summary: [soundnua]: gnome-control-center crashed with SIGSEGV in
- g_signal_emit_valist()
+ gvc_mixer_control_change_input()
tags: removed: need-amd64-retrace
Revision history for this message
Conor Curran (cjcurran) wrote :

Hi,

Is this reproducible ? We released a fix for a similar issue Wednesday last week.

Conor

visibility: private → public
Changed in gnome-control-center (Ubuntu):
status: New → In Progress
assignee: nobody → Conor Curran (cjcurran)
Revision history for this message
Conor Curran (cjcurran) wrote :

I need more info here. Was it a USB device that you were using at the time of the crash ? Can it reproduce it ?
Marking incomplete until more info is given.

Changed in gnome-control-center (Ubuntu):
status: In Progress → Incomplete
Revision history for this message
Frotty (frotty) wrote :

No, I am using a Creative SB 5.1 VX Soundcard and did set the default audio output to it and listened to the samples to check if it works.
It will try to reproduce it when I get the time.

Revision history for this message
Conor Curran (cjcurran) wrote :

Was your precise up to date when the crash occurred on the 15th ?
We did release a fix through pulseaudio on the 11th which resolved a crash that produced a stack trace very similar to that.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.