Re: [SPAM] RE: Potentially **DANGEROUS** bug in 5.0 - 5.1

2003-06-10 Thread Robert Huff
Ben Calvert writes: > I think I see what's wrong: My apologies - the XF86Config was edited to remove stuff not directly related to the mouse. To clarify: X works fine _except_ for the mouse. Robert Huff ___

Re: [SPAM] RE: Potentially **DANGEROUS** bug in 5.0 - 5.1

2003-06-10 Thread Ben Calvert
I think I see what's wrong: Remington L. said: > And now for extensive information. Heres my XF86config > > Section "Monitor" > Identifier "Monitor0" > VendorName "Monitor Vendor" > ModelName"Monitor Model" > EndSection you have no information at all specified for y

Re: Potentially **DANGEROUS** bug in 5.0 - 5.1

2003-06-10 Thread Kevin Oberman
What you are seeing is probably the most literal demonstration of bit rot I can imagine. It sounds like the effect one gets from turning off the drive to the LCD panel, but leaving the back-light on. It's very odd looking. Most likely something in XFree86 is telling the video card to do something

RE: Potentially **DANGEROUS** bug in 5.0 - 5.1

2003-06-10 Thread Remington L.
Take a look at Picture5.jpg for what I'm referring too. And now for extensive information. Heres my XF86config Section "ServerLayout" Identifier "XFree86 Configured" Screen 0 "Screen0" 0 0 InputDevice"Mouse0" "CorePointer" InputDevice"Keyboard0" "

Re: Potentially **DANGEROUS** bug in 5.0 - 5.1

2003-06-10 Thread Ben Calvert
Remington L. said: > I have a Sony VAIO GRX-570 laptop. When 5.0-R came out I noticed VERY > unusual symptoms on startx. This is very hard to describe(I'm gonna get a > picture and post). When I launch startx the screen goes blank, and imagine > this ocean wave type thing sweep across my screen. It