| 2010-12-10 15:49:56 |
Tarun K. Mall |
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 |
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
|
|
