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 125257 - GtkSocket doesn't check screen before reparenting
GtkSocket doesn't check screen before reparenting
Status: RESOLVED OBSOLETE
Product: gnome-panel
Classification: Other
Component: notification area
unspecified
Other Linux
: Normal critical
: ---
Assigned To: Panel Maintainers
Panel Maintainers
Depends on:
Blocks: 346162
 
 
Reported: 2003-10-23 02:31 UTC by Gregory Merchan
Modified: 2020-11-06 20:25 UTC
See Also:
GNOME target: ---
GNOME version: 2.9/2.10


Description Gregory Merchan 2003-10-23 02:31:52 UTC 
(Looking at CVS HEAD)
I'm unable to find a screen check before gtk/gdk reparents a window.
According to the manual, reparenting from another screen will result
in a BadMatch error. The Gtk+ API documentation does not mention that
error will occur.

The notification area code doesn't check the screen before calling
gtk_socket_add_id(), and this is almost surely the cause of the
multi-screen (non-Xinerama) errors that have been reported against it.
Those reports also indicate mapping is occuring though reparenting
was unsuccessful, but I'm not sure Gtk+ is responsible.
Comment 1 Owen Taylor 2003-10-23 15:49:08 UTC 
I don't consider this a GTK+ problem. All GTK+ could conceivably
do would be to give a better warning message.
Comment 2 Mark McLoughlin 2004-02-04 10:03:21 UTC 
Re-assigning to gnome-panel-maint. Apologies for the spam.
Comment 3 Luis Villa 2004-02-05 18:51:06 UTC 
What's the user effect here?
Comment 4 Gregory Merchan 2004-02-05 19:25:01 UTC 
Bug #115704 is caused by this, at least in part.
Comment 5 Stephane Wirtel 2005-01-27 19:49:51 UTC 
Can I close this bug ?
Comment 6 Vincent Untz 2005-01-27 23:50:14 UTC 
Why do you want to close this bug?
Comment 7 Kjartan Maraas 2007-02-09 15:17:28 UTC 
Any pointers to what's missing here? Is it just a function call or more involved?
Comment 8 Aryeh Gregor 2008-02-03 15:58:57 UTC 
(In reply to comment #3)
> What's the user effect here?

Well, this is marked as blocking bug 346162.  Whether that's correct or not I can't say, but if it is, that's a user effect.
Comment 9 André Klapper 2020-11-06 20:25:41 UTC 
bugzilla.gnome.org is being replaced by gitlab.gnome.org. We are closing all old bug reports in Bugzilla which have not seen updates for many years.

If you can still reproduce this issue in a currently supported version of GNOME (currently that would be 3.38), then please feel free to report it at https://gitlab.gnome.org/GNOME/gnome-panel/-/issues/

Thank you for reporting this issue and we are sorry it could not be fixed.