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 593805 - Critical when calling gtk_dialog_run() on a non-modal dialog
Critical when calling gtk_dialog_run() on a non-modal dialog
Status: RESOLVED DUPLICATE of bug 581633
Product: gtk+
Classification: Platform
Component: Backend: X11
2.16.x
Other Linux
: Normal normal
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2009-09-01 14:03 UTC by Philip Chimento
Modified: 2009-09-01 14:40 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Test case for critical, compile with: gcc `pkg-config gtk+-2.0 --cflags --libs` testbug.c -o testbug (373 bytes, text/x-csrc)
2009-09-01 14:03 UTC, Philip Chimento 		Details

Description Philip Chimento 2009-09-01 14:03:20 UTC 
Created attachment 142245 [details]
Test case for critical, compile with: gcc `pkg-config gtk+-2.0 --cflags --libs` testbug.c -o testbug

Calling gtk_dialog_run() on a non-modal dialog generates the following
critical:

Gdk-CRITICAL **: gdk_x11_atom_to_xatom_for_display: assertion `atom !=
GDK_NONE' failed

I don't think it should do that. The documentation for gtk_dialog_run() says:

"Also, during gtk_dialog_run() the dialog will be modal."

implying that gtk_dialog_run() will make the dialog modal even if it is not.
Furthermore, I seem to remember doing this in earlier versions of GTK without
any complaint, but I can't verify that right now.

A test program is attached which reproduces the critical.
Comment 1 Claudio Saavedra 2009-09-01 14:40:58 UTC 

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