[SPARCbook] Display problem with Netscape 4.73

[Jan.Klingel at edag-us.com]

Hello,

I wonder if this is related to a problem I have on my SPARCbook 3GX: After a
while of using Netscape 4.7 the mouse cursor is slowly moving down the screen.
OS is Solaris 2.6, recommended patch cluster, Tadpole drivers and patches.

cu

Jan
---cut---

Message: 1
Date: Sun, 11 Jun 2000 14:59:02 +0200 (CEST)
From: Rainer Canavan <rainer at canavan.de>
Subject: Re: [SPARCbook] Display problem with Netscape 4.73 under Solaris 2.6
To: sparcbook at sunhelp.org
Reply-To: sparcbook at sunhelp.org

OK, I've found the guilty one: It's 105284-33 Motif 1.2.7: Runtime library
patch. I can install/uninstall it, and the display problems come and go
away. All other patches from both Tadpole and Solaris 2.6 are installed.
Now, the question is: is this a Netscape, Tadpole, or Solaris bug?
I don't know what version of motif Netscape was originally linked
against, but that's most probably be something from Solaris 2.5.1. It's also
interesting to see that some people seem to have this problem, and others
not.  What versions of 105284 do you have installed?

Rainer


On  5-Jun-00 at 16:38, Ken Hansen (n2vip at bellatlantic.net) wrote:
> That would be great...
>
> Ken
>
> ----- Original Message -----
> From: "Rainer Canavan" <canavan at cs.bonn.edu>
> To: <sparcbook at sunhelp.org>
> Sent: Monday, June 05, 2000 2:20 AM
> Subject: Re: [SPARCbook] Display problem with Netscape 4.73 under Solaris
> 2.6
>
>
> > > On Fri, 2 Jun 2000, Ken Hansen wrote:
> > >
> > > > Hello,
> > > >     I have installed Netscape Communicator 4.73 on my SPARCBook 3GX
> > > >     running
> > > > Solaris 2.6, but I am having a problem - when I call up a web site,
> the
> > > > initial screen appears fine, but if I scroll down, the display is
> > > > jumbled.
> > > >     By jumbled I mean, for example, the lines of text that were
> > > >     previously covered up
> > > > are now displaying a few times in succession,and sometimes over other
> > > > lines. It is as if the CPU/display can not keep up with the scroll
> > > > request and just tries it's best to "throw up" what it can.

[...]