nautilus crashed with signal 5 in _XReply() - drag and drop crash

[Rodrigo Alconchel]

NOTE: Ubuntu won't fix this bug, but if you are interested in a work around, read the last comment!

ORIGINAL BUG REPORT:

To reproduce on a fully updated Ubuntu Desktop 16.04 system with Unity:

Step 1: Start nautilus

Step 2: Drag and drop a file to any target: to a different folder in the same nautilus window, to another folder in a different nautilus window, etc. ... The target is irrelevant.

Expected to happen: File successfully copied or moved.

Actually happened: Mouse pointer changes to a hand with a plus sign. Source file moves only slightly and then freezes, never makes it to the target. Application locks up for a few seconds, and then the application window vanishes. Crash report is then generated.

Ubuntu release: Ubuntu 16.04.3 LTS

Nautilus package version: Installed: 1:3.18.4.is.3.14.3-0ubuntu6

Additional (and maybe relevant) notes:

1) Drag and drop function seems broken generally, across applications, not just in nautilus. For instance, same behavior appears when trying to drag and drop a Thunderbird message to another Thunderbird folder, or when trying to drag and drop a cell or a range of cells within the same Libreoffice Calc spreadsheet.

2) Interestingly, application windows can be dragged and dropped across display monitors (3 monitor setup), without any problems.

3) I am using proprietary NVIDIA drivers, but please do not suggest using nouveau drivers, because they work horribly (heavy display corruption, pixelated screen, and constant mouse flickering)

4) Graphics setup: NVIDIA Quadro NVS 450 card with twin GPU and 4 heads. NVIDIA proprietary driver version 340.102 (installed from ubuntu repositories, not from proprietary NVIDIA installer; this is the correct driver version for this card according to NVIDIA documentation). 3 monitors connected in a simple horizontal layout.

5) Nautilus extension installed: nautilus-share 0.7.3-2ubuntu1

6) Attaching a nautilus debugging log from terminal command: G_DEBUG="all" NAUTILUS_DEBUG ="All" nautilus

7) Attaching X Org log file with -logverbose 6 option

8) Attaching xorg.conf configuration file

ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: apport 2.20.1-0ubuntu2.10
ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17
Uname: Linux 4.10.0-33-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
CrashReports: 640:1000:116:10641522:2017-09-14 12:49:07.088649823 +0200:2017-09-14 12:27:03.381461842 +0200:/var/crash/_usr_bin_nautilus.1000.crash
CurrentDesktop: Unity
Date: Thu Sep 14 11:02:40 2017
ExecutablePath: /usr/bin/nautilus
ExecutableTimestamp: 1481715745
PackageArchitecture: all
ProcCmdline: nautilus
ProcCwd: /var/crash
Signal: 5
SourcePackage: apport
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
 XShapeGetRectangles () from /usr/lib/x86_64-linux-gnu/libXext.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: adm cdrom dip lpadmin plugdev sambashare sudo
modified.conffile..etc.apport.crashdb.conf: [modified]
mtime.conffile..etc.apport.crashdb.conf: 2017-09-14T09:20:26.397971

[Apport retracing service (apport)]

StacktraceTop:
 XShapeGetRectangles (dpy=0x1996cb0, window=1684, kind=kind@entry=0, count=count@entry=0x7ffe3171c0d0, ordering=ordering@entry=0x7ffe3171c0d4) at ../../src/XShape.c:456
 _gdk_x11_xwindow_get_shape (xdisplay=<optimized out>, window=<optimized out>, scale=scale@entry=1, shape_type=shape_type@entry=0) at /build/gtk+3.0-2Ut_nl/gtk+3.0-3.18.9/./gdk/x11/gdkwindow-x11.c:4534
 is_pointer_within_shape (y_pos=<optimized out>, x_pos=366, child=0x1ede5f0, display=<optimized out>) at /build/gtk+3.0-2Ut_nl/gtk+3.0-3.18.9/./gdk/x11/gdkdnd-x11.c:660
 get_client_window_at_coords (cache=<optimized out>, cache=<optimized out>, y_root=392, x_root=366, ignore=<optimized out>) at /build/gtk+3.0-2Ut_nl/gtk+3.0-3.18.9/./gdk/x11/gdkdnd-x11.c:765
 gdk_x11_drag_context_find_window (context=0x7f8fc8005860, drag_window=<optimized out>, screen=<optimized out>, x_root=<optimized out>, y_root=<optimized out>, protocol=0x7ffe3171c2b4) at /build/gtk+3.0-2Ut_nl/gtk+3.0-3.18.9/./gdk/x11/gdkdnd-x11.c:2038

[Rodrigo Alconchel (rodag)]

Adding X Org configuration file xorg.conf

[Rodrigo Alconchel (rodag)]

Using Compiz by the way

[Rodrigo Alconchel (rodag)]

Dear Bug Triager,

I have now realized that the Xorg team won't look into Xinerama issues as they claim that it's deprecated in favor of RandR. Please feel free to mark this bug as Won't Fix as that better reflects the reality of the situation from the standpoint of the Ubuntu developers.

FOR ANYONE ELSE WHO MAY CARE ABOUT THIS:

At some point I realized that both Xinerama and the Compiz window manager where causing this problem. Besides the bug issue reported above, the setup was causing very slow graphics performance and a few crash reports.

Sticking with Nvidia proprietary drivers, I made the switch to BaseMosaic (instead of Xinerama) and moved away from the Unity/Compiz combination and on to Gnome-Classic/Metacity (Non-composite window manager). For Gnome Classic the package to install is gnome-session-flashback, and you need to use it because Unity requires a composite manager while Gnome Classic does not.

This nearly solved all problems, but then I found resume from suspend not working properly. Resume from suspend was working in the sense of restarting the system again (I could ssh into it), but the display monitors remained black. The culprit was the Nvidia propietary driver, which I finally removed in favor of the nouveau driver. Last but not least, a bit of shifting monitors around with xrandr, and problem solved!

To sum up, use:

- Gnome Classic Desktop Environment
- Metacity Window Manager
- Install a dock launcher like cairo-dock if you are missing Unity's dock
- Nouveau driver
- NO xorg.conf file!
- Xrandr if you are not getting the correct monitor layout
- place the xrandr command in an executable shell script, and include the script in the startup apps.

[Sebastien Bacher (seb128)]

there has been no recent report of similar problem, assuming it's resolved