Closed
Bug 200243
Opened 23 years ago
Closed 23 years ago
Going to jboss.org crashes browser
Categories
(SeaMonkey :: General, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: burt.alexander, Assigned: asa)
References
()
Details
(Keywords: crash)
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3) Gecko/20030313
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3) Gecko/20030313
When loading http://www.jboss.org, the browser crashes with no other indications
- stack traces or other.
Reproducible: Always
Steps to Reproduce:
1.Go to jboss.org
2.Restart browser
3.
Actual Results:
Browser crashes
Expected Results:
Browser should load page
Comment 1•23 years ago
|
||
Reporter, could you install the 1.4a build and try it again?
http://ftp.mozilla.org/pub/mozilla/releases/mozilla1.4a/
Keywords: crash
wfm 200303105 on xp pro sp1.
What Linux version are you using? Are you using rpm Moz install?
What java VM are you using?
Comment 4•23 years ago
|
||
Burt, what version of the Flash plugin are you using? What _exact_ mozilla
binary did you download?
| Reporter | ||
Comment 5•23 years ago
|
||
I have the 1.3 gtk2 rpms of Mozilla installed under RH8, the Shockwave Flash 4.0
r12 plugin, and the 1.4.0_01 (build 1.4.0_01-b3) Sun jdk/plugin installed. I
have a slow connection; will try the latest Mozilla when I can.
Burt.
| Reporter | ||
Comment 6•23 years ago
|
||
This may need to be a separate bug, but I've just noticed that the Java plugin
no longer works with this build. I have symlinks with
ns610/libjavaplugin_oji.so in my /usr/lib/mozilla/plugins (old symlink, worked
between previous upgrades) and /usr/lib/mozilla-1.3/plugins (new, just to cover
the bases).
| Reporter | ||
Comment 7•23 years ago
|
||
Build 1.4a fixes all the problems.
Comment 8•23 years ago
|
||
->WFM based on reporter's last comment
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → WORKSFORME
Updated•21 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•