nautilus crashed with signal 5 in _XReply()

[Barry Drake]

The crash occurred while using nautilus under gksu. I had just copied sume extremely large directories from one HD to another. The crash occurred after I had opened a .deb package using the software center to install. This was not working as superuser.

ProblemType: Crash
DistroRelease: Ubuntu 16.10
Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu4
ProcVersionSignature: Ubuntu 4.4.0-30.49-generic 4.4.13
Uname: Linux 4.4.0-30-generic x86_64
ApportVersion: 2.20.2-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Tue Jul 5 14:52:33 2016
ExecutablePath: /usr/bin/nautilus
GsettingsChanges:
 b'org.gnome.nautilus.preferences' b'enable-delete' b'true'
 b'org.gnome.nautilus.window-state' b'sidebar-width' b'359'
 b'org.gnome.nautilus.window-state' b'geometry' b"'890x550+550+24'"
 b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where']"
InstallationDate: Installed on 2016-07-05 (0 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160701)
ProcCmdline: nautilus
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
 LANGUAGE=en_GB:en
 SHELL=/bin/bash
Signal: 5
SourcePackage: nautilus
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
 ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
 _XReply () from /usr/lib/x86_64-linux-gnu/libX11.so.6
 XGetWindowProperty () from /usr/lib/x86_64-linux-gnu/libX11.so.6
 ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
Title: nautilus crashed with signal 5 in _XReply()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

[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 #1427332, 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.