This indeed looks like my bug, I got this stack trace: StacktraceTop: g_type_check_instance_is_fundamentally_a () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_object_ref () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_list_copy_deep () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () ?? ()
I think the bug ID you probably want is 473ad704-5182-11f0-b915-fa163e171f02 I'm not attaching my full journal, that's huge and LBR if attaching the crash dump publicly is a privacy risk so is that log. I'm looking at it and I can see sensitive things in there already. But! I can copy just the last bit of the journal as I repro the crash. I can virtually guarantee it adds nothing over the call stack in the crash dump though: Jun 25 00:39:36 andak tracker-miner-fs-3[601770]: (tracker-extract-3:601770): GLib-GIO-WARNING **: 00:39:36.572: Error creating IO channel for /proc/self/mountinfo: Invalid argument (g-io-error-quark, 13) Jun 25 00:39:43 andak nautilus[598509]: g_object_ref: assertion 'G_IS_OBJECT (object)' failed Jun 25 00:39:43 andak kernel: nautilus[598509]: segfault at 21 ip 0000734fe23bd7d8 sp 00007ffe81e112c0 error 4 in libglib-2.0.so.0.8000.0[597d8,734fe2382000+a0000] likely on CPU 3 (core 1, socket 0) Jun 25 00:39:43 andak kernel: Code: 00 00 48 8b 3b 4c 89 ee 41 ff d4 4c 8b 7b 08 49 89 06 4c 89 f3 49 c7 46 10 00 00 00 00 4d 85 ff 75 1d eb 45 66 0f 1f 44 00 00 <49> 8b 3f 4c 89 ee 41 ff d4 48 89 03 4d 8b 7f 08 4d 85 ff 74 2a bf Jun 25 00:39:43 andak nautilus[598509]: g_object_ref: assertion 'G_IS_OBJECT (object)' failed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/2111657 Title: nautilus crashed with SIGSEGV in g_list_copy_deep() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2111657/+subscriptions -- desktop-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
