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 664481 - GtkFileChooserDialog folder selection crashes
GtkFileChooserDialog folder selection crashes
Status: RESOLVED DUPLICATE of bug 664137
Product: gtk+
Classification: Platform
Component: Widget: GtkFileChooser
3.2.x
Other Linux
: Normal critical
: ---
Assigned To: gtk-bugs
Federico Mena Quintero
Depends on:
Blocks:
 
 
Reported: 2011-11-21 15:29 UTC by Chris Vine
Modified: 2011-11-29 20:53 UTC
See Also:
GNOME target: ---
GNOME version: 3.1/3.2

Attachments
Sample test program (643 bytes, text/plain)
2011-11-21 15:29 UTC, Chris Vine 		Details
backtrace (1.81 KB, text/plain)
2011-11-21 15:32 UTC, Chris Vine 		Details

Description Chris Vine 2011-11-21 15:29:59 UTC 
Created attachment 201822 [details]
Sample test program

Folder selection using GtkFileChooserDialog in gtk+3.2.2 crashes the application after "double-click" operations are carried out on those parts of the dialog requiring a double click (anything in the right-hand folder/file display).

On each occasion a double-click on one of these items is made, the following error message is displayed:

GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed

After some 3 to five such double-clicks, the program crashes.  A sample test program which demonstrates this is attached.  Also attached is a backtrace.
Comment 1 Chris Vine 2011-11-21 15:32:15 UTC 
Created attachment 201823 [details]
backtrace
Comment 2 Chris Vine 2011-11-22 13:58:20 UTC 
This is to confirm that this bug is not present in gtk+-3.2.1.  In version 3.2.2, the bug is also triggered when selecting files as well as when selecting directories (gedit crashes with this).
Comment 3 Federico Mena Quintero 2011-11-29 20:53:47 UTC 

*** This bug has been marked as a duplicate of bug 664137 ***