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 767588 - GNOME Terminal crashes when dragging tabs onto its own window
GNOME Terminal crashes when dragging tabs onto its own window
Status: RESOLVED OBSOLETE
Product: gtk+
Classification: Platform
Component: Widget: GtkNotebook
3.20.x
Other Linux
: Normal critical
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2016-06-13 09:04 UTC by Jeff Bai
Modified: 2018-05-02 17:13 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Jeff Bai 2016-06-13 09:04:44 UTC 
GNOME Terminal 3.20.2 will crash when:

1. Using tabs to open "new windows" (as per the Preference says);
2. Create some tabs;
3. Using the mouse, drag the actual "tabs" onto the window area (a.k.a. the actual terminal);
4. Run a command;

... And the Terminal will crash (segfault on gnome-terminal-server), with a backtrace as follows.

+ Trace 236334

  • #0 gtk_widget_get_ancestor
  • #1 0x000055ab6367a196 in
  • #2 g_closure_invoke
  • #3 0x00007ffbec169e28 in
  • #4 g_signal_emit_valist
  • #5 g_signal_emit
  • #6 0x00007ffbec15c2c4 in
  • #7 0x00007ffbec15bb59 in
  • #8 g_object_thaw_notify
  • #9 0x00007ffbecbc5bed in
  • #10 0x00007ffbecbc6961 in
  • #11 0x00007ffbecbc6a48 in
  • #12 0x00007ffbecbc6aae in
  • #13 0x00007ffbec082923 in
  • #14 g_main_context_dispatch
  • #15 0x00007ffbec082260 in
  • #16 g_main_context_iteration
  • #17 g_application_run
  • #18 0x000055ab6366a1ed in
  • #19 __libc_start_main
  • #20 0x000055ab6366a329 in 

Sorry, but I don't have myself a debug binary handy at the moment. The backtrace will be updated.

P.S. two of my friends was able to reproduce the same issue but without the step "4. Run a command;", I have told them to come over to confirm it - and of course, explain it a bit better.
Comment 1 Junde Yhi 2016-06-14 10:07:01 UTC 
I am a friend of Jeff Bai above. This problem was first discovered by his another friend Icenowy Zheng (also mine), yet only Jeff needs to run a command to trigger the crash of gnome-terminal.

We have another way to reproduce it, first enter "Edit > Preferences" and set "New window opens at" to "Tab" (ignore this step if it's already so), then use "File > Open Terminal" to create another terminal in a new tab. Then, drag one of the tabs to the text field, and gnome-terminal will crash at once.
Comment 2 Christian Persch 2016-06-15 09:35:14 UTC 
This used to work just fine, likely a gtk regression from the DND or notebook changes in gtk 3.20.

-> gtk+
Comment 3 Emmanuele Bassi (:ebassi) 2016-06-15 09:40:39 UTC 
Thanks for taking the time to report this.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed in the code repository.

*** This bug has been marked as a duplicate of bug 766442 ***
Comment 4 Jeff Bai 2016-07-07 11:43:15 UTC 
That commit did not solve the issue for me though. With GTK+ 3.20.7, the problem still persists.

I don't think a rebuild would be necessary, would it?
Comment 5 Jeff Bai 2016-07-07 11:47:08 UTC 
GTK+ 3.20.6, sorry.
Comment 6 Vlad Orlov 2016-10-07 11:56:07 UTC 
Well, I see this happening in mate-terminal (unlike gnome-terminal, we didn't disable tab detaching). It started only with 3.21 though. So currently I can reproduce it in Debian Testing with 3.22.1 but can't in Ubuntu 16.10 with 3.20.9.
Comment 7 robert.samal 2017-04-26 23:42:43 UTC 
Have the same issue with gnome-terminal 3.20.2 in Ubuntu 16.10.
Comment 8 Mike 2018-01-26 14:06:38 UTC 
Does anyone know the status of this bug? I'm using GNOME Shell 3.26.2 and can not move tabs to different windows.
Comment 9 GNOME Infrastructure Team 2018-05-02 17:13:19 UTC 
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gtk/issues/634.