From: Ray Allis <ray@bcstec.ca.boeing.com>
Cc: Linux/PPC Development <linuxppc-dev@lists.linuxppc.org>
Subject: Re: Communicator 4.5 or Linuxppc at fault?
Date: Sun, 06 Dec 1998 20:18:58 -0800 [thread overview]
Message-ID: <366B5732.ED9EC57B@bcstec.ca.boeing.com> (raw)
In-Reply-To: v04102f07b28e12cb45e7@[168.143.6.39]
charlie buckheit wrote:
> At 9:33 AM -0800 12/1/98, Sean Harding wrote:
> > On Mon, 30 Nov 1998, Daniel Jacobowitz wrote:
> >
> >> done on ours. 4.5 is very unstable; 4.07 I have not tried; 4.5b2 is
> >
> > Note that this is unlikely to be a glibc2-related problem. 4.5 is unstable
> > on every LinuxPPC machine I've tried it on (it works fine on Irix and
> > Solaris).
>
> I shut off javascript, and 4.5 has been running just fine.
Not my experience. Communicator 4.5b2 in announcing that it expires
Dec. 10. 4.5 crashes often, even with Javascript turned off. It -does-
seem to happen predictably when opening those little advertisement
windows -- like anything with http://geocities.com in it. Autocrash.
It works on mklinux? (it is so identified on the Netscape site). I am using
the June release 4 CD system on a 7500/100, and otherwise everything
works beautifully.
Is this a Linuxppc r4/KDE or Xpmac problem that will be fixed by r5/gnome?
I -live- on the web. Am I going to have to go back to MacOS when
Communicator 4.5b2 expires on the 10th?
Ray Allis - ray.allis@boeing.com
[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request@lists.linuxppc.org ]]
parent reply other threads:[~1998-12-07 4:18 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <v04102f07b28e12cb45e7@[168.143.6.39]>]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=366B5732.ED9EC57B@bcstec.ca.boeing.com \
--to=ray@bcstec.ca.boeing.com \
--cc=linuxppc-dev@lists.linuxppc.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).