audacious crashed with SIGSEGV in bmp_config_save

[solkanar]

Binary package hint: audacious

 lsb_release -rd
Description: Ubuntu hardy (development branch)
Release: 8.04

apt-cache policy audacious
audacious:
  Installé : 1.5.0-2
  Candidat : 1.5.0-2
 Table de version :
 *** 1.5.0-2 0
        500 http://be.archive.ubuntu.com hardy/universe Packages
        100 /var/lib/dpkg/status

I use nfs mounted files for my music. Audacious freezed while playing one of these files. I had to xkill it. It became a zombie. I tried to launch audacious again. That last action triggered a bug report window.

ProblemType: Crash
Architecture: i386
Date: Sat Apr 12 14:17:25 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/bin/audacious
NonfreeKernelModules: nvidia
Package: audacious 1.5.0-2
PackageArchitecture: i386
ProcCmdline: audacious
ProcEnviron:
 SHELL=/bin/bash
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=fr_FR.UTF-8
Signal: 11
SourcePackage: audacious
Stacktrace: #0 0x0805cdb0 in ?? ()
StacktraceTop: ?? ()
ThreadStacktrace:

Title: audacious crashed with SIGSEGV
Uname: Linux 2.6.24-15-generic i686
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin plugdev scanner video
SegvAnalysis:
 Segfault happened at: 0x805cdb0 <gtk_button_box_get_type@plt+24704>: cmpl $0xffffffff,0x98(%eax)
 PC (0x0805cdb0) ok
 source "$0xffffffff" ok
 destination "0x98(%eax)" (0x00000098) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA

[Apport retracing service (apport)]

StacktraceTop:bmp_config_save () at main.c:884

[Bryce Harrington (bryce)]

Hmm, I can't find bmp_config_save() mentioned in the audacious codebase, and the stacktrace doesn't mention any other routines so there isn't enough info to troubleshoot this one.

Can you please see if you can reproduce this bug on Jaunty, and if so attach another backtrace?

[solkanar (thomasroux)]

I don't have Jaunty on any box right now, I'll try to find time to install it and make a few tests. Thank you for working on the bug I reported.

[Benjamin Drung (bdrung)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test audacious 2.3 in the current Ubuntu development version (10.04). Thanks again!