nautilus crashed with SIGSEGV in g_type_check_instance_cast() due to the deja-dup (35.1-0ubuntu2) change

[dino99]

Opened a fresh gnome-shell session, and checked for updates via synaptic: got the crash at that time. Now nautilus fails to load/open (Segmentation fault (core dumped)).

Note: if deja-dup* packages are downgraded from 35.1 to 34.4, then nautilus can be used without warning/error/crash.

Note2: i've the feeling that nautilus get that issue only with the latest deja-dup* 35.1-0ubuntu2 version(but i'm not sure, the previous 35.1-oubuntu1 had not made nautilus crashing)

Feedback: reinstalled the previous 35.1-0ubuntu1 packages, and can confirm that nautilus is not affected by that version.
So the problem is ONLY with the ...ubuntu2 ones's change described as below:

deja-dup (35.1-0ubuntu2) artful; urgency=medium

  * debian/tests/control, debian/tests/check:
    - Fix tests; upstream (me) removed the test target we were using

 -- Michael Terry <email address hidden> Fri, 28 Jul 2017 23:15:45 -0400

ProblemType: Crash-0ubuntu2
DistroRelease: Ubuntu 17.10
Package: nautilus 1:3.24.1-0ubuntu5
ProcVersionSignature: Ubuntu 4.11.0-11.16-generic 4.11.10
Uname: Linux 4.11.0-11-generic x86_64
ApportVersion: 2.20.6-0ubuntu4
Architecture: amd64
CurrentDesktop: GNOME
Date: Sat Jul 29 07:17:08 2017
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/nautilus
ProcCmdline: /usr/bin/nautilus --gapplication-service
ProcEnviron:
 XDG_RUNTIME_DIR=<set>
 SHELL=/bin/bash
 LANGUAGE=en_US
 PATH=(custom, no user)
 LANG=en_US.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7f5d3f2f918a <g_type_check_instance_cast+26>: mov (%rdi),%r9
 PC (0x7f5d3f2f918a) ok
 source "(%rdi)" (0xffffffff825cae00) not located in a known VMA region (needed readable region)!
 destination "%r9" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 g_type_check_instance_cast () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/nautilus/extensions-3.0/libdeja-dup.so
 ?? () from /usr/lib/x86_64-linux-gnu/nautilus/extensions-3.0/libdeja-dup.so
 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: nautilus crashed with SIGSEGV in g_type_check_instance_cast()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

[Apport retracing service (apport)]

StacktraceTop:
 g_type_check_instance_cast () from /tmp/apport_sandbox_mJ7f5_/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 update_include_excludes () from /tmp/apport_sandbox_mJ7f5_/usr/lib/x86_64-linux-gnu/nautilus/extensions-3.0/libdeja-dup.so
 update_include_excludes_idle_cb () from /tmp/apport_sandbox_mJ7f5_/usr/lib/x86_64-linux-gnu/nautilus/extensions-3.0/libdeja-dup.so
 g_main_context_dispatch () from /tmp/apport_sandbox_mJ7f5_/lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_main_context_iterate.isra () from /tmp/apport_sandbox_mJ7f5_/lib/x86_64-linux-gnu/libglib-2.0.so.0

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Michael Terry (mterry)]

OK, I looked into it quickly in gdb, it seems like something not obvious or memory-corruption related. Since I felt it was going to not be a one-minute fix, I just disabled the nautilus extension for now. It's not very important to the deja-dup workflow.

But I'll keep digging on why nautilus is crashing and have a better fix.

[dino99 (9d9)]

...ubuntu3 indeed works with nautilus; thanks for the quick temp fix

[Launchpad Janitor (janitor)]

This bug was fixed in the package deja-dup - 35.1-0ubuntu3

---------------
deja-dup (35.1-0ubuntu3) artful; urgency=medium

  * debian/control:
    - Disable building the nautilus extension, it has a regression that
      crashes nautilus. This needs to be looked at in more depth, but
      this is a quick fix to get nautilus running again. (LP: #1707346)

 -- Michael Terry <email address hidden> Sat, 29 Jul 2017 11:40:08 -0400

[Michael Terry (mterry)]

OK, pushed 35.2-0ubuntu1, which re-enables the nautilus extension, after fixing the root cause upstream. Thanks all!