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 694532 - CRITICAL **: file gtktreeviewaccessible.c: line 331 (set_cell_data): should not be reached
CRITICAL **: file gtktreeviewaccessible.c: line 331 (set_cell_data): should n...
Status: RESOLVED OBSOLETE
Product: gtk+
Classification: Platform
Component: Widget: GtkTreeView
3.6.x
Other Linux
: Normal normal
: ---
Assigned To: gtktreeview-bugs
gtktreeview-bugs
Depends on:
Blocks:
 
 
Reported: 2013-02-23 14:52 UTC by Michael Schwendt
Modified: 2018-04-15 00:07 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Michael Schwendt 2013-02-23 14:52:08 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

...
  • #0 set_cell_data
    from /lib64/libgtk-3.so.0
  • #1 create_cell
    from /lib64/libgtk-3.so.0
  • #2 _gtk_tree_view_accessible_add_state
    from /lib64/libgtk-3.so.0
  • #3 gtk_tree_view_real_set_cursor
    from /lib64/libgtk-3.so.0
  • #4 gtk_tree_view_row_deleted
    from /lib64/libgtk-3.so.0

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);
Comment 1 Matthias Clasen 2018-02-10 04:58:38 UTC
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.
Comment 2 Matthias Clasen 2018-04-15 00:07:49 UTC
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