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 369301 - Closing file chooser dialog causes hang
Closing file chooser dialog causes hang
Status: RESOLVED DUPLICATE of bug 355409
Product: rhythmbox
Classification: Other
Component: User Interface
0.9.6
Other Linux
: Normal normal
: ---
Assigned To: RhythmBox Maintainers
RhythmBox Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-11-02 08:45 UTC by Arthur Taylor
Modified: 2006-11-03 01:06 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Arthur Taylor 2006-11-02 08:45:34 UTC 
1. Open a file chooser dialog (any of the three, import folder, import file, open playlist).
2. Close it in any matter (Okay, Cancel or delete window).
3. Result: Hang. Windows don't redraw, app is un-responsive.

I've traced the hang back to the calls to delete the dialog widget in the add_to_library_response_cb callback. There are two instances of gtk_widget_destroy (GTK_WIDGET (dialog));, each hang at their respected instances (one for the cancel/delete event, the other for the accept event.)  I haven't bothered to check the callback for the load playlist file, but I imagine that it is the same situation. The code in question is similar to the gtk documentation's example.

Tried with
rhythmbox-0.9.6
gtk+-2.10.6
glib-2.12.4
Comment 1 Arthur Taylor 2006-11-02 08:49:04 UTC 
Forgot to add:
gcc-3.4.4

I have not updated or otherwised change my buildchain for about a year, long before rhythmbox developed this quirk.
Comment 2 Jonathan Matthew 2006-11-02 08:53:46 UTC 
This is most likely a duplicate of bug 355409.  If you have libgnomeui 2.16.0, try upgrading to 2.16.1.
Comment 3 Arthur Taylor 2006-11-03 01:06:33 UTC 
It would indeed be a duplicate of bug 355409 as an upgrade fixed it. Sorry for the bug-spam.

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