Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=471927
--- Comment #9 from Akira TAGOH <tagoh(a)redhat.com> 2008-11-25 07:46:43 EDT ---
For more information:
Sorry, the above was false alarm. and it races something. I've added the below
code to see what value XGetWindowProperty returns in
gdk_x11_screen_get_window_manager_name():
diff -pruN gtk+-2.14.4.orig/gdk/x11/gdkevents-x11.c
gtk+-2.14.4/gdk/x11/gdkevent
s-x11.c
--- gtk+-2.14.4.orig/gdk/x11/gdkevents-x11.c 2008-10-17 13:06:37.000000000
+0
900
+++ gtk+-2.14.4/gdk/x11/gdkevents-x11.c 2008-11-25 19:40:42.000000000 +0900
@@ -2719,6 +2719,7 @@ gdk_x11_screen_get_window_manager_name (
&type, &format,
&n_items, &bytes_after,
(guchar **)&name);
+g_print("%d: 0x%x, %d, %ld, %ld, %s\n", getpid(),
screen_x11->wmspec_check_wind
ow, format, n_items, bytes_after, name);
gdk_display_sync (screen_x11->display);
And this appears in .xsession-errors:
21550: 0xe00003, 8, 14, 0, imsettings-xim
pid 21550 is xfce-mcs-manager, which is reporting it. and imsettings-xim
certainly owns window id 0xe00003, which was created as a communication window
between client and server in XIM. there are no code to modify _NET_WM_NAME nor
_NET_SUPPORTING_WM_CHECK in imsettings-xim though. and gtk+ has only code to
modify _NET_WM_NAME. and window manager modifies _NET_SUPPORTING_WM_CHECK.
actually just running X server and imsettings-xim doesn't create
_NET_SUPPORTING_WM_CHECK on the root window.
Since this issue doesn't appear in metacity, I'm a bit suspecting xfwm4 behaves
around it differently. looking at xfwm4 now.
--
Configure bugmail:
https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.