[Touch-packages] [Bug 1438014] Re: gnome-terminal-server and mate-terminal crash when setting keyboard shortcuts

2018-05-19 Thread yzp15 
Reported to gnome's gitlab: https://gitlab.gnome.org/GNOME/gtk/issues/180
Reference: GNOME/gtk#180

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1438014

Title:
  gnome-terminal-server and mate-terminal crash when setting keyboard
  shortcuts

Status in gtk+3.0 package in Ubuntu:
  Confirmed

Bug description:
  I put my laptop to sleep for an hour or so; when I restored it, gnome-
  terminal had crashed. It did not do this the previous time I suspended
  my laptop today, so I doubt that's immediately related.

  This crash can be reproduced by setting a shortcut in preferences.

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: gnome-terminal 3.14.2-0ubuntu2
  ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2
  Uname: Linux 3.19.0-10-generic x86_64
  NonfreeKernelModules: openafs
  ApportVersion: 2.16.2-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Mar 30 00:19:43 2015
  ExecutablePath: /usr/lib/gnome-terminal/gnome-terminal-server
  InstallationDate: Installed on 2014-02-03 (419 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  ProcCmdline: /usr/lib/gnome-terminal/gnome-terminal-server
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   LANGUAGE=en_US
   PATH=(custom, user)
   LANG=en_US.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x7f98e2afbf1f :
testb  $0x4,0x16(%rax)
   PC (0x7f98e2afbf1f) ok
   source "$0x4" ok
   destination "0x16(%rax)" (0xbcae) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: gnome-terminal
  StacktraceTop:
   g_type_check_instance_is_a () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   gtk_widget_get_toplevel (widget=0x2580c30) at 
/build/buildd/gtk+3.0-3.14.9/./gtk/gtkwidget.c:11382
   window_group_cleanup_grabs (group=, 
window=window@entry=0x252a230) at 
/build/buildd/gtk+3.0-3.14.9/./gtk/gtkwindowgroup.c:110
   gtk_window_group_add_window (window_group=0x27e5c40, window=0x252a230) at 
/build/buildd/gtk+3.0-3.14.9/./gtk/gtkwindowgroup.c:169
   gtk_window_set_transient_for (window=0x252a230, parent=0x23ac7d0) at 
/build/buildd/gtk+3.0-3.14.9/./gtk/gtkwindow.c:3134
  Title: gnome-terminal-server crashed with SIGSEGV in 
g_type_check_instance_is_a()
  UpgradeStatus: Upgraded to vivid on 2015-03-29 (0 days ago)
  UserGroups: adm cdrom dialout dip kvm libvirtd lpadmin plugdev sambashare 
sbuild sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1438014/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1667227] Re: mate-terminal crashed with SIGSEGV in g_type_check_instance_is_a() - while editing Keyboard Shortcuts

2018-04-14 Thread yzp15 
*** This bug is a duplicate of bug 1438014 ***
https://bugs.launchpad.net/bugs/1438014

Reposted to gnome's gitlab:
https://gitlab.gnome.org/GNOME/gtk/issues/180

** Bug watch removed: GNOME Bug Tracker #607668
   https://bugzilla.gnome.org/show_bug.cgi?id=607668

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1667227

Title:
  mate-terminal crashed with SIGSEGV in g_type_check_instance_is_a() -
  while editing Keyboard Shortcuts

Status in gnome-terminal package in Ubuntu:
  Invalid
Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in mate-terminal package in Ubuntu:
  Invalid

Bug description:
  1) 
  $ lsb_release -rd
  Description:  Ubuntu Zesty Zapus (development branch)
  Release:  17.04

  Installed as Ubuntu-MATE 17.04 "Zesty Zapus" - Alpha amd64

  2) 
  $ apt-cache policy mate-terminal
  mate-terminal:
Installed: 1.17.0-0ubuntu1
Candidate: 1.17.0-0ubuntu1
  3) 
  Open mate-terminal
  Select "Edit" -> "Keyboard Shortcuts"
  Select "Help"->"Contents", click on default shortcut key "F1" to change
  Try to set it to various key sequences. Sometimes bug is triggered by 
pressing "Fn" key with some of Alt/Ctrl/Shift, sometimes by selecting 
Ctrl-Shift-W / Crtl-Shift-Alt-W
  Expected: changed keyboard shortcut for "Help"->"Contents"

  4) Abort and closed mate-terminal

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: mate-terminal 1.17.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-8.10-generic 4.10.0-rc8
  Uname: Linux 4.10.0-8-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Thu Feb 23 09:33:19 2017
  ExecutablePath: /usr/bin/mate-terminal
  ExecutableTimestamp: 1484233434
  InstallationDate: Installed on 2017-02-22 (1 days ago)
  InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Alpha amd64 (20170125)
  ProcCmdline: mate-terminal
  ProcCwd: /home/user
  SegvAnalysis:
   Segfault happened at: 0x7f883e41c321 :
testb  $0x4,0x16(%rax)
   PC (0x7f883e41c321) ok
   source "$0x4" ok
   destination "0x16(%rax)" (0x7001e) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: mate-terminal
  StacktraceTop:
   g_type_check_instance_is_a () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   gtk_widget_get_toplevel () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   gtk_window_group_add_window () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   gtk_window_set_transient_for () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  Title: mate-terminal crashed with SIGSEGV in g_type_check_instance_is_a()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1667227/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1438014] Re: gnome-terminal-server and mate-terminal crash when setting keyboard shortcuts

2018-04-14 Thread yzp15 
Hello. I had some debugging with valgrind and gdb for the error with
stacktrace top

 g_type_check_instance_is_a   glib2.0-2.43.92/./gobject/gtype.c:4016
 gtk_widget_get_toplevel   gtk+3.0-3.14.9/./gtk/gtkwidget.c:11382
 window_group_cleanup_grabs  gtk+3.0-3.14.9/./gtk/gtkwindowgroup.c:110
 gtk_window_group_add_window  gtk+3.0-3.14.9/./gtk/gtkwindowgroup.c:169
 gtk_window_set_transient_for gtk+3.0-3.14.9/./gtk/gtkwindow.c:3134

This is use-after-free due to incorrect grab deregistration (gtk_grab_remove 
tries to remove the grab not from the same window_group where it was added by 
gtk_grab_add)
Results were posted to   Bug #1667227 and  Bug #1667232
https://bugs.launchpad.net/ubuntu/+source/mate-terminal/+bug/1667227 and 
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1667232

I think that gnome-terminal grab use-after-free after editing keyboard
shortcuts may be not related to the patch
"debian/patches/016_no_offscreen_widgets_grabbing.patch" (it only helps
to report Critical to the log).

Both gtk_grab_add and gtk_grab_remove calls gtk_main_get_window_group
function, but it returns different results for these two calls (more
details at https://bugs.launchpad.net/ubuntu/+source/mate-
terminal/+bug/1667227/comments/8)

static GtkWindowGroup *
gtk_main_get_window_group (GtkWidget *widget)
...
  if (GTK_IS_WINDOW (toplevel))
return gtk_window_get_group (GTK_WINDOW (toplevel));
  else
return gtk_window_get_group (NULL);

At the time of gtk_grab_add (called from gtk_cell_renderer_accel_start_editing 
which is called from gtk_cell_renderer_start_editing) this widget had window = 
0x0 and parent = 0x0
And at time of gtk_grab_remove (called from 
gtk_cell_editable_event_box_key_press_event) same widget had window = 
0x55e507e0 (parent = 0x55e183f0) which leads to incorrect 
deregistration of the grab.

Parent of the widget was changed by
gtk_tree_view_multipress_gesture_pressed -> .. ->
gtk_cell_area_activate_cell -> gtk_cell_area_add_editable -> ..signal..
-> gtk_tree_view_column_add_editable_callback ->
_gtk_tree_view_add_editable -> gtk_tree_view_put ->
gtk_widget_set_parent

So, gtk_cell_area_activate_cell of gtk+3 (3.22.7) has some kind of incorrect 
ordering of actions which broke gtk_grab_add / gtk_grab_remove pair
https://github.com/GNOME/gtk/blob/6cc08d60efeb02afc0d67982c3dc205dfd16d7cd/gtk/gtkcellarea.c#L3388

3428 gtk_cell_renderer_start_editing (renderer,
...
3444 gtk_cell_area_add_editable (area, priv->focus_cell, editable_widget, 
cell_area);

(There was also quick and probably incorrect fix in Bug #1667227 for
this use-after-free with additional removing of grab from
gtk_window_get_group (NULL)
https://launchpadlibrarian.net/308873213/lp1667227_quick_fix_gtk_grab_remove.gtk+3.22.8.patch
)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1438014

Title:
  gnome-terminal-server and mate-terminal crash when setting keyboard
  shortcuts

Status in gtk+3.0 package in Ubuntu:
  Confirmed

Bug description:
  I put my laptop to sleep for an hour or so; when I restored it, gnome-
  terminal had crashed. It did not do this the previous time I suspended
  my laptop today, so I doubt that's immediately related.

  This crash can be reproduced by setting a shortcut in preferences.

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: gnome-terminal 3.14.2-0ubuntu2
  ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2
  Uname: Linux 3.19.0-10-generic x86_64
  NonfreeKernelModules: openafs
  ApportVersion: 2.16.2-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Mar 30 00:19:43 2015
  ExecutablePath: /usr/lib/gnome-terminal/gnome-terminal-server
  InstallationDate: Installed on 2014-02-03 (419 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  ProcCmdline: /usr/lib/gnome-terminal/gnome-terminal-server
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   LANGUAGE=en_US
   PATH=(custom, user)
   LANG=en_US.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x7f98e2afbf1f :
testb  $0x4,0x16(%rax)
   PC (0x7f98e2afbf1f) ok
   source "$0x4" ok
   destination "0x16(%rax)" (0xbcae) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: gnome-terminal
  StacktraceTop:
   g_type_check_instance_is_a () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   gtk_widget_get_toplevel (widget=0x2580c30) at 
/build/buildd/gtk+3.0-3.14.9/./gtk/gtkwidget.c:11382
   window_group_cleanup_grabs (group=, 
window=window@entry=0x252a230) at 
/build/buildd/gtk+3.0-3.14.9/./gtk/gtkwindowgroup.c:110
   gtk_window_group_add_window (window_group=0x27e5c40, window=0x252a230) at 
/build/buildd/gtk+3.0-3.14.9/./gtk/gtkwindowgroup.c:169
   gtk_window_set_transient_for (window=0x252a230, parent=0x23ac7d0) at

[Touch-packages] [Bug 1667227] Re: mate-terminal crashed with SIGSEGV in g_type_check_instance_is_a() - while editing Keyboard Shortcuts

2017-02-25 Thread yzp15 
** Patch added: "lp1667227_quick_fix_gtk_grab_remove.gtk+3.22.8.patch"
   
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1667227/+attachment/4826656/+files/lp1667227_quick_fix_gtk_grab_remove.gtk+3.22.8.patch

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1667227

Title:
  mate-terminal crashed with SIGSEGV in g_type_check_instance_is_a() -
  while editing Keyboard Shortcuts

Status in gnome-terminal package in Ubuntu:
  New
Status in gtk+3.0 package in Ubuntu:
  New
Status in mate-terminal package in Ubuntu:
  New

Bug description:
  1) 
  $ lsb_release -rd
  Description:  Ubuntu Zesty Zapus (development branch)
  Release:  17.04

  Installed as Ubuntu-MATE 17.04 "Zesty Zapus" - Alpha amd64

  2) 
  $ apt-cache policy mate-terminal
  mate-terminal:
Installed: 1.17.0-0ubuntu1
Candidate: 1.17.0-0ubuntu1
  3) 
  Open mate-terminal
  Select "Edit" -> "Keyboard Shortcuts"
  Select "Help"->"Contents", click on default shortcut key "F1" to change
  Try to set it to various key sequences. Sometimes bug is triggered by 
pressing "Fn" key with some of Alt/Ctrl/Shift, sometimes by selecting 
Ctrl-Shift-W / Crtl-Shift-Alt-W
  Expected: changed keyboard shortcut for "Help"->"Contents"

  4) Abort and closed mate-terminal

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: mate-terminal 1.17.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-8.10-generic 4.10.0-rc8
  Uname: Linux 4.10.0-8-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Thu Feb 23 09:33:19 2017
  ExecutablePath: /usr/bin/mate-terminal
  ExecutableTimestamp: 1484233434
  InstallationDate: Installed on 2017-02-22 (1 days ago)
  InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Alpha amd64 (20170125)
  ProcCmdline: mate-terminal
  ProcCwd: /home/user
  SegvAnalysis:
   Segfault happened at: 0x7f883e41c321 :
testb  $0x4,0x16(%rax)
   PC (0x7f883e41c321) ok
   source "$0x4" ok
   destination "0x16(%rax)" (0x7001e) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: mate-terminal
  StacktraceTop:
   g_type_check_instance_is_a () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   gtk_widget_get_toplevel () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   gtk_window_group_add_window () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   gtk_window_set_transient_for () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  Title: mate-terminal crashed with SIGSEGV in g_type_check_instance_is_a()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1667227/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1667227] Re: mate-terminal crashed with SIGSEGV in g_type_check_instance_is_a() - while editing Keyboard Shortcuts

2017-02-25 Thread yzp15 
Bug can be detected by "Gtk-CRITICAL **: gtk_widget_get_toplevel: assertion 
'GTK_IS_WIDGET (widget)' failed" messages, when mate-terminal or gnome-terminal 
are started from another console (with option --disable-factory) and keyboard 
shortcuts are edited.
I have such messages with gtk+3 (upstream) versions 3.16.7, 3.18.9, 3.20.9, 
3.22.8; valgrind can detect invalid reads (use after free) from 
window_group_cleanup_grabs -> gtk_widget_get_toplevel.

Simple, but potentially incorrect patch corrects this bug (both Gtk-CRITICAL 
messages and valgrind detections/SIGSEGVs) in mate-terminal and gnome-terminal 
(bug #1667232). It is tested with gtk+3 3.16.7, 3.18.9, 3.20.9, 3.22.8.
Just call _gtk_window_group_remove_grab from gtkmain.c:gtk_grab_remove twice, 
additional call with default window group, to clear all possible references to 
the widget from the grabs list:

diff --git a/gtk/gtkmain.c b/gtk/gtkmain.c
index 3152971256..681cb2bec9 100644
--- a/gtk/gtkmain.c
+++ b/gtk/gtkmain.c
@@ -2274,6 +2274,9 @@ gtk_grab_remove (GtkWidget *widget)
 
   group = gtk_main_get_window_group (widget);
   _gtk_window_group_remove_grab (group, widget);
+  // quick workaround for lp #1667227, lp #1667232
+  _gtk_window_group_remove_grab (gtk_window_get_group (NULL), widget);
+
   new_grab_widget = gtk_window_group_get_current_grab (group);
 
   gtk_grab_notify (group, NULL, widget, new_grab_widget, FALSE);

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1667227

Title:
  mate-terminal crashed with SIGSEGV in g_type_check_instance_is_a() -
  while editing Keyboard Shortcuts

Status in gnome-terminal package in Ubuntu:
  New
Status in gtk+3.0 package in Ubuntu:
  New
Status in mate-terminal package in Ubuntu:
  New

Bug description:
  1) 
  $ lsb_release -rd
  Description:  Ubuntu Zesty Zapus (development branch)
  Release:  17.04

  Installed as Ubuntu-MATE 17.04 "Zesty Zapus" - Alpha amd64

  2) 
  $ apt-cache policy mate-terminal
  mate-terminal:
Installed: 1.17.0-0ubuntu1
Candidate: 1.17.0-0ubuntu1
  3) 
  Open mate-terminal
  Select "Edit" -> "Keyboard Shortcuts"
  Select "Help"->"Contents", click on default shortcut key "F1" to change
  Try to set it to various key sequences. Sometimes bug is triggered by 
pressing "Fn" key with some of Alt/Ctrl/Shift, sometimes by selecting 
Ctrl-Shift-W / Crtl-Shift-Alt-W
  Expected: changed keyboard shortcut for "Help"->"Contents"

  4) Abort and closed mate-terminal

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: mate-terminal 1.17.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-8.10-generic 4.10.0-rc8
  Uname: Linux 4.10.0-8-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Thu Feb 23 09:33:19 2017
  ExecutablePath: /usr/bin/mate-terminal
  ExecutableTimestamp: 1484233434
  InstallationDate: Installed on 2017-02-22 (1 days ago)
  InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Alpha amd64 (20170125)
  ProcCmdline: mate-terminal
  ProcCwd: /home/user
  SegvAnalysis:
   Segfault happened at: 0x7f883e41c321 :
testb  $0x4,0x16(%rax)
   PC (0x7f883e41c321) ok
   source "$0x4" ok
   destination "0x16(%rax)" (0x7001e) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: mate-terminal
  StacktraceTop:
   g_type_check_instance_is_a () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   gtk_widget_get_toplevel () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   gtk_window_group_add_window () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   gtk_window_set_transient_for () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  Title: mate-terminal crashed with SIGSEGV in g_type_check_instance_is_a()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1667227/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1667227] Re: mate-terminal crashed with SIGSEGV in g_type_check_instance_is_a() - while editing Keyboard Shortcuts

2017-02-25 Thread yzp15 
gtk_main_get_window_group function return different results for
gtk_grab_add and gtk_grab_remove, but widget address was same in both
functions:

  if (GTK_IS_WINDOW (toplevel))
return gtk_window_get_group (GTK_WINDOW (toplevel));
  else
return gtk_window_get_group (NULL);

On gtk_grab_add window group is 0x55b0b160 for widget 0x55e50780:
Thread 1 "mate-terminal" hit Breakpoint 3, gtk_main_get_window_group 
(widget=0x55e50780) at ././gtk/gtkmain.c:2
025
2025  if (GTK_IS_WINDOW (toplevel))
$2044 (widget) = 0x55e50780
$2045 (toplevel) = 0x55e50780
$2046 (*widget) = {parent_instance = {g_type_instance = {g_class = 
0x55e5e800}, ref_count = 1, qdata = 0x2}, priv = 0x555
555e50690}
$2047 (*widget.priv) = {..., window = 0x0, registered_windows = 0x0, parent = 
0x0, event_contr
ollers = 0x0, accessible = 0x0}
#0  gtk_main_get_window_group (widget=0x55e50780) at ././gtk/gtkmain.c:2025
#1  0x771f3bb3 in gtk_grab_add (widget=0x55e50780) at 
././gtk/gtkmain.c:2231
#2  0x770ac1d1 in gtk_cell_renderer_accel_start_editing 
(cell=0x55845270, event=0x55d416f0, widget=
0x55e183f0, path=0x55e57720 "2:0", background_area=0x7fffc2e0, 
cell_area=0x7fffc2e0, flags=(unknown
: 0)) at ././gtk/gtkcellrendereraccel.c:497
#3  0x770a92dd in gtk_cell_renderer_start_editing (cell=0x55845270, 
event=0x55d416f0, widget=0x
55e183f0, path=0x55e57720 "2:0", background_area=0x7fffc2e0, 
cell_area=0x7fffc2e0, flags=(unknown: 0)) 
at ././gtk/gtkcellrenderer.c:921
#4  0x7709d47e in gtk_cell_area_activate_cell (area=0x55e0d140, 
widget=0x55e183f0, renderer=0x55845270, event=0x55d416f0, 
cell_area=0x7fffc380, flags=(unknown: 0)) at ././gtk/gtkcellarea.c:3432
#5  0x77096407 in gtk_cell_area_real_event (area=0x55e0d140, 
context=0x55e26850, widget=0x55e183f0, event=0x55d416f0, 
cell_area=0x7fffc570, flags=(unknown: 0)) at ././gtk/gtkcellarea.c:1101


At time of gtk_grab_remove, when event is delivered to widget 0x55e50780 
from gtk_main_do_event, its toplevel was 0x55ddb0d0
Thread 1 "mate-terminal" hit Breakpoint 3, gtk_main_get_window_group 
(widget=0x55e50780) at ././gtk/gtkmain.c:2025
2025  if (GTK_IS_WINDOW (toplevel))
$2092 (widget) = 0x55e50780
$2093 (toplevel) = 0x55ddb0d0
$2094 (*widget) = {parent_instance = {g_type_instance = {g_class = 
0x55e5e800}, ref_count = 7, qdata = 0x55ecf180}, priv = 0x55e50690}
$2095 (*widget.priv) = {, window = 0x55e507e0, registered_windows = 
0x5595
7d00, parent = 0x55e183f0, event_controllers = 0x0, accessible = 
0x55e1d320}
#0  gtk_main_get_window_group (widget=0x55e50780) at ././gtk/gtkmain.c:2025
#1  0x771f3d8c in gtk_grab_remove (widget=0x55e50780) at 
././gtk/gtkmain.c:2286
#2  0x770ac56b in gtk_cell_editable_event_box_key_press_event 
(widget=0x55e50780, event=0x55e473c0)
 at ././gtk/gtkcellrendereraccel.c:645


Parent of the widget was changed by gtk_tree_view_multipress_gesture_pressed -> 
.. -> gtk_cell_area_activate_cell -> gtk_cell_area_add_editable -> ..signal.. 
-> gtk_tree_view_column_add_editable_callback -> _gtk_tree_view_add_editable -> 
gtk_tree_view_put -> gtk_widget_set_parent

So, gtk_cell_area_activate_cell of gtk+3 (3.22.7) has incorrect order of 
actions which broke gtk_grab_add / gtk_grab_remove pair
https://github.com/GNOME/gtk/blob/6cc08d60efeb02afc0d67982c3dc205dfd16d7cd/gtk/gtkcellarea.c#L3388

3428   gtk_cell_renderer_start_editing (renderer,
...
3444   gtk_cell_area_add_editable (area, priv->focus_cell, editable_widget, 
cell_area);

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1667227

Title:
  mate-terminal crashed with SIGSEGV in g_type_check_instance_is_a() -
  while editing Keyboard Shortcuts

Status in gnome-terminal package in Ubuntu:
  New
Status in gtk+3.0 package in Ubuntu:
  New
Status in mate-terminal package in Ubuntu:
  New

Bug description:
  1) 
  $ lsb_release -rd
  Description:  Ubuntu Zesty Zapus (development branch)
  Release:  17.04

  Installed as Ubuntu-MATE 17.04 "Zesty Zapus" - Alpha amd64

  2) 
  $ apt-cache policy mate-terminal
  mate-terminal:
Installed: 1.17.0-0ubuntu1
Candidate: 1.17.0-0ubuntu1
  3) 
  Open mate-terminal
  Select "Edit" -> "Keyboard Shortcuts"
  Select "Help"->"Contents", click on default shortcut key "F1" to change
  Try to set it to various key sequences. Sometimes bug is triggered by 
pressing "Fn" key with some of Alt/Ctrl/Shift, sometimes by selecting 
Ctrl-Shift-W / Crtl-Shift-Alt-W
  Expected: changed keyboard shortcut for "Help"->"Contents"

  4) Abort and closed mate-terminal

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: mate-terminal 1.17.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-8.10-generic 4.10.0-rc8

[Touch-packages] [Bug 1667227] Re: mate-terminal crashed with SIGSEGV in g_type_check_instance_is_a() - while editing Keyboard Shortcuts

2017-02-25 Thread yzp15 
** Also affects: gtk+3.0 (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1667227

Title:
  mate-terminal crashed with SIGSEGV in g_type_check_instance_is_a() -
  while editing Keyboard Shortcuts

Status in gnome-terminal package in Ubuntu:
  New
Status in gtk+3.0 package in Ubuntu:
  New
Status in mate-terminal package in Ubuntu:
  New

Bug description:
  1) 
  $ lsb_release -rd
  Description:  Ubuntu Zesty Zapus (development branch)
  Release:  17.04

  Installed as Ubuntu-MATE 17.04 "Zesty Zapus" - Alpha amd64

  2) 
  $ apt-cache policy mate-terminal
  mate-terminal:
Installed: 1.17.0-0ubuntu1
Candidate: 1.17.0-0ubuntu1
  3) 
  Open mate-terminal
  Select "Edit" -> "Keyboard Shortcuts"
  Select "Help"->"Contents", click on default shortcut key "F1" to change
  Try to set it to various key sequences. Sometimes bug is triggered by 
pressing "Fn" key with some of Alt/Ctrl/Shift, sometimes by selecting 
Ctrl-Shift-W / Crtl-Shift-Alt-W
  Expected: changed keyboard shortcut for "Help"->"Contents"

  4) Abort and closed mate-terminal

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: mate-terminal 1.17.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-8.10-generic 4.10.0-rc8
  Uname: Linux 4.10.0-8-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Thu Feb 23 09:33:19 2017
  ExecutablePath: /usr/bin/mate-terminal
  ExecutableTimestamp: 1484233434
  InstallationDate: Installed on 2017-02-22 (1 days ago)
  InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Alpha amd64 (20170125)
  ProcCmdline: mate-terminal
  ProcCwd: /home/user
  SegvAnalysis:
   Segfault happened at: 0x7f883e41c321 :
testb  $0x4,0x16(%rax)
   PC (0x7f883e41c321) ok
   source "$0x4" ok
   destination "0x16(%rax)" (0x7001e) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: mate-terminal
  StacktraceTop:
   g_type_check_instance_is_a () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   gtk_widget_get_toplevel () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   gtk_window_group_add_window () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   gtk_window_set_transient_for () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  Title: mate-terminal crashed with SIGSEGV in g_type_check_instance_is_a()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1667227/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp