question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Toolbox fails to start after updating

See original GitHub issue

I just used TLA+'s Check For Updates feature. It downloaded something and prompted me to restart. Restarting failed with “An error has occurred” and told me to view the log.

This still happens after I removed the .tlaplus directory. The newly created directory contains:

$ tree -a
.
└── .metadata
    ├── .lock
    ├── .log
    └── .plugins
        └── org.lamport.tla.toolbox.product.standalone

3 directories, 2 files

The log contains:

$ cat .metadata/.log 
!SESSION 2018-08-07 10:02:25.465 -----------------------------------------------
eclipse.buildId=1.5.7
java.version=1.8.0_73
java.vendor=Oracle Corporation
BootLoader constants: OS=macosx, ARCH=x86_64, WS=cocoa, NL=en_GB
Framework arguments:  -keyring /Users/tal/.eclipse_keyring
Command-line arguments:  -os macosx -ws cocoa -arch x86_64 -keyring /Users/tal/.eclipse_keyring

!ENTRY org.lamport.tla.toolbox.product.standalone 1 -1 2018-08-07 10:02:26.524
!MESSAGE TLA+ Toolbox started without arguments.

!ENTRY org.eclipse.osgi 4 0 2018-08-07 10:02:26.803
!MESSAGE Application error
!STACK 1
The Toolbox failed to launch because of an unexpected error. Please try to launch the Toolbox with the "-clean" parameter.
If "-clean" does not fix the problem, please open a bug and attach the .log file.

org.lamport.tla.toolbox.Application$2: org.eclipse.e4.core.di.InjectionException: Could not find satisfiable constructor in org.eclipse.e4.ui.internal.workbench.WorkbenchLogger
	at org.lamport.tla.toolbox.Application.start(Application.java:148)
	at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:388)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:497)
	at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:653)
	at org.eclipse.equinox.launcher.Main.basicRun(Main.java:590)
	at org.eclipse.equinox.launcher.Main.run(Main.java:1499)
Caused by: org.eclipse.e4.core.di.InjectionException: Could not find satisfiable constructor in org.eclipse.e4.ui.internal.workbench.WorkbenchLogger
	at org.eclipse.e4.core.internal.di.InjectorImpl.internalMake(InjectorImpl.java:408)
	at org.eclipse.e4.core.internal.di.InjectorImpl.make(InjectorImpl.java:318)
	at org.eclipse.e4.core.contexts.ContextInjectionFactory.make(ContextInjectionFactory.java:162)
	at org.eclipse.e4.ui.internal.workbench.swt.E4Application.createDefaultContext(E4Application.java:510)
	at org.eclipse.e4.ui.internal.workbench.swt.E4Application.createE4Workbench(E4Application.java:204)
	at org.eclipse.ui.internal.Workbench.lambda$3(Workbench.java:614)
	at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
	at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:594)
	at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148)
	at org.lamport.tla.toolbox.Application.start(Application.java:141)
	... 12 more
!SESSION 2018-08-07 10:06:01.637 -----------------------------------------------
eclipse.buildId=1.5.7
java.version=1.8.0_73
java.vendor=Oracle Corporation
BootLoader constants: OS=macosx, ARCH=x86_64, WS=cocoa, NL=en_GB
Framework arguments:  -keyring /Users/tal/.eclipse_keyring
Command-line arguments:  -os macosx -ws cocoa -arch x86_64 -keyring /Users/tal/.eclipse_keyring

!ENTRY org.lamport.tla.toolbox.product.standalone 1 -1 2018-08-07 10:06:02.699
!MESSAGE TLA+ Toolbox started without arguments.

!ENTRY org.eclipse.osgi 4 0 2018-08-07 10:06:02.982
!MESSAGE Application error
!STACK 1
The Toolbox failed to launch because of an unexpected error. Please try to launch the Toolbox with the "-clean" parameter.
If "-clean" does not fix the problem, please open a bug and attach the .log file.

org.lamport.tla.toolbox.Application$2: org.eclipse.e4.core.di.InjectionException: Could not find satisfiable constructor in org.eclipse.e4.ui.internal.workbench.WorkbenchLogger
	at org.lamport.tla.toolbox.Application.start(Application.java:148)
	at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:388)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:497)
	at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:653)
	at org.eclipse.equinox.launcher.Main.basicRun(Main.java:590)
	at org.eclipse.equinox.launcher.Main.run(Main.java:1499)
Caused by: org.eclipse.e4.core.di.InjectionException: Could not find satisfiable constructor in org.eclipse.e4.ui.internal.workbench.WorkbenchLogger
	at org.eclipse.e4.core.internal.di.InjectorImpl.internalMake(InjectorImpl.java:408)
	at org.eclipse.e4.core.internal.di.InjectorImpl.make(InjectorImpl.java:318)
	at org.eclipse.e4.core.contexts.ContextInjectionFactory.make(ContextInjectionFactory.java:162)
	at org.eclipse.e4.ui.internal.workbench.swt.E4Application.createDefaultContext(E4Application.java:510)
	at org.eclipse.e4.ui.internal.workbench.swt.E4Application.createE4Workbench(E4Application.java:204)
	at org.eclipse.ui.internal.Workbench.lambda$3(Workbench.java:614)
	at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
	at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:594)
	at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148)
	at org.lamport.tla.toolbox.Application.start(Application.java:141)
	... 12 more

I don’t know how to pass -clean to it.

Issue Analytics

  • State:closed
  • Created 5 years ago
  • Reactions:2
  • Comments:10 (5 by maintainers)

github_iconTop GitHub Comments

1reaction
lemmycommented, Aug 7, 2018

There is additional state in the configuration directory under /Applications/TLA+ Toolbox.app.

0reactions
lemmycommented, Nov 22, 2018

842f0be7c85a505547d135ae1f83d8ce956483c9

Read more comments on GitHub >

github_iconTop Results From Across the Web

Toolbox crash on startup after update on windows10 : TBX-6461
1 driver, the Toolbox app crashes with the popup: "LoadLibrary failed with error 87: The parameter is incorrect", no logs are created on...
Read more >
Solved: HP Toolbox won't run after Windows 10 update
After the latest Windows 10 update, HP Toolbox will not start no matter what I do. I've tried running as administrator and tried...
Read more >
Canon ToolBox error after Win 10 Update - Microsoft Community
Have a canon mf4150 printer scanner which worked fine up until last Win10 update. Now it does not recognize scanner but printer works...
Read more >
Fix SOLIDWORKS Previous Toolbox Installed Blocking ...
If the update fails to complete, the first step is to repair SOLIDWORKS. Open the Control Panel and find Programs and Features. Locate ......
Read more >
Troubleshoot ToolBox installation issue - OfficeScan
The following error message appears when installing the ToolBox plugin via plug-in manager: An update error occured... Error: An update error occurred. Plug-in ......
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found