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 107217 - gdk_display_close is a recipe for segfault on X11
gdk_display_close is a recipe for segfault on X11
Status: RESOLVED DUPLICATE of bug 85715
Product: gtk+
Classification: Platform
Component: Backend: X11
2.2.x
Other other
: Normal major
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2003-02-27 20:15 UTC by Ethan Blanton
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Ethan Blanton 2003-02-27 20:15:52 UTC
gdk_display_close in Gtk2.2.1 (and 2.2.0) causes, in normal operation,
gdk_display_x11_dispose to be called twice (once explicitly, once by way of
g_object_unref) ... the second time a couple of Xlib functions are called
with a NULL display pointer, causing them to segfault.

There is a patch at:

http://web.ics.purdue.edu/~eblanton/gtk/gtk+-2.2.1-gdk_display_close-fix.diff

which fixes this.

(I personally consider this a critical bug because a: I need it, and b: it
causes a segfault ... however, I have marked it as merely major because I
suspect not many people are using this functionality -- yet)
Comment 1 Owen Taylor 2003-02-27 20:27:31 UTC
I very much doubt that this patch is anywhere near complete;
there are a lot of GTK+ resources that needs to be
cleaned up.

Basically, gdk_display_close() is known not to work for
2.2. Sorry.


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