GNOME Bugzilla – Bug 694532
CRITICAL **: file gtktreeviewaccessible.c: line 331 (set_cell_data): should not be reached
Last modified: 2018-04-15 00:07:49 UTC
The source code says "this should never happen", but it happens when a GtkTreeView has cursor focus and multiple rows have been deleted from the underlying model. In turn, something runs into an invalid path (= not getting a valid iter), which makes gtktreeviewaccessible.c warn. If the GtkTreeView does not have focus, this does not happen. The documentation says that unsetting the cursor would be possible, but that either doesn't work or doesn't avoid the warning. [...] $ rpm -q gtk3 gtk3-3.6.4-1.fc18.x86_64 CRITICAL **: file gtktreeviewaccessible.c: line 331 (set_cell_data): should not be reached ...
+ Trace 231559
gtk/a11y/gtktreeviewaccessible.c 323 path = cell_info_get_path (cell_info); 324 if (path == NULL || 325 !gtk_tree_model_get_iter (model, &iter, path)) 326 { 327 /* We only track valid cells, this should never happen */ 328 g_return_if_reached (); 329 } 330 gtk_tree_path_free (path);
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