nautilus-desktop crashed with SIGSEGV in g_type_check_instance_cast()

[Dennis Coomans]

crashes direct after starting up Ubuntu, without having started Nautilus manually

ProblemType: Crash
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 14:44:23 2017
ExecutablePath: /usr/bin/nautilus-desktop
InstallationDate: Installed on 2017-07-03 (25 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170703)
ProcCmdline: nautilus-desktop
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=nl_NL.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f7717d5d18a <g_type_check_instance_cast+26>: mov (%rdi),%r9
 PC (0x7f7717d5d18a) ok
 source "(%rdi)" (0xffffffffce66a940) 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-desktop 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)]

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1707369, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.