Same crash? Really? Then why isn't the backtrace in your crash dump file [1] pointing at xine_get_next_audio_frame() in /usr/lib/libxine.so.1?
What would be a lot more useful is (a) a separate bug report for what looks suspiciously like a separate issue, (b) knowing what you were doing with gxine at the time and (c) http://www.chiark.greenend.org.uk/~sgtatham/bugs.html [1] Bloated, insufficiently-annotated, lacking full debug info, would ideally be processed after upload to provide this info *without* the core dump... yes, I agree, /var/crash/_usr_bin_gxine.1000 is a problem :-) -- crash gxine https://launchpad.net/bugs/72613 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
