[soundnua]: gnome-control-center crashed with SIGSEGV

[omarly666]

updates and reboot
Sound settings crashed on firstrun
second try alll seems ok

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: gnome-control-center 1:3.3.91-0ubuntu3
ProcVersionSignature: Ubuntu 3.2.0-18.28-generic 3.2.9
Uname: Linux 3.2.0-18-generic i686
ApportVersion: 1.94.1-0ubuntu2
Architecture: i386
CheckboxSubmission: 8617bffd198177508bf030f94c880aca
CheckboxSystem: bb422ca46d02494cdbc459927a98bc2f
Date: Sat Mar 10 11:28:56 2012
ExecutablePath: /usr/bin/gnome-control-center
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
ProcCmdline: gnome-control-center sound-nua
SegvAnalysis:
 Segfault happened at: 0x1e0cfd6c: fstl 0x88(%eax)
 PC (0x1e0cfd6c) ok
 source "0x88(%eax)" (0xaaaaab32) ok
 SP (0xbfae3900) ok
 Reason could not be automatically determined.
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/i386-linux-gnu/libpulse.so.0
 ?? () from /usr/lib/i386-linux-gnu/libpulsecommon-1.1.so
 ?? () from /usr/lib/i386-linux-gnu/libpulsecommon-1.1.so
Title: [soundnua]: gnome-control-center crashed with SIGSEGV
UpgradeStatus: Upgraded to precise on 2012-02-16 (23 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
usr_lib_gnome-control-center:
 activity-log-manager-control-center 0.9.3-0ubuntu1
 deja-dup 21.90-0ubuntu1
 gnome-bluetooth 3.2.2-0ubuntu3
 indicator-datetime 0.3.91-0ubuntu1

[Apport retracing service (apport)]

StacktraceTop:
 update_input_peak (dialog=0x21511150, v=0) at gvc-mixer-dialog.c:226
 update_input_meter (v=<optimized out>, dialog=0x21511150, source_index=<optimized out>, sink_input_idx=<optimized out>) at gvc-mixer-dialog.c:242
 on_monitor_read_callback (s=0x216b9980, length=4, userdata=0x21511150) at gvc-mixer-dialog.c:292
 pstream_memblock_callback (p=0x2166fd68, channel=0, offset=0, seek=PA_SEEK_RELATIVE, chunk=0xbfae3a10, userdata=0x21716320) at pulse/context.c:365
 do_read (p=0x2166fd68) at pulsecore/pstream.c:844

[Launchpad Janitor (janitor)]

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

[Conor Curran (cjcurran)]

Stacktrace seems to be irrelevant. Looks as if Pulse might have been misbehaving itself. It's difficult to tell. Has this happened since ?

[Sebastien Bacher (seb128)]

closing the bug since there was no reply to the question

[John Winterton (jwinterton)]

no recurrence, so closing is appropriate.