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 #14 from Matthias Clasen <mclasen(a)redhat.com> 2008-12-15 00:04:25 EDT
---
Akira, thanks for investing the time to track this down this far.
3. imsettings-xim is running. it grabs same window id. thus, window id on
_NET_SUPPORTING_WM_CHECK is valid again. which isn't right.
Have you confirmed that this is actually happening ? I'd be surprised if the X
server recycled client ids that quickly, but it is of course possible...
a. metacity doesn't delete _NET_SUPPORTING_WM_CHECK from the root window. it
may be dangerous since the window id could be reused.
Worth filing a bug about.
b. invoking xfce-mcs-manager before xfwm4 may be not a good idea as long as
it
uses gdk_x11_screen_get_window_manager_name(), because of caching the value.
it's still likely to return "unknown" if no _NET_SUPPORTING_WM_CHECK is
set
to
the root window and it's being cached before running xfwm4.
If things work as expected, you'll get a window-manager-changed signal in
xfce-mcs-manager when xfwm4 starts up, so this shouldn't be a problem. But
you'll of course have to expect the warning
xfce_err (_("These settings cannot work with your current window
manager (%s)"), wm_name);
to trigger if you start xfce-mcs-manager earlier than xfwm4. And the manager
needs to handle window manager changes correctly.
--
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.