https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4754
--- Comment #8 from Jeff Morriss <jeff.morriss.ws@xxxxxxxxx> 2010-05-17 12:02:37 PDT ---
So is Wireshark *crashing* (i.e., it is running and then disappears) or
*hanging* (i.e., it stops responding and must be killed)? It sounds like the
latter (but the Synopsis says the former).
The backtrace indicates that whatever it was doing when you hit Ctrl-C was down
in the portaudio stuff. It may be a bug in that library or your audio, but it
seems reasonably unlikely that it's a problem in Wireshark.
Did you try any of the hints from that Ubuntu bug to at least clear the
bluetooth errors?
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.