🚀 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'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've had this problem throughout 3 different XFree86 versions 
(3.1.2, 3.2, and now 3.2A).  Using Linux 2.0.29 (was Red Hat 4.0),
a Panasonic CF-41 laptop with C&T65548 video, and the XF86_SVGA server.  

Mine will SIGSEGV consistently - 9 out of 10 times I switch from 
X to another tty.  This happens both in 8-bit and 16-bit color modes, 
apparently regardless of what is running. AHHH!!

It would be nice if, like everyone else, I could access the virtual 
consoles while running X.  

Does anyone have any insight as to the nature of this beast?

Thanks ahead of time,

Nelson Tibbitt


-----BEGIN GEEK CODE BLOCK-----
GAT d- s:+ !a C+(+++) UI/L/S/B++(+++) P>+ L+(++) E---- W+++ N+ o? K?
w++++ O--- M-- V PS+++@ PE Y-- PGP+ t++ 5 X++ R- tv+ b DI++ D+ G e>* 
h*(!) r- y*(+)
------END GEEK CODE BLOCK------
"Nobody goes there anymore - it's too crowded."