On Mon, 15 Dec 2003 16:28:18 +0000
Mikhael Goikhman <migo_at_homemail.com> wrote:
> On 15 Dec 2003 19:16:56 +0200, stu wrote:
> >
> > On Mon, 15 Dec 2003 13:59:11 +0000
> > Mikhael Goikhman <migo_at_homemail.com> wrote:
> >
> > > On 15 Dec 2003 16:58:10 +0200, stu wrote:
> > > >
> > > > I have three individual konsole sessions running. Whenever I
> > > > restart fvwm, the konsole sessions are re-arranged
> > > >
> > > > Before Restart
> > > > --------------
> > > > DesktopPage 3 : konsole session 1
> > > > DesktopPage 4 : konsole session 2
> > > > DesktopPage 10 : konsole session 3
> > > >
> > > > After Restart
> > > > -------------
> > > > DesktopPage 3 : konsole session 3
> > > > DesktopPage 4 : konsole session 1
> > > > DesktopPage 10 : konsole session 2
>
> What exactly do you mean by "DesktopPage 3"?
> Desk 1, Page 0, 2 or something else?
I should have been more specific. I have one desktop with a size of 10x2
(as stated in my original post), so :
DesktopPage 3 = Page 2 0
DesktopPage 4 = Page 3 0
DesktopPage 10 = Page 9 0
> > > > The re-arranging does not seem to follow any pattern, except
> > > > that it seems to happen after every restart (using fvwm's
> > > > 'Restart' command).
> > > >
> > > > Why is this happening?
> > > > How would I prevent this from happening?
> > >
> > > It seems like you run fvwm under some session manager, like
> > > ksmserver.
> >
> > No I don't. fvwm is all I need :)
>
> It is easy to determine whether fvwm is run under a session manager.
> Open any xterm or FvwmConsole and execute: echo $SESSION_MANAGER # if
> set
I checked - it's not set. My whole aim in running fvwm is to have as
light a 'window management system' as possible running on my machine
- my work machine, never fast enough :(
> > > So either don't do this, i.e. put "fvwm" as the only program of
> > > your~/.xinitrc,
> >
> > My ~/.xinitrc contains only the following :
> >
> > xsetroot -solid black
> > xset r rate 400 80
> > # This pointer is ugly
> > xsetroot -cursor_name diamond_cross
> > xscreensaver &
> > exec fvwm &>fvwm.out 2>&1
>
> I hope this is a typo, because this first "&" is incorrect, you should
> run the window manager in foreground, if you run it in background then
> some other process holds the X running (usually a session manager).
Yes, this is a typo, (temporary code to get some of fvwm's error
messages) although fvwm runs perfectly well this way. I definitely do
not have a session manager running.
Regards
--
Stuart Logie
Programmer
UNIVERSAL COMPUTER SERVICES (PTY) LTD
A member of South Africa's largest retail software vendor, the UCS Group
Tel : (011) 712 1371 Cell : 082 902 5632
Fax : (011) 339 3421
Internet : http://ucs.co.za
"I am the Unconquerable Spirit."
-- Poet Unknown
Powered by Debian GNU/Linux - testing/unstable
--
Visit the official FVWM web page at <URL: http://www.fvwm.org/>.
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_fvwm.org.
To report problems, send mail to fvwm-owner_at_fvwm.org.
Received on Wed Dec 17 2003 - 11:13:46 GMT