Re: FVWM: fvwm 2.3.24: iconifying crashes X Window System

From: Dan Espen <dane_at_mk.telcordia.com>
Date: Fri, 08 Dec 2000 14:49:16 -0500

Neil Zanella <nzanella_at_cs.mun.ca> writes:
>
> On Fri, 8 Dec 2000, Dan Espen wrote:
>
> > If you meant
> > to say "crashes fvwm" you should trim down this file a bit but start with
> > sending us a stack trace.
>
> Out of curiosity how can I tell the difference between a window manager
> crash and an X Server crash? I am running in runlevel 3 and start X and
> fvwm2 simultaneously with startx. What I meant is that what I described
> returned me the the Linux console so I think that's an X Server crash
> since it's not just like fvwm is freezing... please let me know. Either
> way I will try out 2.3.25 and see if that still happens.

I think trying 2.3.25 is good advice.

Either program crashing should leave a core file, but
if XFree8.6 is like the Solaris X server, it won't produce a
core file by default.

If you see no core file, I'd guess its the X Server that crashed.
If you do see a core file, run:

file core

Some of the output on the console may supply a hint.

You are not really running both programs simultaneously,
the details vary from system to system, but heres an outline:

startx launches X which reads $HOME/.xinitrc. $HOME/.xinitrc
launches any number of X clients, usually including your window manager.
One of the X clients in your .xinitrc has to be run in the foreground,
the rest are put into the background. The one run in the foreground
is the one that holds the X session. For most users, the window manager
holds the session. When this is the case, it reinforces the illusion
that the window manager and the X Server are one and the same.

Try this,
instead of ending your .xinitrc with fvwm, end it like this:

fvwm2 || xterm

--
Dan Espen
444 Hoes Lane  Room RRC 1C-214           E-mail: dane_at_mk.telcordia.com
Piscataway, NJ 08854                     Phone: (732) 699-5570
--
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 Fri Dec 08 2000 - 13:52:23 GMT

This archive was generated by hypermail 2.3.0 : Mon Aug 29 2016 - 19:37:51 BST