Bug 857 - exception in 'getting started' page (1GEUXRR)
Summary: exception in 'getting started' page (1GEUXRR)
Status: RESOLVED FIXED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: User Assistance (show other bugs)
Version: 2.0   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Dorian Birsan CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2001-10-10 21:49 EDT by Dorian Birsan CLA
Modified: 2002-04-22 14:19 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dorian Birsan CLA 2001-10-10 21:49:02 EDT
AK (6/5/01 7:07:04 PM)
	note: i use internet explorer 2.0

	1. open the getting started page
	2. hit the Workbench User Guide link
	3. note: no busy cursor ! <<BUG 1
	4. an error message show up saying that i don't have a correct version of ie installed.
		but it does not tell me which version _is_ correct. << BUG 2
	5. i get the following walkback in the console << BUG 3

		
Check to see if the correct version of Internet Explorer is installed on your sy
stem.
org.eclipse.swt.SWTException: Class ID not found in registry result = -214722100
5
        at org.eclipse.swt.ole.win32.OLE.error(OLE.java:304)
        at org.eclipse.swt.ole.win32.OleClientSite.getClassID(OleClientSite.java
:631)
        at org.eclipse.swt.ole.win32.OleControlSite.<init>(OleControlSite.java:8
0)
        at org.eclipse.help.internal.ui.win32.HelpControlSite.<init>(HelpControl
Site.java:28)
        at org.eclipse.help.internal.ui.win32.WebBrowser.<init>(WebBrowser.java:
102)
        at org.eclipse.help.internal.ui.win32.BrowserFactory.createBrowser(Brows
erFactory.java:27)
        at org.eclipse.help.internal.ui.HTMLHelpViewer.createControl(HTMLHelpVie
wer.java:56)
        at org.eclipse.help.internal.ui.HTMLHelpViewer.<init>(HTMLHelpViewer.jav
a:35)
        at org.eclipse.help.internal.ui.EmbeddedHelpView.createPartControl(Embed
dedHelpView.java:107)
        at org.eclipse.ui.internal.PartPane$2.run(PartPane.java:54)
        at org.eclipse.core.internal.runtime.InternalPlatform.run(InternalPlatfo
rm.java(Compiled Code))
        at org.eclipse.core.runtime.Platform.run(Platform.java(Compiled Code))
        at org.eclipse.ui.internal.PartPane.createChildControl(PartPane.java:52)

        at org.eclipse.ui.internal.PartPane.createControl(PartPane.java:96)
        at org.eclipse.ui.internal.ViewPane.createControl(ViewPane.java:108)
        at org.eclipse.ui.internal.PartSashContainer.createControl(PartSashConta
iner.java:163)
        at org.eclipse.ui.internal.PerspectivePresentation.activate(PerspectiveP
resentation.java:78)
        at org.eclipse.ui.internal.Perspective.onActivate(Perspective.java:499)
        at org.eclipse.ui.internal.WorkbenchPage.onActivate(WorkbenchPage.java:8
27)
        at org.eclipse.ui.internal.WorkbenchWindow$5.run(WorkbenchWindow.java:87
2)
        at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java(Com
piled Code))
        at org.eclipse.ui.internal.WorkbenchWindow.setActivePage(WorkbenchWindow
.java:860)
        at org.eclipse.ui.internal.WorkbenchWindow.busyOpenPage(WorkbenchWindow.
java:281)
        at org.eclipse.ui.internal.WorkbenchWindow.access$6(WorkbenchWindow.java
:269)
        at org.eclipse.ui.internal.WorkbenchWindow$4.run(WorkbenchWindow.java:64
1)
        at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java(Com
piled Code))
        at org.eclipse.ui.internal.WorkbenchWindow.openPage(WorkbenchWindow.java
:638)
        at org.eclipse.help.internal.ui.DefaultHelp.getHelpViewInHelpPerspective
(DefaultHelp.java:223)
        at org.eclipse.help.internal.ui.DefaultHelp.getHelpViewInCurrentPerpecti
ve(DefaultHelp.java:167)
        at org.eclipse.help.internal.ui.DefaultHelp.displayHelp(DefaultHelp.java
:132)
        at org.eclipse.ui.internal.dialogs.WelcomeItem.openHelpTopic(WelcomeItem
.java:91)
        at org.eclipse.ui.internal.dialogs.WelcomeItem.access$0(WelcomeItem.java
:88)
        at org.eclipse.ui.internal.dialogs.WelcomeItem$1.run(WelcomeItem.java:13
1)
        at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java(Com
piled Code))
        at org.eclipse.ui.internal.dialogs.WelcomeItem.triggerLinkAt(WelcomeItem
.java:129)
        at org.eclipse.ui.internal.dialogs.WelcomeEditor$1.mouseUp(WelcomeEditor
.java:71)
        at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java(
Compiled Code))
        at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java(Compiled C
ode))
        at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java(Compiled C
ode))
        at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java(Compil
ed Code))
        at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java(Compiled
 Code))
        at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java(Compile
d Code))
        at org.eclipse.ui.internal.Workbench.run(Workbench.java:620)
        at org.eclipse.core.internal.boot.InternalBootLoader.run(InternalBootLoa
der.java:815)
        at org.eclipse.core.boot.BootLoader.run(BootLoader.java:285)
        at java.lang.reflect.Method.invoke(Native Method)
        at org.eclipse.core.launcher.Main.basicRun(Main.java:69)
        at org.eclipse.core.launcher.Main.run(Main.java:311)
        at org.eclipse.core.launcher.Main.main(Main.java:198)

NOTES:
EG (6/5/2001 9:18:48 AM)
	moving to ITPUI

KH (6/5/2001 3:25:25 PM)
	Moving to TOR

	MF (6/7/01 3:47:46 PM)
		OK. 
		For bug 1, I *do* get the hour glass. So can you please be more specific if you are doing some 
		special steps?

		For bug 2: I have added the IE version to the pop-up message.

		For bug 3: yes, we do stack dump, but we stack dump to our own .log file, not console.
		Note that we are using the Platform's "log" object, and the platform by default has a global
		log listener, that will listen to us. 
		So the only way that I can see where you will see us stack dumping to the console, it would be if
		you have started the platform with logging directed to standard out. 
		And even then, it is *not* us stack dumping, we would still be logging to our .log file in this 
		scenario. It is the platform that is listening to us, and deciding to use standard out instead.

		So the point is, can you please let us know if you had platform logging directed to standard
		out ?


	MF (6/7/01 4:52:12 PM)
		Bug2: fixed in build > 0.119
Comment 1 DJ Houghton CLA 2001-10-24 06:27:08 EDT
PRODUCT VERSION:
	118

Comment 2 Dorian Birsan CLA 2002-04-22 14:19:19 EDT
It was fixed in 1.0