audacious2 crashed with SIGSEGV in std::ios_base::Init::~Init()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
audacious (Ubuntu) |
New
|
Medium
|
Unassigned |
Bug Description
Binary package hint: audacious
Ubuntu maverick (development branch)
Release: 10.10
package : Audacious
audacious:
Installé : 2.4.0-0ubuntu1
Candidat : 2.4.0-0ubuntu1
Table de version :
*** 2.4.0-0ubuntu1 0
500 http://
100 /var/lib/
i was playing a playlist m3u on a SD card, when i have clicked on the quit bouton, audacious crashed
ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: audacious 2.4.0-0ubuntu1
ProcVersionSign
Uname: Linux 2.6.35-22-generic x86_64
NonfreeKernelMo
Architecture: amd64
Date: Sat Sep 18 14:56:39 2010
Disassembly: => 0x0: Cannot access memory at address 0x0
ExecutablePath: /usr/bin/audacious2
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Beta amd64 (20100901.1)
ProcCmdline: audacious2 /media/
ProcEnviron:
LANG=fr_CH.UTF-8
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_
__run_
exit (status=0) at exit.c:100
__libc_start_main (main=<value optimized out>, argc=<value optimized out>, ubp_av=<value optimized out>, init=<value optimized out>, fini=<value optimized out>, rtld_fini=<value optimized out>, stack_end=
Title: audacious2 crashed with SIGSEGV in std::ios_
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
Changed in audacious (Ubuntu): | |
importance: | Undecided → Medium |
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.