I can confirm that this still happens with audacious 2.4.4-1 in Natty. Also, this is a crash, and not a hang--it only appears to be a hang due to the very large number of threads that audacious2 has causing apport to take a very long time to write a .crash file for it (and thus keeping the process a zombie with an open but unresponsive interface).
This is definitely not bug 640732 (as suggested in my original description), since that bug has been found to be due to a bug in gcc-4.4, and this is on Natty, which is gcc-4.5 based. This is also not bug 650531 (as similarly suggested), as that bug's trace is highly inconsistent with the manual traces I obtained for this bug (this bug is a locking problem, and that bug isn't). I've reported this in Natty as bug 800078. If Apport retracing service can make anything of that bug's stack trace, I'll mark this as a duplicate of that bug and edit its description to make it more informative. Otherwise, I'll mark it as a duplicate of this bug and edit this bug's description to reflect the above information. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/691378 Title: audacious2 crashed with SIGSEGV when quitting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/audacious/+bug/691378/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
