After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 764960 - Pulling tab out of tab bar crashes gnome-terminal on Wayland
Pulling tab out of tab bar crashes gnome-terminal on Wayland
Status: RESOLVED DUPLICATE of bug 769161
Product: gnome-terminal
Classification: Core
Component: general
3.20.x
Other Linux
: Normal major
: ---
Assigned To: GNOME Terminal Maintainers
GNOME Terminal Maintainers
Depends on:
Blocks:
 
 
Reported: 2016-04-12 17:52 UTC by Tyler Brock
Modified: 2016-08-01 18:28 UTC
See Also:
GNOME target: ---
GNOME version: 3.19/3.20


Description Tyler Brock 2016-04-12 17:52:24 UTC 
I'm running 3.20 with Wayland.

Pulling a terminal tab out of the tab bar crashes gnome terminal.

I'm not sure how to get a log for gnome-terminal as launching it from a gnome-terminal (not via the launcher) produces no debugging/log output.
Comment 1 Debarshi Ray 2016-04-12 18:09:21 UTC 
(In reply to Tyler Brock from comment #0)
> I'm running 3.20 with Wayland.
> 
> Pulling a terminal tab out of the tab bar crashes gnome terminal.

On 3.18.x, I lose my entire Wayland session if I do that. :)

> I'm not sure how to get a log for gnome-terminal as launching it from a
> gnome-terminal (not via the launcher) produces no debugging/log output.

You need two terminals.

On the first one do this:
$ gdb /path/to/gnome-terminal-server
...
(gdb) run --app-id foo.bar
...

On the second one do this:
$ gnome-terminal --app-id foo.bar
$
Comment 2 Tyler Brock 2016-04-12 18:29:18 UTC 
Interesting, so, now when I run the terminal like you suggested it doesn't crash but it also doesn't pull the tab out. The tab that I drag just fades away and then remains in the original tab bar.
Comment 3 Christian Persch 2016-04-15 16:14:28 UTC 
Need a backtrace.
Comment 4 Christian Persch 2016-04-24 16:32:21 UTC 
Please re-open if you get a trace.
Comment 5 Lionel Landwerlin 2016-07-27 22:05:30 UTC 
Just experienced this issues. Here is the backtrace : 

Thread 1 "gnome-terminal-" received signal SIGABRT, Aborted.
0x00007fe906d031c8 in __GI_raise (sig=sig@entry=6)
    at ../sysdeps/unix/sysv/linux/raise.c:54
54	../sysdeps/unix/sysv/linux/raise.c: No such file or directory.
(gdb) bt

+ Trace 236492

  • #0 __GI_raise
    at ../sysdeps/unix/sysv/linux/raise.c line 54
  • #1 __GI_abort
    at abort.c line 89
  • #2 g_assertion_message
  • #3 g_assertion_message_expr
    at /build/glib2.0-wnDt2X/glib2.0-2.48.1/./glib/gtestutils.c line 2452
  • #4 gtk_widget_get_frame_clock
    at /build/gtk+3.0-MFQuqz/gtk+3.0-3.20.6/./gtk/gtkwidget.c line 5804
  • #5 gtk_widget_unrealize
    at /build/gtk+3.0-MFQuqz/gtk+3.0-3.20.6/./gtk/gtkwidget.c line 5511
  • #6 gtk_widget_unparent
    at /build/gtk+3.0-MFQuqz/gtk+3.0-3.20.6/./gtk/gtkwidget.c line 4621
  • #7 gtk_notebook_remove_tab_label
    at /build/gtk+3.0-MFQuqz/gtk+3.0-3.20.6/./gtk/gtknotebook.c line 4987
  • #8 gtk_notebook_remove
    at /build/gtk+3.0-MFQuqz/gtk+3.0-3.20.6/./gtk/gtknotebook.c line 5058
  • #9 gtk_notebook_remove
    at /build/gtk+3.0-MFQuqz/gtk+3.0-3.20.6/./gtk/gtknotebook.c line 4222
  • #10 g_cclosure_marshal_VOID__OBJECTv
    at /build/glib2.0-wnDt2X/glib2.0-2.48.1/./gobject/gmarshal.c line 2102
  • #11 _g_closure_invoke_va
    at /build/glib2.0-wnDt2X/glib2.0-2.48.1/./gobject/gclosure.c line 867
  • #12 g_signal_emit_valist
    at /build/glib2.0-wnDt2X/glib2.0-2.48.1/./gobject/gsignal.c line 3294
  • #13 g_signal_emit
    at /build/glib2.0-wnDt2X/glib2.0-2.48.1/./gobject/gsignal.c line 3441
  • #14 gtk_container_remove
    at /build/gtk+3.0-MFQuqz/gtk+3.0-3.20.6/./gtk/gtkcontainer.c line 1905
  • #15 0x0000000000429720 in
  • #16 0x000000000041e4b6 in
  • #21 <emit signal 0x7fe908a8dd38 "drag-data-received" on instance 0x1223e60 [TerminalScreen]>
    at /build/glib2.0-wnDt2X/glib2.0-2.48.1/./gobject/gsignal.c line 3481
  • #22 gtk_drag_selection_received
    at /build/gtk+3.0-MFQuqz/gtk+3.0-3.20.6/./gtk/gtkdnd.c line 1636
  • #26 <emit signal 0x7fe908ae3ce4 "selection-received" on instance 0x12a4fd0 [GtkWindow]>
    at /build/glib2.0-wnDt2X/glib2.0-2.48.1/./gobject/gsignal.c line 3481
  • #27 gtk_selection_retrieval_report
    at /build/gtk+3.0-MFQuqz/gtk+3.0-3.20.6/./gtk/gtkselection.c line 3031
  • #28 gtk_selection_convert
    at /build/gtk+3.0-MFQuqz/gtk+3.0-3.20.6/./gtk/gtkselection.c line 1143
  • #29 gtk_drag_get_data
    at /build/gtk+3.0-MFQuqz/gtk+3.0-3.20.6/./gtk/gtkdnd.c line 908
  • #30 gtk_drag_dest_drop
    at /build/gtk+3.0-MFQuqz/gtk+3.0-3.20.6/./gtk/gtkdnd.c line 2151
  • #31 _gtk_drag_dest_handle_event
    at /build/gtk+3.0-MFQuqz/gtk+3.0-3.20.6/./gtk/gtkdnd.c line 1717
  • #32 _gtk_drag_dest_handle_event
    at /build/gtk+3.0-MFQuqz/gtk+3.0-3.20.6/./gtk/gtkdnd.c line 1474
  • #33 gtk_main_do_event
    at /build/gtk+3.0-MFQuqz/gtk+3.0-3.20.6/./gtk/gtkmain.c line 1896
  • #34 _gdk_event_emit
    at /build/gtk+3.0-MFQuqz/gtk+3.0-3.20.6/./gdk/gdkevents.c line 73
  • #35 gdk_event_source_dispatch
    at /build/gtk+3.0-MFQuqz/gtk+3.0-3.20.6/./gdk/wayland/gdkeventsource.c line 118
  • #36 g_main_context_dispatch
    at /build/glib2.0-wnDt2X/glib2.0-2.48.1/./glib/gmain.c line 3154
  • #37 g_main_context_dispatch
    at /build/glib2.0-wnDt2X/glib2.0-2.48.1/./glib/gmain.c line 3769
  • #38 g_main_context_iterate
    at /build/glib2.0-wnDt2X/glib2.0-2.48.1/./glib/gmain.c line 3840
  • #39 g_main_context_iteration
    at /build/glib2.0-wnDt2X/glib2.0-2.48.1/./glib/gmain.c line 3901
  • #40 g_application_run
    at /build/glib2.0-wnDt2X/glib2.0-2.48.1/./gio/gapplication.c line 2381
  • #41 0x0000000000412599 in
  • #42 __libc_start_main
    at ../csu/libc-start.c line 291
  • #43 0x00000000004126c9 in 






Comment 6


Christian Persch





          2016-07-28 07:41:56 UTC
        



Likely dup of bug 769161, try the patch there.






Comment 7


Christian Persch





          2016-08-01 18:28:30 UTC
        




*** This bug has been marked as a duplicate of bug 769161 ***