130914 - cannot run Novell eGuide on Mozilla 0.9.9 or earlier

Status: CLOSED WORKSFORME

(Core Graveyard :: Java-Implemented Plugins, defect)

Description

[hbueno]

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.9) Gecko/20020311
BuildID:    2002031194

We use Novell eGuide 1.5 on our intranet as a corporate phonebook.  When I click
on the link that starts eGuide, I get prompted to Grant access, I say grant
always, then it starts loading.  Mozilla status bar reads "Opening
http://intranet.abc.com/eguide/themes/en_US/themelist.properties".  (abc is not
our real domain) then the browser locks up.

Reproducible: Always
Steps to Reproduce:
1. Click on eGuide link. to start loading Java applet

Actual Results:  Browser locks up.

Expected Results:  eGuide screen should come up as it does in IE or Netscape 4.7x.

Web server is Novell Enterprise Server running on Netware 5.1 SP3, eDirectory
85.20c.

Workstation is using Java Plug-in 1.3.1_02.

Comment 1

[hbueno]

I updated to JRE 1.4 and problem is the same as first reported.

Comment 2

[Mike Schuette]

Reporter, do you still have issues with this under any of the recent mozilla
releases?  (1.0rc2 or higher)

Comment 3

[hbueno]

I just updated to RC3 and the problem is exactly the same.  After Mozilla locked
up, I went to close the Mozilla window using the upper right X button and the
talkback feature kicked in.  So, I let it send in a report.

Comment 4

[Peter 'vt100' Schwindt]

Reporter, could you give us the talbback id?

Comment 5

[hbueno]

I would, but I don't know how. 

BTW, I just installed the latest 1.1 alpha (2002061104) and the problem still
remains.  I made it crash as before, and the talkback agent popped up.  I
couldn't find an ID number on any of the screens, but I did allow it to submit
the report.

Comment 6

[Peter 'vt100' Schwindt]

Just run (in the file system) mozilla\components\talkback.exe where you will see
those Talkback IDs

Comment 7

[hbueno]

OK, the incident ID for yesterday is TB7277101X

Comment 8

[Kai Lahmann (is there, where MNG is)]

Reporter ([e-mail]):
could you please send us a new Talkback ID (from a fresh crash)? They are only
usefull for a limited time - and as nobody has asked for the stack..... sorry

Comment 9

[Bill Mason]

Resolving as we have had no reply from reporter in almost a month.

Reporter, if you are still having this issue in a current build, please reopen
and comment with details, including TalkBack ID.

Comment 10

[Peter 'vt100' Schwindt]

closed. please reopen if the problem still exists