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 699376 - FileChooser opens up blank when opened second time
FileChooser opens up blank when opened second time
Status: RESOLVED DUPLICATE of bug 483502
Product: gtk+
Classification: Platform
Component: Widget: GtkFileChooser
3.8.x
Other Linux
: Normal normal
: ---
Assigned To: gtk-bugs
Federico Mena Quintero
Depends on:
Blocks:
 
 
Reported: 2013-05-01 12:47 UTC by Gursimran singh
Modified: 2013-10-06 05:59 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Test case (2.26 KB, text/x-vala)
2013-05-01 12:47 UTC, Gursimran singh 		Details

Description Gursimran singh 2013-05-01 12:47:03 UTC 
Created attachment 242990 [details]
Test case

The FileChooser opens up blank when you click cancel and open it again.

I'm attaching a test case (vala code) with this bug.
Refer - bug#699013

Steps
1. One the FileChooser by clicking the button
2. Click Cancel
3. Open the FIleChooser again.

This bug can be reproduced in master branch
Comment 1 Matthias Clasen 2013-05-13 01:58:02 UTC 
works fine here, with 3.8 or master
are you still seeing this problem ?
Comment 2 Timothy Arceri 2013-06-28 14:56:25 UTC 
Reading bug 699013 this test case never actually caused the bug to occur. The issue was the in the gnome-boxes code they were using .hide() instead of .destroy()

I tried changing the testcase to use .hide() but I still could not reproduce the issue. 

In any case this looks like a duplicate of bug 483502

It would be good to have a reliable test case for this as 483502 is about Gimp which no longer hides the filechooser either as a result of this and other issues reported when reusing the filechooser so there doesn't seem to be an easy way to reproduce it currently.
Comment 3 Matthias Clasen 2013-10-06 05:59:34 UTC 

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