audacious2 crashed with SIGSEGV when quitting

Bug #688599 reported by Eliah Kagan
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
audacious (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: audacious

Audacious2 usually quits with no problems, but occasionally it hangs on exit. Sending SIGTERM quits it (after a delay of a minute or more), producing this crash. The delay between sending SIGTERM and the audacious window closing might just be the time it takes for Apport to collect information. I am unsure if this is a new bug -- it might be a duplicate of Bug 640732 or Bug 650531 (or others). The bug report summary generated by Apport was just "audacious2 crashed with SIGSEGV", which is different from the summaries for those bugs which appeared to be automatically generated as well. So I decided to play it safe and submit a new bug report.

I'm running audacious 2.4.0-0ubuntu3 on Maverick amd64. My Audacious music library is (mostly) on an external USB drive that occasionally becomes unreadable and has to be powered off and back on again. I suspect there may be a hardware (or driver) problem with that drive and/or USB on this machine. Perhaps that is a factor in producing this error. In case it's relevant, the drive is formatted NTFS (and mounted readwrite with NTFS-3G). In any case, even if the crash is motivated by problems elsewhere in the system, it still probably reflects some bug in Audacious itself. And I am not sure the crash has anything to do with any defects external to Audacious.

In case this crash is triggered by an I/O error, here's the output of "uname -a":
Linux Apok 2.6.35-23-generic #41-Ubuntu SMP Wed Nov 24 11:55:36 UTC 2010 x86_64 GNU/Linux

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: audacious 2.4.0-0ubuntu3
ProcVersionSignature: Ubuntu 2.6.35-23.41-generic 2.6.35.7
Uname: Linux 2.6.35-23-generic x86_64
Architecture: amd64
CrashCounter: 1
Date: Fri Dec 10 10:03:49 2010
Disassembly: => 0x7f0a67a4c286: Cannot access memory at address 0x7f0a67a4c286
ExecutablePath: /usr/bin/audacious2
InstallationMedia: Xubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100406)
ProcCmdline: audacious
ProcEnviron:
 LANGUAGE=en_US.utf8
 LANG=en_US.utf8
 LC_MESSAGES=en_US.utf8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f0a67a4c286: Cannot access memory at address 0x7f0a67a4c286
 PC (0x7f0a67a4c286) not located in a known VMA region (needed executable region)!
 Stack memory exhausted (SP below stack segment)
SegvReason: executing unknown VMA
Signal: 11
SourcePackage: audacious
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: audacious2 crashed with SIGSEGV
UserGroups: adm admin cdrom lpadmin plugdev sambashare

Revision history for this message
Eliah Kagan (degeneracypressure) wrote :
visibility: private → public
Tarun K. Mall (c2tarun)
description: updated
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in audacious (Ubuntu):
status: New → Invalid
Revision history for this message
Apport retracing service (apport) wrote : Crash report cannot be processed

Thank you for your report!

However, processing it in order to get sufficient information for the
developers failed (it does not generate an useful symbolic stack trace). This
might be caused by some outdated packages which were installed on your system
at the time of the report:

libudev0: installed version 162-2.1, latest version: 162-2.2
libpango1.0-common: installed version 1.28.1-1ubuntu3, latest version: 1.28.2-0ubuntu1
libpango1.0-0: installed version 1.28.1-1ubuntu3, latest version: 1.28.2-0ubuntu1
libglib2.0-0: installed version 2.26.0-0ubuntu1, latest version: 2.26.1-0ubuntu1
libc-bin: installed version 2.12.1-0ubuntu9, latest version: 2.12.1-0ubuntu10
udev: installed version 162-2.1, latest version: 162-2.2
libc6: installed version 2.12.1-0ubuntu9, latest version: 2.12.1-0ubuntu10

Please upgrade your system to the latest package versions. If you still
encounter the crash, please file a new report.

Thank you for your understanding, and sorry for the inconvenience!

tags: removed: need-amd64-retrace
Revision history for this message
Eliah Kagan (degeneracypressure) wrote :

These latest package versions are available through the maverick-proposed repository. I've added that to my sources.list file and I'm upgrading to them. If I can reproduce this bug again, I'll file a new bug report as the friendly bot instructed.

@TARUN KUMAR MALL: I'm curious, what did you change in the bug description? A diff doesn't reveal anything.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.