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 710436 - Assertion failure using GtkFileChooserDialog with a file filter
Assertion failure using GtkFileChooserDialog with a file filter
Status: RESOLVED FIXED
Product: gtk+
Classification: Platform
Component: Widget: GtkFileChooser
3.10.x
Other Linux
: Normal normal
: ---
Assigned To: gtk-bugs
Federico Mena Quintero
: 692546 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2013-10-18 06:45 UTC by Andrew Church
Modified: 2015-02-24 11:16 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Glade UI file demonstrating bug (1.52 KB, application/xml)
2013-10-18 06:45 UTC, Andrew Church
Details

Description Andrew Church 2013-10-18 06:45:46 UTC
Created attachment 257613 [details]
Glade UI file demonstrating bug

If a file chooser dialog has a filter attached to it, file operations in the directory displayed in the file chooser can corrupt the list of displayed files, eventually causing a crash with this error:

Gtk:ERROR:gtkrbtree.c:465:_gtk_rbtree_insert_after: assertion failed: (_gtk_rbtree_is_nil (tree->root))

Sometimes the following nonfatal assertion can also be seen:

(glade:1694): Gtk-CRITICAL **: _gtk_rbtree_reorder: assertion 'tree->root->count == length' failed

To reproduce, load the attached file in Glade, then (in a separate terminal) repeatedly touch and rm a file which does _not_ match the file filter (in this case *.foo) in Glade's cwd.  In my case, the nonfatal assertion failure appears on the second "touch", and subsequently attempting to remove the filter from the dialog triggers the fatal assertion.  The file operations will also sometimes cause an unrelated entry to be removed from the file list.
Comment 1 Lubomir Rintel 2015-02-24 09:06:22 UTC
Your testcase works fine for me with gtk3-3.14.8-2.fc21.x86_64.

I'm wondering if you can confirm?
Comment 2 Lubomir Rintel 2015-02-24 09:06:55 UTC
*** Bug 692546 has been marked as a duplicate of this bug. ***
Comment 3 Andrew Church 2015-02-24 11:16:23 UTC
(In reply to Lubomir Rintel from comment #1)
> Your testcase works fine for me with gtk3-3.14.8-2.fc21.x86_64.
> 
> I'm wondering if you can confirm?

I can indeed no longer reproduce the bug using gtk+-3.14.8.  It seems to have been fixed sometime since 3.12.2.

Marking FIXED.