mumble crashed with SIGSEGV in vfprintf()

Bug #859695 reported by Steve Magoun
18
This bug affects 2 people
Affects Status Importance Assigned to Milestone
mumble (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

Launched Mumble from the command line. It immediately segfaulted. Launching it again resulted in Mumble functioning:

steve@steve-laptop:~$ mumble
Segmentation fault (core dumped)
steve@steve-laptop:~$
steve@steve-laptop:~$
steve@steve-laptop:~$ mumble
G15LCDEngineUnix: Unable to connect to G15Daemon.
CELT bitstream 8000000b from libcelt0.so.0.0.0
Locale is en_US
Database SQLite: "3.7.7"
[...]

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: mumble 1.2.3-2ubuntu2
ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4
Uname: Linux 3.0.0-11-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 1.23-0ubuntu1
Architecture: amd64
Date: Mon Sep 26 10:31:09 2011
ExecutablePath: /usr/bin/mumble
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Beta amd64 (20100901.1)
ProcCmdline: mumble
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=en_US.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7f22491791a4 <vfprintf+7348>: repnz scas %es:(%rdi),%al
 PC (0x7f22491791a4) ok
 source "%es:(%rdi)" (0x300030005f0030) not located in a known VMA region (needed readable region)!
 destination "%al" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: mumble
StacktraceTop:
 vfprintf () from /lib/x86_64-linux-gnu/libc.so.6
 __vsprintf_chk () from /lib/x86_64-linux-gnu/libc.so.6
 __sprintf_chk () from /lib/x86_64-linux-gnu/libc.so.6
 ?? () from /usr/lib/x86_64-linux-gnu/libasound.so.2
 snd_device_name_hint () from /usr/lib/x86_64-linux-gnu/libasound.so.2
Title: mumble crashed with SIGSEGV in vfprintf()
UpgradeStatus: Upgraded to oneiric on 2011-09-02 (23 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Steve Magoun (smagoun) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 _IO_vfprintf_internal (s=<optimized out>, format=<optimized out>, ap=<optimized out>) at vfprintf.c:1620
 ___vsprintf_chk (s=0x7f2234061460 "pcm.", flags=1, slen=128, format=0x7f224bf28130 "%s.%s", args=0x7fff5e0d70e8) at vsprintf_chk.c:86
 ___sprintf_chk (s=<optimized out>, flags=<optimized out>, slen=<optimized out>, format=<optimized out>) at sprintf_chk.c:33
 sprintf (__fmt=0x7f224bf28130 "%s.%s", __s=0x7f2234061460 "pcm.") at /usr/include/x86_64-linux-gnu/bits/stdio2.h:34
 try_config (list=0x7fff5e0d7280, base=0x5e71d3 "pcm", name=0x300030005f0030 <Address 0x300030005f0030 out of bounds>) at namehint.c:229

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 mumble (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in mumble (Ubuntu):
status: New → Confirmed
tags: added: precise
Logan Rosen (logan)
information type: Private → Public
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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