nautilus crashes when trying to show files extracted to desktop

[Julian Raschke]

I've opened a ZIP file in Ubuntu's default archive utility, extracted it to the desktop, then chose "Show extracted files". Instead of a ~/Desktop Nautilus window, I got the crash reporter.

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: nautilus 1:3.24.1-0ubuntu5
ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
Uname: Linux 4.11.0-10-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.6-0ubuntu4
Architecture: amd64
CurrentDesktop: GNOME
Date: Sat Jul 29 10:57:25 2017
ExecutablePath: /usr/bin/nautilus
InstallationDate: Installed on 2017-07-21 (7 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170719)
ProcCmdline: /usr/bin/nautilus --gapplication-service
SegvAnalysis:
 Segfault happened at: 0x7fd65baa318a <g_type_check_instance_cast+26>: mov (%rdi),%r9
 PC (0x7fd65baa318a) ok
 source "(%rdi)" (0x48eb9940) 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 docker 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 #1707346, 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.