audacious2 crashed with SIGSEGV in std::ios_base::Init::~Init()

[davidlorente]

Binary package hint: audacious

i dont know

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: audacious 2.4.0-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic x86_64
Architecture: amd64
Date: Fri Sep 24 18:35:27 2010
Disassembly: => 0x0: No se puede acceder a la memoria en la dirección 0x0
ExecutablePath: /usr/bin/audacious2
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Beta amd64 (20100901.1)
ProcCmdline: audacious2
ProcEnviron:
 LANG=es_ES.utf8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x0: No se puede acceder a la memoria en la dirección 0x0
 PC (0x00000000) not located in a known VMA region (needed executable region)!
 source "0x0" (0x00000000) not located in a known VMA region (needed readable region)!
SegvReason:
 executing NULL VMA
 reading NULL VMA
Signal: 11
SourcePackage: audacious
StacktraceTop:
 ?? ()
 std::ios_base::Init::~Init() () from /usr/lib/libstdc++.so.6
 __cxa_finalize () from /lib/libc.so.6
 ?? () from /usr/lib/libbinio.so.1
 ?? ()
Title: audacious2 crashed with SIGSEGV in std::ios_base::Init::~Init()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XsessionErrors:
 (polkit-gnome-authentication-agent-1:1636): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
 (process:2506): Gtk-WARNING **: Locale not supported by C library.
 (process:3155): Gtk-WARNING **: Locale not supported by C library.

[Apport retracing service (apport)]

StacktraceTop:
 ?? ()
 std::ios_base::Init::~Init ()
 ?? ()
 __cxa_finalize (d=0x7f53851a70d0)
 __do_global_dtors_aux () from /usr/lib/libbinio.so.1

[Benjamin Drung (bdrung)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug #640732, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.