Version-Release number of selected component: nautilus-3.18.3-1.fc23 Additional info: reporter: libreport-2.6.3 backtrace_rating: 4 cmdline: /usr/bin/nautilus --gapplication-service crash_function: wl_proxy_marshal_array_constructor executable: /usr/bin/nautilus kernel: 4.2.7-300.fc23.x86_64 runlevel: N 5 type: CCpp Truncated backtrace: Thread no. 1 (6 frames) #2 wl_proxy_marshal_array_constructor at src/wayland-client.c:602 #3 wl_proxy_marshal at src/wayland-client.c:648 #4 _gdk_wayland_window_drag_begin at /usr/include/wayland-client-protocol.h:999 #6 gtk_drag_begin_internal at gtkdnd.c:2467 #7 gtk_drag_begin_with_coordinates at gtkdnd.c:2637 #8 on_motion_notify_event at gtkplacessidebar.c:1521
Created attachment 1107206 [details] File: backtrace
Created attachment 1107207 [details] File: core_backtrace
Created attachment 1107208 [details] File: dso_list
Created attachment 1107209 [details] File: limits
Created attachment 1107210 [details] File: maps
Created attachment 1107211 [details] File: namespaces
Created attachment 1107212 [details] File: open_fds
Created attachment 1107213 [details] File: proc_pid_status
Another user experienced a similar problem: This issue seems to be reproduced following these steps: 0. use a gnome/wayland session (I don't know whether that is required) 1. open nautilus 2. open an archive with file-roller 3. drag and drop a folder from file-roller into nautilus What happens: Nothing. What should happen: copy files When closing nautilus or file-roller very quickly after 3., nautilus crashes, which lead to this bug report. reporter: libreport-2.6.3 backtrace_rating: 4 cmdline: /usr/bin/nautilus --gapplication-service crash_function: wl_proxy_marshal_array_constructor executable: /usr/bin/nautilus kernel: 4.3.4-300.fc23.x86_64 package: nautilus-3.18.4-1.fc23 reason: nautilus killed by SIGABRT runlevel: N 5 type: CCpp
*** This bug has been marked as a duplicate of bug 1288287 ***