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 624224 - Missing accessor for GdkDisplay.closed
Missing accessor for GdkDisplay.closed
Status: RESOLVED FIXED
Product: gtk+
Classification: Platform
Component: Widget: Other
2.21.x
Other Linux
: Normal normal
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks: 597610
 
 
Reported: 2010-07-13 08:35 UTC by John Stowers
Modified: 2010-08-07 11:22 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Add gdk_display_is_closed (1.87 KB, patch)
2010-07-17 00:13 UTC, John Stowers 		none Details | Review
Add gdk_display_is_closed (2.36 KB, patch)
2010-07-25 11:19 UTC, John Stowers 		none Details | Review

Description John Stowers 2010-07-13 08:35:18 UTC 
For building PyGtk against Gtk-3.0 [1]

AFAICT PyGtk keeps the display around when closing it, so that it is not collected before the python object is collected [2][3], or something more complex related to the async nature of X11....

To do that we need to check if the display has been previously closed.

[1] http://mail.gnome.org/archives/gtk-devel-list/2010-July/msg00005.html
[2] http://git.gnome.org/browse/pygtk/tree/gtk/gdk.override#n1571
[3] http://git.gnome.org/browse/pygtk/tree/ChangeLog.pre-2-16#n1280
Comment 1 John Stowers 2010-07-17 00:13:30 UTC 
Created attachment 166047 [details] [review]
Add gdk_display_is_closed
Comment 2 John Stowers 2010-07-17 00:15:16 UTC 
Comment on attachment 166047 [details] [review]
Add gdk_display_is_closed

against 2.22 branch
Comment 3 John Stowers 2010-07-25 11:19:29 UTC 
Created attachment 166516 [details] [review]
Add gdk_display_is_closed

Updated patch, adds entry to gdk-sections.txt
Comment 4 John Stowers 2010-07-29 22:15:38 UTC 
Ping? ACK/NACK?
Comment 5 Matthias Clasen 2010-08-04 23:28:05 UTC 
This one looks harmless to me, so lets just add it. To 2.22 too, please
Comment 6 John Stowers 2010-08-07 11:22:13 UTC 
This problem has been fixed in the development version. The fix will be available in the next major software release. Thank you for your bug report.