🚀 go-pugleaf

On 02 Apr 1997 18:13:33 GMT, Peter B. West <p.west@mailbox.uq.edu.au> wrote:
>Has anyone else had the problem of X being killed by a SIGSEGV when they
>switch to a virtual terminal?  It only happens when I am running 16 bit
>colour; 8 bit is OK.  It doesn't usually happen immediately I switch,
>but fairly soon after.  My startup is via xdm.
>
>I am running version 3.1.2 on an AST Bravo Pentium with an on-board
>CL5434 controller.  OS is from RedHat 4.0; don't know the kernel version
>off hand.
>
>TIA,
>Peter


I'm having the exact same problem.  And it'd be nice to know if there
are any fixes.  =)  Tho there are some situations where it'll segfault
and others where it won't.  Symptoms:

Let's say I start X with:

	bash$ X &

No problems so far ... I can switch between X and my VT just fine.
Now at my prompt, I type:

	xterm -display :0

and everything bombs.  When I'm using Netscape and I click on a text
field (like the "open location" box), then switch, X segfaults.  When
I'm using Netscape and there's nothing blinking but the "N" logo, VT
switches are fine.

Thus, it must have something to do with the X server's screen updates.
I tried this under twm, fvwm, and AfterStep with similar results, so
it's not the window manager's fault.


System Info?

I went for the X Consortium's release and compiled X11R6.3 (patched
w./ the first set of fixes) using a P5/100 with an STB Trio64 (vanilla
version).  Linux 2.0.29.  Used to be slackware 3.0, until I started
playing with its guts.  ;)  Oh, btw, I'm using the accelerated S3
server.

Anybody have any insights into this problem?


-Albert
 aklee@interport.net