mumble crashed with SIGABRT in raise()

Bug #951945 reported by Logan Rosen
26
This bug affects 3 people
Affects Status Importance Assigned to Milestone
mumble (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

This occurred after importing a certificate for the first time. It worked the second time, so I'm not sure how reproducible this crash is.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: mumble 1.2.3-2ubuntu4
ProcVersionSignature: Ubuntu 3.2.0-18.29-generic 3.2.9
Uname: Linux 3.2.0-18-generic x86_64
ApportVersion: 1.94.1-0ubuntu2
Architecture: amd64
Date: Sat Mar 10 20:48:33 2012
ExecutablePath: /usr/bin/mumble
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120309)
ProcCmdline: mumble
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 6
SourcePackage: mumble
StacktraceTop:
 raise () from /lib/x86_64-linux-gnu/libc.so.6
 abort () from /lib/x86_64-linux-gnu/libc.so.6
 ?? () from /lib/x86_64-linux-gnu/libc.so.6
 ?? () from /lib/x86_64-linux-gnu/libc.so.6
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
Title: mumble crashed with SIGABRT in raise()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Logan Rosen (logan) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 __libc_message (do_abort=2, fmt=0x7f1052ef7250 "*** glibc detected *** %s: %s: 0x%s ***\n") at ../sysdeps/unix/sysv/linux/libc_fatal.c:201
 malloc_printerr (action=3, str=0x7f1052ef4201 "free(): invalid pointer", ptr=<optimized out>) at malloc.c:5007
 ?? ()
 ?? ()
 ?? ()

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
tags: added: apport-failed-retrace
tags: removed: need-amd64-retrace
Logan Rosen (logan)
visibility: private → public
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
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.