Thunar tree view behaves very strangely
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Thunar File Manager |
Fix Released
|
Unknown
|
|||
thunar (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: thunar
I have noticed a rather annoying bug in Thunar when the tree view is used for the left pane. If I do the following:
- Change into a random directory, which contains subdirectories (e.g. directory x).
- In the tree view click on the arrow left of the symbol of directory x (uncollapses its subdirectories).
- Now delete or move a file in directory x (can be an empty file).
- Now the tree view looks very weird (the following screenshots show it before and after deleting a file).
http://
http://
- The right look of the tree view can be brought back by collapsing directory x or a directory above directory x in the tree view.
When I start Thunar as root (only way to get a console output), messages likes this appear when I delete a file as described above:
-------
(thunar:25922): Gtk-CRITICAL **: file gtktreeview.c: line 6054 (do_validate_rows): assertion `gtk_tree_
There is a disparity between the internal view of the GtkTreeView,
and the GtkTreeModel. This generally means that the model has changed
without letting the view know. Any display from now on is likely to
be incorrect.
(thunar:25922): Gtk-CRITICAL **: file gtktreeview.c: line 6054 (do_validate_rows): assertion `gtk_tree_
There is a disparity between the internal view of the GtkTreeView,
and the GtkTreeModel. This generally means that the model has changed
without letting the view know. Any display from now on is likely to
be incorrect.
(thunar:25922): Gtk-CRITICAL **: _gtk_rbtree_
(thunar:25922): Gtk-CRITICAL **: _gtk_rbtree_
(thunar:25922): Gtk-CRITICAL **: _gtk_rbtree_
(thunar:25922): Gtk-CRITICAL **: _gtk_rbtree_
(thunar:25922): Gtk-CRITICAL **: _gtk_rbtree_
(thunar:25922): Gtk-CRITICAL **: _gtk_rbtree_
(thunar:25922): Gtk-CRITICAL **: _gtk_rbtree_
(thunar:25922): Gtk-CRITICAL **: file gtktreeview.c: line 6054 (do_validate_rows): assertion `gtk_tree_
There is a disparity between the internal view of the GtkTreeView,
and the GtkTreeModel. This generally means that the model has changed
without letting the view know. Any display from now on is likely to
be incorrect.
(thunar:25922): Gtk-CRITICAL **: gtk_tree_
(thunar:25922): GLib-GObject-
(thunar:25922): GLib-GObject-
(thunar:25922): Gtk-CRITICAL **: gtk_tree_
(thunar:25922): GLib-GObject-
(thunar:25922): GLib-GObject-
(thunar:25922): Gtk-CRITICAL **: gtk_tree_
(thunar:25922): GLib-GObject-
(thunar:25922): GLib-GObject-
(thunar:25922): Gtk-CRITICAL **: gtk_tree_
(thunar:25922): GLib-GObject-
(thunar:25922): GLib-GObject-
(thunar:25922): Gtk-CRITICAL **: gtk_tree_
(thunar:25922): Gtk-CRITICAL **: file gtktreeview.c: line 6054 (do_validate_rows): assertion `gtk_tree_
There is a disparity between the internal view of the GtkTreeView,
and the GtkTreeModel. This generally means that the model has changed
without letting the view know. Any display from now on is likely to
be incorrect.
(thunar:25922): Gtk-CRITICAL **: gtk_tree_
(thunar:25922): GLib-GObject-
(thunar:25922): GLib-GObject-
(thunar:25922): Gtk-CRITICAL **: gtk_tree_
(thunar:25922): GLib-GObject-
(thunar:25922): GLib-GObject-
(thunar:25922): Gtk-CRITICAL **: gtk_tree_
(thunar:25922): GLib-GObject-
(thunar:25922): GLib-GObject-
(thunar:25922): Gtk-CRITICAL **: gtk_tree_
(thunar:25922): GLib-GObject-
(thunar:25922): GLib-GObject-
(thunar:25922): Gtk-CRITICAL **: gtk_tree_
(thunar:25922): Gtk-CRITICAL **: file gtktreeview.c: line 6054 (do_validate_rows): assertion `gtk_tree_
There is a disparity between the internal view of the GtkTreeView,
and the GtkTreeModel. This generally means that the model has changed
without letting the view know. Any display from now on is likely to
be incorrect.
-------
This happens on my AMD64-installation of Edgy and I can reproduce it also with the Xubuntu 6.10-Live-CD. I also compiled manually older and current versions of Thunar from the svn repository on Edgy, all show the same behaviour.
On Dapper, which I used before, this bug seems to be definately not present (likewise with current and older versions of Thunar), so I am not sure if the cause for this problem lies somewhere in the source code of Thunar itself and I would maybe suppose instead that this could be some weird interaction between Thunar and certain versions of other software, but I have absolutely no deeper knowledge.
Kind regards,
Jan
Changed in thunar: | |
status: | Unknown → Confirmed |
Changed in thunar: | |
status: | Confirmed → Fix Released |
I can confirm this. I've seen it for a while on edgy.