headers
Abrolag | 18 Mar 2009 15:30
Picon

Re: Broken WM change

On Wed, 11 Mar 2009 12:31:17 +0000
Abrolag <abrolag <at> users.sourceforge.net> wrote:

> On Thu, 5 Mar 2009 22:38:55 +0000
> Abrolag <abrolag <at> users.sourceforge.net> wrote:
> 
> > I've been using OpenBox for a long time now, but just recently
> > thought I'd have a look again at other WMs but everything seems
> > horribly unstable.
> > 
> > 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.
> > 
> > The command I'm using (in a script) is:
> > 
> > dbus-send --print-reply --type=method_call --dest=net.sf.rox.Session \
> >   /Settings net.sf.rox.Session.Settings.SetString
> > string:ROX/WindowManager string:xfwm4
> > 
> > OroboROX of course has its own incomprehensible startup script!
> > 
> > I had been running ROX Session 0.30, but upgrading to 0.40 made no
> > difference.
> 
> I am very disappointed that nobody has commented on this. Mostly I want
> to carry on using OpenBox, but would still like to be able to switch to
> the others from time to time.
(Continue reading)

Permalink | Reply |
headers
Thomas Leonard | 18 Mar 2009 21:43
Picon
Gravatar

Re: Broken WM change

2009/3/18 Abrolag <abrolag <at> users.sourceforge.net>:
> On Wed, 11 Mar 2009 12:31:17 +0000
> Abrolag <abrolag <at> users.sourceforge.net> wrote:
>
>> On Thu, 5 Mar 2009 22:38:55 +0000
>> Abrolag <abrolag <at> users.sourceforge.net> wrote:
>>
>> > I've been using OpenBox for a long time now, but just recently
>> > thought I'd have a look again at other WMs but everything seems
>> > horribly unstable.
>> >
>> > 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.

>> > The command I'm using (in a script) is:
>> >
>> > dbus-send --print-reply --type=method_call --dest=net.sf.rox.Session \
>> >   /Settings net.sf.rox.Session.Settings.SetString
>> > string:ROX/WindowManager string:xfwm4
>> >
>> > OroboROX of course has its own incomprehensible startup script!
>> >
>> > I had been running ROX Session 0.30, but upgrading to 0.40 made no
(Continue reading)

Permalink | Reply |
headers
Abrolag | 19 Mar 2009 22:22
Picon

Re: Broken WM change

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

> 2009/3/18 Abrolag <abrolag <at> users.sourceforge.net>:
> > On Wed, 11 Mar 2009 12:31:17 +0000
> > Abrolag <abrolag <at> users.sourceforge.net> wrote:
> >
> >> On Thu, 5 Mar 2009 22:38:55 +0000
> >> Abrolag <abrolag <at> users.sourceforge.net> wrote:
> >>
> >> > I've been using OpenBox for a long time now, but just recently
> >> > thought I'd have a look again at other WMs but everything seems
> >> > horribly unstable.
> >> >
> >> > 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.

OK, first thing is I hadn't noticed the --replace operation (must be
getting slow, when did that arrive). If I untick this then all WMs
behave correctly. BTW Tony, the latest version of OpenBox does respond
correctly.

The problem occurs when you incorrectly have this option set and the
(Continue reading)

Permalink | Reply |
headers
Tony Houghton | 19 Mar 2009 00:00
Picon

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

------------------------------------------------------------------------------
(Continue reading)

Permalink | Reply |

Gmane