Error when I press "Open project" (Linux 32 bit) [SOLVED]

Bugs
#1

Hi guys. I’m following the GETTING STARTED TUTORIAL.
I’m stuck in the 4th step. When I click “Open project”, nothing
happens.

In the error log sector appears that message:
“Unhandled event loop exception”

plug-in:
org.eclipse.ui

Thanks for your help

#2

Are you running on Mac or Windows? Does it help to restart the editor? Do you see any additional output in the Error Log window?

1 Like
#3

Thanks for response britzl. I’m running it on Linux. This is the entire output log:

Exception Stack Trace:

org.eclipse.swt.SWTError: No more handles [Unknown Mozilla path (MOZILLA_FIVE_HOME not set)]
	at org.eclipse.swt.SWT.error(SWT.java:4387)
	at org.eclipse.swt.browser.Mozilla.initMozilla(Mozilla.java:1936)
	at org.eclipse.swt.browser.Mozilla.create(Mozilla.java:699)
	at org.eclipse.swt.browser.Browser.<init>(Browser.java:99)
	at com.dynamo.cr.editor.dialogs.OpenIDLoginDialog.createDialogArea(OpenIDLoginDialog.java:200)
	at org.eclipse.jface.dialogs.Dialog.createContents(Dialog.java:760)
	at com.dynamo.cr.editor.dialogs.OpenIDLoginDialog.createContents(OpenIDLoginDialog.java:181)
	at org.eclipse.jface.window.Window.create(Window.java:431)
	at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1089)
	at org.eclipse.jface.window.Window.open(Window.java:790)
	at com.dynamo.cr.editor.Activator.connectProjectClient(Activator.java:366)
	at com.dynamo.cr.editor.handlers.ConnectHandler.execute(ConnectHandler.java:20)
	at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:290)
	at org.eclipse.core.commands.Command.executeWithChecks(Command.java:499)
	at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508)
	at org.eclipse.ui.internal.handlers.HandlerService.executeCommand(HandlerService.java:169)
	at org.eclipse.ui.internal.handlers.SlaveHandlerService.executeCommand(SlaveHandlerService.java:241)
	at org.eclipse.ui.menus.CommandContributionItem.handleWidgetSelection(CommandContributionItem.java:829)
	at org.eclipse.ui.menus.CommandContributionItem.access$19(CommandContributionItem.java:815)
	at org.eclipse.ui.menus.CommandContributionItem$5.handleEvent(CommandContributionItem.java:805)
	at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
	at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1276)
	at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3562)
	at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3186)
	at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2701)
	at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2665)
	at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2499)
	at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:679)
	at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
	at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:668)
	at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
	at com.dynamo.cr.editor.Application.start(Application.java:42)
	at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:353)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:180)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
	at java.lang.reflect.Method.invoke(Unknown Source)
	at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:629)
	at org.eclipse.equinox.launcher.Main.basicRun(Main.java:584)
	at org.eclipse.equinox.launcher.Main.run(Main.java:1438)
#4

Have a look at this potential solution: https://www.eclipse.org/forums/index.php/t/235996/

2 Likes
#5

Great! now Defold crashes when I click “Open Project” ha ha. The error became another xD.

I just ran this command:
apt-get install libwebkitgtk-1.0-0

#6

I removed the library

apt-get remove libwebkitgtk-1.0-0

and came back to the first error xD

#7

What kind of error did you get the second time?

1 Like
#8

Are you on 64bit Linux?

1 Like
#9

No man. It’s Elementary Os freya 32 bit (ubuntu-based distro)

#10

I solved the second error. I came back to the first one: “When I click “Open project”, nothing happens”.

"Unhandled event loop exception" :pensive:

#11

When I say: “nothing happens” means that the “open project window” doesn’t open

#12

Oh yeah! I solved the problem :smiley:. I just:

  • Downloaded the xulrunner (I don’t know what it is)
  • Extract it on /opt/ folder
  • And I added the line: “-Dorg.eclipse.swt.browser.XULRunnerPath=/opt/xulrunner”
    in the ./Defold-linux.gtk.x86/Defold.ini file
  • I restarted Defold

And I can open the “open project window” :smiley: Woooooo!

Screenshot from 2016-02-03 08:07:29.png1368×767 398 KB

4 Likes
"Could not open window" error in side scroller tutorial
Can't build project. console is empty. Error log tab "Unhandled event loop exception" (SOLVED)
#13

Nice! Let us know if you run into any other issues!

2 Likes
#14

Thanks buddy! I hope to help other “defolders” with their issues also

2 Likes
#15

Thank you very much for documenting this. I’m using Elementary OS too and got to solve the issue just as you said. Using chrome instead of mozilla so I also had to change that in the .ini file.

#16

There’s a file called Defold-linux.sh that is shipped with the Linux (64bit) version of Defold. If you start Defold using that script instead of the Defold binary it should work, in addition to mapping a XulRunner, we’re making some changes to the desktop environment to better support the Defold editor.

2 Likes