From: Niels Stenhoj <stenhoj@adr.dk> Date: Fri, 1 Dec 2000 17:14:53 +0100 Message-Id: <00120117145300.01327@linux> Subject: Re: [SLE] Netscape 4.76 - No Go - Bus Error On Fri, 01 Dec 2000, you wrote:
The second time I ran into bus errors was even more frustrating. I had just upgraded my 6.3 installation to 7.0 and netscape to 4.75. Netscsape would not start for any user. It would simply give a bus error. I tried a couple of the suggestions I had seen on this list including deleting cache files and *not* using the SuSE Netscape startup script. None of these helped. I finally renamed my /opt/netscape to /opt/netscape.old (just so I could preserve the problem installation) directory and reinstalled the nescape rpm. My problem went away. I had the same plugins in both installations I have not compared the two netscape installations in detail to see what the exact differences are.
Please let me know if either of these suggestions helps you out
On Thu, 30 Nov 2000, Ben Rosenberg wrote:
Date: Thu, 30 Nov 2000 21:36:17 -0800 From: Ben Rosenberg <brosenb@suse.com> To: SuSE Linux English <suse-linux-e@suse.com> Subject: Re: [SLE] Netscape 4.76 - No Go - Bus Error
Yes, Netscape creates some temp files in /tmp that need to be deleted. I forget the name that they are created under..just hunt about in /tmp..shouldn't be much to check through.
A general approach to unwanted stuff in /tmp is to wipe it at shut down. I've added these three lines to /sbin/init.d/halt.local wipe -IfRsez /tmp mkdir /tmp chmod 777 /tmp There is a little twist to it. Sometimes you have to restart the X-server immediately after boot. The symptoms are that certain programs may not be able to execute. A restart of the X-server is a small price to pay for this security. Then possible shit being installed in /tmp by java or otherwise during a surfing session won't have any effect at boot time. Cheers, Niels