You are not logged in.
There are still lots of gdk messages in .xsession-errors when using Firefox :
hundreds of
(firefox:4889): Gdk-WARNING **: XID collision, trouble ahead
tens of
(firefox:18520): Gdk-CRITICAL **: gdk_x11_atom_to_xatom_for_display: assertion `atom != GDK_NONE' failed
I searched the web for these messages and I found that they result from known bugs.
The Gdk-CRITICAL messages appently should have been fixed with a new gtk+ release, but it's not yet the case. Maybe in the next 2.18 release.
It is said to be harmless despite the critical term used.
The "XID collision" bug is also known since a long time and is not solved yet. It seems more problematic because it may result in crashes in some situations.
But the Gdk-WARNING message was added only for diagnostics reasons by Matthias Clasen who wrote :
This should help with diagnosing crashes caused by over-eager XID reuse in Xlib, see bug 581526.
http://bugzilla.gnome.org/show_bug.cgi?id=581526
Personally as I do not intend to use the diagnostics infos provided by the "XID collision" messages, I rebuilt the gtk2 package without this added warning message.
I used the ABS build tree and added that gdkxid.patch to build process :
--- gtk+-2.16.5/gdk/x11/gdkxid.c 2009-06-19 04:59:18.000000000 +0200
+++ gtk+-2.16.5/gdk/x11/gdkxid.c.new 2009-07-22 11:30:12.000000000 +0200
@@ -56,10 +56,10 @@
if (!display_x11->xid_ht)
display_x11->xid_ht = g_hash_table_new ((GHashFunc) gdk_xid_hash,
(GEqualFunc) gdk_xid_equal);
-
+/*
if (g_hash_table_lookup (display_x11->xid_ht, xid))
g_warning ("XID collision, trouble ahead");
-
+*/
g_hash_table_insert (display_x11->xid_ht, xid, data);
}and added that line in the PKGBUILD :
patch -Np1 -i "${srcdir}/gdkxid.patch" || return 1
along with the patch in the source lines and md5sums lines.
It's not a fix but to suppress the annoying "XID collision" messages, which I can't use because I don't develop gtk or firefox.
I post that to share what I found and did in the present situation, waiting for future bug fixes.
Offline
Thanks for the info. I'm getting lots of those warnings as well and see no need for them to be there if there is no need for me to worry about them.
oz
Offline
I get the same shit, this is one patch that should be added, as the code now is just cluttering up my tty and what logs it decides to write too.
Offline