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

[Rovano]

Binary package hint: audacious

Only 1x.

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: audacious 2.4.0-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.35-19.28-generic 2.6.35.3
Uname: Linux 2.6.35-19-generic i686
Architecture: i386
CrashCounter: 1
Date: Sun Sep 5 13:28:13 2010
Disassembly: => 0x0: Cannot access memory at address 0x0
ExecutablePath: /usr/bin/audacious2
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Alpha i386 (20100827)
ProcCmdline: audacious2
ProcEnviron:
 LANG=cs_CZ.utf8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x0: Cannot access memory at address 0x0
 PC (0x00000000) not located in a known VMA region (needed executable region)!
SegvReason: executing 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
 _fini () 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:1390): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
 (nautilus:1389): GConf-CRITICAL **: gconf_value_free: assertion `value != NULL' failed

[Apport retracing service (apport)]

StacktraceTop:
 ?? ()
 __cxa_finalize (d=0x19ec06c) at cxa_finalize.c:56
 __do_global_dtors_aux () from /usr/lib/libbinio.so.1
 _fini () from /usr/lib/libbinio.so.1
 _dl_close_worker (map=0x8aa36e0) at dl-close.c:271

[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.