FVWM: Crash in Linux

From: Erik Rissanen <erik.rissanen_at_mn.medstroms.se>
Date: Fri, 31 May 1996 13:39:09 +0200 (MET DST)

I have tried fvwm2 42, but it seems to be very unstable. I didn't
find this bug in the mailing list archives or the TO-DO list, so
I thought that I should report it.

The problem is that fvwm2 crashes when I switch to an another
virtual console with ctrl+alt+Fn (Fn is any F-key). This seems to
happen at random times, but very often. To produce it I just
do something in X and switch from and back until it happens.
It always happens when I switch from X to text, never the opposite.

Here is the output:

Fatal server error:
Caught signal 11. Server aborting

X connection to :0.0 broken (explicit kill or server shutdown).
X connection to :0.0 broken (explicit kill or server shutdown).
X connection to :0.0 broken (explicit kill or server shutdown).
X connection to :0.0 broken (explicit kill or server shutdown).
X connection to :0.0 broken (explicit kill or server shutdown).
xterm: fatal IO error 2 (Broken pipe) or KillClient on X server ":0.0"
xinit: connection to X server lost.

This never happens with fvwm 1.2. I am currently using Linux 1.99.8, but
I had the same problem with 1.2.13.

In case it is a bug in the server, here is the version info:

XFree86 Version 3.1.2 / X Window System
(protocol Version 11, revision 0, vendor release 6000)

It is the SVGA server.
I run it with a Cirrus Logic 5434 card with 2 Mb RAM in 16bpp.

I didn't find any notice of such bug in the XFree86 FAQ.

If you need additional info, just contact me.

Bye.

-- 
http://www.mn.medstroms.se/~d5dos/
I am sorry for my bad English (eller svenska).
--
Visit the official FVWM web page at <URL:http://www.hpc.uh.edu/fvwm/>.
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_hpc.uh.edu.
To report problems, send mail to fvwm-owner_at_hpc.uh.edu.
Received on Fri May 31 1996 - 10:26:25 BST

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