> that's not because the first function matches that the crash is the same
I got that the first time. Then again, if Apport brings average users here, they are not aware of the issue at hand, they usually only have a crash and a program to report it that pops up a window with a pre- compiled field. Usually, users tend to trust its ability to identify what caused the crash. If they don't, we may as well doubt every single instance, and report each crash as a separate bug in the event it might be a new issue, regardless of duplicates. > open a new bug and wait for retracing... I'll make sure I do so, as soon as this happens again. These days Ubuntu doesn't fail to crash every other day... -- nautilus crashed with SIGSEGV in g_cclosure_marshal_VOID__VOID() https://bugs.launchpad.net/bugs/422393 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
