In situations like this where we think multiple different crash signatures may share a single root cause, I prefer to keep them separate for as long as possible. Because bugs can have multiple root causes and if you have only fixed one root cause then the same crash signature may keep appearing. This is particularly likely with heap corruption where any piece of code could become a new root cause. I don't think it's safe to assume we have fixed all the causes of heap corruption in nautilus this early.
The final test we use to close secondary bugs like this is to wait until a fix is released and confirm the number of crash reports on errors.ubuntu.com for it has dropped to almost zero. Although right now I can't find this crash at all: https://errors.ubuntu.com/?release=Ubuntu%2026.04&package=nautilus&period=month -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2148631 Title: nautilus crashed with SIGSEGV in gtk_accessible_value_unref() from gtk_accessible_attribute_set_free() from g_atomic_rc_box_release_full() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk4/+bug/2148631/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
