Re: Broken WM change

On Wed, 18 Mar 2009 20:43:46 +0000
Thomas Leonard <talex5 <at> gmail.com> wrote:

> >> On Thu, 5 Mar 2009 22:38:55 +0000
> >> Abrolag <abrolag <at> users.sourceforge.net> wrote:
> >>
> >> > I can reasonably reliable switch between OpenBox and Kwin, but
> >> > OroboROX, Sawfish, xfwm4 all crash. In doing so they disable WM
> >> > selection and the only way I can recover control is by loging out and
> >> > back in again.
> 
> How do they disable switching? Is the process still running (so
> ROX-Session doesn't prompt for a new one) or does the prompt get
> burried under other windows, etc? Putting some print statements in
> might help track it down.

I'm aware of something "not quite right" in ROX-Session's WM management,
which means it can lose track of the active window manager, but I
haven't really had the motivation to fix it TBH. I don't know whether
the python ROX-Session has the same problem.

Modern window managers are supposed to have a "--replace" option and
allow other wms using the same protocol to replace them, but neither
OroboROX nor Openbox support that. Sawfish probably doesn't, but I think
kwin and xfwm4 do.

--

-- 
TH * http://www.realh.co.uk

------------------------------------------------------------------------------
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
easily build your RIAs with Flex Builder, the Eclipse(TM)based development
software that enables intelligent coding and step-through debugging.
Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com