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 53353 - Check results of all X calls
Check results of all X calls
Status: RESOLVED OBSOLETE
Product: gtk+
Classification: Platform
Component: Backend: X11
1.3.x
Other All
: Low normal
: Medium fix
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2001-04-18 18:18 UTC by Owen Taylor
Modified: 2013-10-04 12:20 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Owen Taylor 2001-04-18 18:18:37 UTC 
There are considerable number of calls that GDK makes to
X that could conceivably fail if the user has done 
a gdk_error_trap_push(). In quite a few cases, GTK+
assumes that these will succeed, which can result in
segfaults.

While a blanket gdk_error_trap_push() over calls to
GDK functions is not really a good way of doing things,
systems like Bonobo do it, and it would be rather nice
to support it.

Note that in some cases, the GDK API may assume that the
call succeeds. But usually, some sort of fallback or
kludge should deal with this.
Comment 1 Elijah Newren 2004-06-19 18:45:36 UTC 
Mass changing gtk+ bugs with target milestone of 2.4.2 to target 2.4.4, as
Matthias said he was trying to do himself on IRC and was asking for help with. 
If you see this message, it means I was successful at fixing the borken-ness in
bugzilla :)  Sorry for the spam; just query on this message and delete all
emails you get with this message, since there will probably be a lot.
Comment 2 Timothy Arceri 2013-10-04 07:32:52 UTC 
Is the still a valid bug 12 years on? With a shift in focus to Wayland I would assume this could safely be set to wont fix?