Description of problem:
Opened two files in gedit. Wanted to look at them side by side. I tried to drag a tab to a separate Window. gedit crashed. Running Wayland if that makes any difference.
Version-Release number of selected component:
cmdline: /usr/bin/gedit --gapplication-service
runlevel: N 5
Thread no. 1 (10 frames)
#2 wl_proxy_marshal_array_constructor at src/wayland-client.c:602
#3 wl_proxy_marshal at src/wayland-client.c:648
#4 wl_data_device_start_drag at /usr/include/wayland-client-protocol.h:999
#5 _gdk_wayland_window_drag_begin at gdkdnd-wayland.c:378
#6 gtk_drag_begin_internal at gtkdnd.c:2467
#7 gtk_drag_begin_with_coordinates at gtkdnd.c:2637
#8 gtk_notebook_motion_notify at gtknotebook.c:3495
#9 _gtk_marshal_BOOLEAN__BOXEDv at gtkmarshalers.c:131
#10 _g_closure_invoke_va at gclosure.c:864
#13 gtk_widget_event_internal at gtkwidget.c:7692
Created attachment 1102030 [details]
Created attachment 1102031 [details]
Created attachment 1102032 [details]
Created attachment 1102033 [details]
Created attachment 1102034 [details]
Created attachment 1102035 [details]
Created attachment 1102036 [details]
Created attachment 1102037 [details]
Created attachment 1102038 [details]
Created attachment 1102039 [details]
Created attachment 1102040 [details]
Created attachment 1102041 [details]
Reproduced easily. Works as expected on X11. Added Wayland related
*** Bug 1292876 has been marked as a duplicate of this bug. ***
Cannot reproduce using gedit-3.21.90-1.fc25 (but cannot detach the tab either)
Also, opening a new window (with gedit --new-window) and dragging a tab from the first window to the second works as expected.
(In reply to Olivier Fourdan from comment #15)
> Cannot reproduce using gedit-3.21.90-1.fc25 (but cannot detach the tab
I cannot reproduce this bug either on F25 alpha live images, not even on F24 current gedit versions (3.20.2-1).
(In reply to Christian Stadelmann from comment #17)
> I cannot reproduce this bug either on F25 alpha live images, not even on F24
> current gedit versions (3.20.2-1).
That's good news then! I suspect this might have been a gtk bug instead.
ok, I think we should close this then, if it can't be reproduced anymore.