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 444974 - gtk.gdk.Screen() creates new GdkScreen instance
gtk.gdk.Screen() creates new GdkScreen instance
Status: RESOLVED FIXED
Product: pygtk
Classification: Bindings
Component: gdk
Git Master
Other Linux
: Normal normal
: ---
Assigned To: Nobody's working on this now (help wanted and appreciated)
Python bindings maintainers
Depends on:
Blocks:
 
 
Reported: 2007-06-07 03:23 UTC by Yevgen Muntyan
Modified: 2008-02-06 13:19 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
patch (1.21 KB, patch)
2007-06-07 03:24 UTC, Yevgen Muntyan 		committed Details | Review

Description Yevgen Muntyan 2007-06-07 03:23:39 UTC 
gtk.gdk.Screen() creates new GdkScreen instance, so if people call X11 methods on it, they get segfault. While creating a new screen object doesn't make sense, the constructor could do something like what Display() does, e.g. call gdk_screen_get_default(); or it could raise an exception.
Comment 1 Yevgen Muntyan 2007-06-07 03:24:10 UTC 
Created attachment 89527 [details] [review]
patch

This one calls gdk_screen_get_default().
Comment 2 Johan (not receiving bugmail) Dahlin 2008-02-05 22:35:28 UTC 
Comment on attachment 89527 [details] [review]
patch

Looks good
Comment 3 Gian Mario Tagliaretti 2008-02-06 13:19:58 UTC 
Sending        ChangeLog
Sending        gtk/gdk-base.defs
Sending        gtk/gdk.override
Transmitting file data ...
Committed revision 2960.