GNOME Bugzilla – Bug 548782
When delete a row in gtktreeview, children-changed::remove should be emitted
Last modified: 2018-04-15 00:36:16 UTC
When delete a row in gtktreeview, children-changed::remove should be emitted.
Created attachment 117108 [details] [review] patch
Li, this change causes the gdm greeter to crash: (gdb) bt
+ Trace 206346
I believe this is another bug. People can't find it because gail doesn't emit the signal before. Can I have a full trace?
Created attachment 118074 [details] full stacktrace
Created attachment 118085 [details] [review] patch Here is a patch for at-spi which may fix the crash. (Not for sure because I can not reproduce the crash.) It will be great that someone can test the patch. Thanks.
Seems to work fine in quick testing.
Ah, but it makes evolution crash now. whackamole... Program received signal SIGSEGV, Segmentation fault. 0x00746915 in spi_atk_bridge_signal_listener (signal_hint=0xbfffe71c, n_param_values=3, param_values=0x91d5720, data=0x80d08c8) at bridge.c:1165 1165 else if (strcmp (detail, "add") == 0) (gdb) print detail $1 = (const gchar *) 0x0 (gdb)
Adding a detail != NULL check to the condition fixes the evo crash
Yes. Thanks, Matthias. The datail should be "add" or "remove" ideally. I need to check why a children-changed is emitted without "add" or "remove".
I will file a bug on at-spi and release a new tarball with 2.23.92.
Here is a slightly more robust fix, see bug 530776. We still need to fix evolutions a11y code to emit this signal correctly.
Created attachment 120984 [details] [review] patch
Thanks. After applying the patch, atk-bridge's behavior will be a little different if detail is null but child is an atkobject. I am not sure if some object is doing that...
We're moving to gitlab! As part of this move, we are moving bugs to NEEDINFO if they haven't seen activity in more than a year. If this issue is still important to you and still relevant with GTK+ 3.22 or master, please reopen it and we will migrate it to gitlab.
As announced a while ago, we are migrating to gitlab, and bugs that haven't seen activity in the last year or so will be not be migrated, but closed out in bugzilla. If this bug is still relevant to you, you can open a new issue describing the symptoms and how to reproduce it with gtk 3.22.x or master in gitlab: https://gitlab.gnome.org/GNOME/gtk/issues/new