Unfortunately it looks like mono did not managed to get the trace out after the SIGABRT. Could you run "sudo sysctl kernel.yama.ptrace_scope=1" and try again? It should cause more stuff to be printed out this time.
Also, please upload the full output from "banshee --debug". It'll help in figuring out what went wrong before Banshee hung. If you find yourself encountering a hang, run "killall -SIGQUIT banshee" in a terminal as per http://banshee.fm/contribute/file-bugs/ and then upload ~/.config/banshee-1/log" before restarting Banshee. If it crashes otherwise, ~/.config/banshee-1/log should contain some useful information as well. Again, please upload the full contents, rather than just what's after the gdb trace. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/889407 Title: banshee crashes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/banshee/+bug/889407/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
