those reports are often useful, the retracing gives debug backtraces most of the time which is a good indication of where it crashed, and the number of duplicates tell if several users are running into the issue. In this case the is no duplicate, the retracing didn't work correctly and you don't get the issue every time, the bug still gives some indication but might not be easy to track, especially if there is nobody running into it now to try changes
-- yelp crashed with SIGSEGV in g_signal_emit_valist() https://bugs.launchpad.net/bugs/192941 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
